The public package is collateral only and performs no official actions.
Open path →Give technical reviewers the boundary map first.
A State IT reviewer quickstart for static boundary, runtime modes, adapters, audit matrix, ingest quarantine, export controls, and no-mutation proof.
Local evaluation, pilot, and production behavior are separated and production fails closed.
Open path →Persistence, audit, storage, identity, e-filing, and notification adapters are named.
Open path →Parser output is staged for review and does not mutate canonical records directly.
Open path →State IT reviewer quickstart
This route gives technical reviewers the controls they expect before any pilot conversation moves deeper.
| Review concern | Route | Control answer |
|---|---|---|
| What is public? | /demo/static-boundary-proof/ | Public walkthrough only; fictional records; no court connection. |
| What must be configured? | /demo/state-it/adapter-matrix/ | Adapters are named and court-approved integration is required. |
| What gets audited? | /demo/state-it/audit-matrix/ | Material access, review, packet, and denial events are structured. |
| How is ingest separated? | /demo/state-it/final-review-room/ | Quarantine and human promotion gate are explicit. |
| Can this mutate records? | /demo/state-it/no-mutation-boundary/ | Public route writes zero official records. |
- Static boundary stated
- Production adapters named
- Audit matrix linked
- Ingest quarantine named
- No-mutation proof visible
Court operations can be queue-first and role-safe.
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.
- 1Queue-first operations
Authenticated role claims
- 2Role-safe visibility
Court assignment model
- 3Packet and audit posture
Persistence, audit, storage, and export adapters
- 4State IT configuration boundary
Configured pilot limitations
This public walkthrough uses fictional training records. It does not submit filings, change court records, provide legal advice, or connect to a live court system. Production use requires authenticated access, configured adapters, audit logging, and court-approved integration boundaries.
