Static routes are public collateral and should load without protected runtime dependencies.
Open path →The public proof site is collateral, not the protected runtime app.
This page makes the demo boundary explicit for buyers: public pages load without login, use fictional training records, do not touch private user data, and do not depend on Cloud Run.
All examples are fictional public training records and not connected to a live court system.
Open path →Human review controls every official filing, packet, and record action in production.
Open path →Protected runtime, ingestion, AI orchestration, storage, and court integrations require configured production adapters.
Open path →Static boundary checklist
The boundary proof protects the pitch: the static site can sell the product without pretending to be the production runtime.
| Boundary | Static collateral | Production requirement |
|---|---|---|
| Authentication | None required. | Auth adapter configured. |
| Data | Fictional training records. | Owner-scoped persistence. |
| Ingest | Explained only. | Quarantine worker and staging store. |
| Court actions | No official actions. | Court-approved adapter required. |
- static boundary checklist visible
- public proof site is collateral
- fictional training records
- not connected to a live court system
- human review controls official actions
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.
