Developers
Adapters, events, and exports for onboarding ops teams.
How we're different
- Workflow state is durable and replayable.
- Policy gates enforce approvals.
- Evidence exports are structured (PDF + JSON).
Trust rule: AI drafts; humans decide for sensitive outcomes.
Adapter SDK (concept)
Connectors
Secure integrations to email, ticketing, storage, and core systems.
Vendor adapters
Normalize vendor checks and let customers swap vendors without rewriting onboarding ops.
Events (illustrative)
{
"event_type": "CASE_UPDATED",
"case_id": "case_123",
"timestamp": 1730000000,
"payload": {
"status": "ready",
"missing_documents": ["proof_of_business_address"]
}
}Example payload for internal planning. Event schemas should be versioned.
Docs and API
API reference
Cases, documents, approvals, binder exports.
Audit trail
Event shapes, exports, and integrity rules.
Policies
Risk tier requirements and versioning patterns.
Implementation
Deployment, network requirements, and rollouts.
Try the MVP console
Create a case, upload docs, run extraction, export a binder.