Public walkthrough pages contain fictional records only and cannot call protected case, filing, or report APIs.
Open path →Static walkthroughs and parser candidates do not mutate official records.
This State IT proof page names the safety boundary: public walkthroughs are static, parser outputs are candidates, and production record changes require authenticated app APIs plus human review.
Untrusted files move through a quarantined parser and staging store before promotion review.
Open path →Candidates can be accepted, edited, or rejected before becoming canonical evidence, timeline, or filing records.
Open path →Pilot and production modes require auth, persistence, storage, audit, and configured court-approved adapters.
Open path →No-mutation boundary table
State IT can see exactly what is static collateral, what is staged candidate data, and what requires authenticated production APIs.
| Layer | May read | May write |
|---|---|---|
| Static walkthrough | Public training record copy. | Nothing official. |
| Parser worker | Quarantine artifact. | Staged candidates only. |
| Promotion API | Reviewed candidate. | Canonical record after human review. |
| Filing API | Reviewed envelope. | State transition with audit event. |
- no-mutation boundary table visible
- public route writes zero
- parser candidates staged only
- human promotion required
- production adapters required
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.
