Schemas and policy contracts represent claims, docket provenance, deadlines, filing lifecycle, ADA/accessibility routing, legal-information boundaries, and evidence integrity.
CASE STUDY 04 / LEGAL CONTINUITY
CourtChain
A governed legal workflow and matter-continuity architecture that separates claims from verified authority, tracks evidence and deadlines with provenance, and keeps filing and legal judgment with authorized humans.
PRODUCT / CONTRACT SYSTEMLEGAL + ACCESSIBILITYMERGED REFERENCE CONTRACTNON-PRODUCTION
01 / HUMAN PROBLEM
Legal workflows punish ambiguity.
Deadlines, evidence, filings, accommodations, and source authority are different kinds of state. Collapsing them into notes or chat history creates dangerous ambiguity: drafted is not filed, uploaded is not received, received is not accepted, interpretation is not an order.
CourtChain models those distinctions explicitly and fails closed when a consequential state lacks evidence.
02 / TRUTH MODEL
State transitions carry provenance.
MATTER→CLAIM→SOURCE→DEADLINE / EVENT→EVIDENCE→FILING STATE→HUMAN ACTION→AUDIT
Source-confirmed deadlines require explicit source references. Court-order, docket-entry, filed-document, legal-authority, and verified-source states cannot be manufactured by merely selecting a stronger label.
Normal filing transitions are allowlisted; for example, a draft cannot jump directly to a court-accepted state as an ordinary transition.
03 / SOFTWARE
Evidence integrity becomes executable behavior.
Deterministic validators reject unsupported authoritative states, invalid transitions, missing provenance, and unsafe public projection.
Reference fixtures allow the legal-state model to be tested without copying private litigation, custody, child, or family information into the public product story.
04 / EVIDENCE
The reference-contract package reached a merged checkpoint.
The recorded exact-head checkpoint passed the Court Continuity Contract, ontology lint, ecosystem-boundary conformance, Court validator tests, MGR regression, Agent Continuity regression, synthetic/no-secret checks, and diff hygiene.
Negative coverage includes source-free authoritative states and invalid filing-state jumps rather than only testing the happy path.
The Court Continuity Engine / CourtChain reference-contract PR is currently merged. That merge does not create production runtime or court-system authority.
No autonomous court contact, filing, payment, outcome prediction, restricted scraping, production database mutation, or real private matter ingestion is claimed.
05 / LIMITS
Legal assistance is not legal authority.
- USER ASSERTION is not VERIFIED FACT.
- DOCKET INTERPRETATION is not COURT ORDER.
- DRAFT FILING is not FILED FILING.
- UPLOADED BY USER is not PROVIDER RECEIVED.
- PROVIDER RECEIVED is not COURT ACCEPTED.
- The product does not provide autonomous legal representation or filing authority.
WHAT I LEARNED
In high-stakes software, provenance is not metadata added after the fact. It is part of the state machine. A system should be unable to become “more true” simply because its interface says so.
Contact: founder@thehumancode.tech