Contract, invoice, act, form or another agreed document type.
SYSTEM FAMILY / DOCUMENT INTELLIGENCE
EXTRACTION≠ ACCEPTANCE
Documents in. Structured data out.
Extraction is only one step. Defined fields are checked against rules and uncertain or failed cases have an explicit review path before structured output is accepted.
What an employee gets from document work
Upload the document once. SEN prepares the information a person actually needs to review.
Extracts the required fields, runs the agreed checks and highlights anything uncertain.
Sees the structured data and the places that still need a human decision.
RESULT
Less manual copying from documents and fewer missed fields; uncertain cases stay visible instead of being silently guessed.
CANONICAL FAMILY PATH
The registry is the family-level authority. The operating slice below is illustrative first slice, not a second taxonomy.
One bounded workflow shape.
Capability stays inside explicit authority.
Interpretation, extraction or classification gets a defined task — never open-ended authority.
Completeness, allowed values and routing remain inspectable outside the model.
Human approvals and actions are explicit per workflow. Capability is not authorization.
BOUNDARY RECEIPT / 05Workflow structure, not production performance.
NO FAKE METRICSNO LIVE DEPLOYMENT CLAIMHUMAN REVIEW PATHEXPLICIT FAILURE PATH