The live control room loads and the core proof path pages open from the route cluster.
Open path →Record what passed, what failed, and what package now fixes.
This route captures live-site readiness check status for the control room, top CTAs, role proof clusters, clean URL posture, and presenter fallback routes.
The package keeps top action targets on clean trailing-slash URLs and the client bridge rewrites static hrefs before click.
Open path →E-filing, clerk, judge, State IT, and pilot decision routes are mapped for operator review.
Open path →Local verifier blocks.html href/action targets, dead controls, missing static routes, and unsafe public language.
Open path →readiness check result ledger
This page gives the operator a visible status record without exposing implementation details.
| Check | Result | Package response |
|---|---|---|
| Control room load | Reachable | Preserve route and mirrors. |
| Top Audience router | Live stale.html target observed | Generator, generated HTML, and client bridge enforce clean URLs. |
| Proof buttons | Core route cluster reachable | Map and verify every local target. |
| Final package | Local readiness check required | Run npm run verify:static-demo:all. |
- Control room loads
- Audience router uses clean route in package
- No.html generated action remains
- Role proof links resolve
- Operator reruns verifier before upload
The public package has a clear next step.
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.
- 1Audience path
Plan selection
- 2Public proof route
Account workspace
- 3Review standard
Settings and connections
- 4Forwardable next step
Review-safe outputs
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.
