Static boundary
This public package runs without login, protected runtime dependencies, Cloud Run, or private user data.
Open path →State IT evaluation room
Separate the public walkthrough from production integration requirements.
The evaluation room lets State IT inspect static boundary, auth, route policy, adapters, runtime modes, audit posture, ingest quarantine, export controls, and no-scraping assumptions.
Public proof
PublicProduction
Adapter-gatedParser
QuarantinedNo scraping
ExplicitProduction adapters
Identity, persistence, audit, storage, queue, export, notifications, filing, and ingest adapters are named.
Open path →Audit posture
Access attempts, denials, filing review, deficiencies, scheduling, packet exports, and restricted access are measurable.
Open path →Runtime mode safety
Production fails closed unless auth, persistence, audit, storage, queue, and filing adapters are configured.
Open path →Operational proof
State IT review checklist
The route gives technical reviewers a clean checklist before a pilot decision.
| Review area | Public package shows | Production requirement |
|---|---|---|
| Auth / RBAC | Role-safe route expectations | Court identity provider and role claims. |
| Persistence | Named work object model | Court-approved persistence adapter. |
| Audit | Material action matrix | Structured audit sink with correlation IDs. |
| Ingest | Quarantine and human promotion boundary | Internal parse worker with service-to-service IAM. |
Reviewer-visible checks
- Static boundary understood
- Adapters named
- Runtime modes named
- Audit events named
- Ingest quarantine named
What this proves
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
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
Review standard
Automation assists. Human review controls official records.
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.