Review workflow
The source stays attached from intake through export
The verification spine is designed to make uncertainty inspectable. A fluent paragraph is not the unit of trust; a versioned event, its source page, its checks, and its named review decision are.
1. Register the matter
An authorized operator records the matter identifier, supervising attorney, reviewer, approved document-set description, and start time. The source files are fingerprinted, page-counted, and preserved as immutable originals.
2. Inspect every page
Native text is extracted where present and image-only pages use the approved local OCR path. Each page becomes usable, needs review, or unreadable. Empty OCR output remains an unknown page, never an assumed blank.
3. Find candidate pages
Matter-scoped retrieval identifies pages inside the authorized record. A reviewed similarity floor governs model-assisted retrieval when enabled. Below the floor, the system abstains rather than assembling an adjacent answer.
4. Build proposed events
Chronology statements remain proposals. Each event carries a date or unresolved-date state, source document and page, quote when required, coverage state, and a pending review status. Model generation is not enabled as a released feature until its representative evaluation receipt passes.
5. Review beside the source
The named reviewer accepts, edits, rejects, or marks the event not found while inspecting the source page. An edit creates a new artifact version and receipt instead of erasing the earlier result.
6. Gate the export
An export is eligible only after blocking checks pass and the authenticated supervising attorney signs the reviewed version. Signing does not override unsupported pins, held source pages, missing quotes, or unresolved review status.
Start with fit, not a file upload
The readiness review asks about your firm and intended workflow. Do not submit client names, case facts, records, health information, or privileged material.
Request a pilot readiness review