State IT evaluation
Review route security, adapter boundaries, audit events, runtime modes, and ingest quarantine before any pilot connection.
Open path →Integration posture
Court and storage integrations stay configuration-gated and review-controlled.
This public page explains the integration boundary: production use requires authenticated access, configured persistence, audit, storage, ingest, and court-approved adapters.
Production mode
Fail closedCourt adapters
RequiredParser output
Review requiredLive court link
Not presentAdapter matrix
Separate identity, persistence, audit, storage, queue, export, ingest, notification, and court filing adapters.
Open path →Ingest quarantine
Raw uploads are treated as untrusted. Parser outputs remain candidates until a person reviews and promotes them.
Open path →No-mutation boundary
Public walkthrough routes do not write records, submit filings, or connect to live court systems.
Open path →What this proves
A public visitor gets a finished route, not a dead end.
Human review remains the control point. This route is a public training record with fictional records and is not connected to a live court system.
- 1Clear entry
Public path
- 2Review-safe message
No private records
- 3Next step named
Reviewer path
- 4Production boundary
Configured adapters required
No private user dataReview-safe public posture
No live court connectionReview-safe public posture
No legal decision by automationReview-safe public posture
Production requires configured adaptersReview-safe public posture