Documentation

Run and inspect

• Getting started — install, first replay, first diff
• Explore — point-in-time timelines and provision history
• Artifacts — benchmark interpretation and current command path

Evaluate a claim

• Assurance — how a bounded LawVM claim earns its wording
• Reviewer guide — challenge, reproduce, and adjudicate a bounded claim
• Evidence ledger — confirmed, candidate, blocked, and source-pathology cases

Assess adoption

• Jurisdiction assessment — source readiness and a bounded pilot brief
• Pilots — bounded institutional and jurisdiction starting points
• Jurisdiction status — maturity and claim ceilings by source regime

Understand the model

• Architecture — compiler model, layer model, strict/quirks modes
• Essays — civic argument, structural model, and technical notes

Key concepts

Replay-first: LawVM treats legal state as the result of explicit changes applied over time. The path to the result remains inspectable.

Timelines: Provision versions are organized into temporal timelines. Point-in-time materialization selects the governing version at a given date.

Findings: The system records what happened during replay and comparison: source pathology, normalization events, editorial artifacts, replay defects, unresolved uncertainty.

Truth surfaces: Different systems expose different representations of legal state — enacted-event truth, published artifact truth, revised/editorial truth, replayed truth. These are not the same thing.