The law in force should be knowable
Verify changes to the law.
LawVM reconstructs point-in-time legal text from declared amendment sources. It records the operations applied, preserves what could not be proved, and makes disagreements with a published text inspectable.
For publishers and ministries, the practical use is a bounded, read-only review that can surface omitted or misapplied changes, source gaps, and parallel-language inconsistencies. The institution retains control of the official record.
Current frontend map
One core, thirteen source frontends.
Twelve jurisdiction frontends and one structured-operation frontend exercise different source, authority, language, and replay regimes in the integrated development line.
Jurisdiction frontends
Structured-operation frontend
Integration records where code lives, not how mature or authoritative it is. Each frontend keeps its own source boundary, residual frontier, and maximum public claim.
Choose the question
What are you trying to establish?
Use LawVM when a result needs its sources, changes, dates, uncertainties, and reproduction path.
What did this provision say on a particular date?
Move through a statute timeline, inspect provision history, and follow amendments back to their sources.
Explore legal state → 02 / CONSOLIDATIONDoes the published current text follow from the amendments?
Replay enacted changes independently and classify any difference against the published consolidation.
Audit a consolidation → 03 / LANGUAGESDo official-language expressions remain structurally aligned?
Review corresponding legal units, dates, citations, quantities, and explicit pairing gaps without pretending to automate legal translation.
Review parallel expressions → 04 / LEGACY SOURCESWe have APIs, PDFs, scans, or incomplete archives. Where can we begin?
Account for pages, observations, structure claims, alternatives, and unresolved regions before any reviewed derivative enters LawVM.
Assess source readiness → 05 / PUBLICATION QACan we test a drafting or publication transition before release?
Apply target, reference, temporal, language, and mutation-boundary checks to a frozen structured export.
Explore publication checks → 06 / JURISDICTIONSWhat can LawVM establish in this source regime?
Inspect frontend maturity by source, structure, effects, replay, verification, language, and public-artifact readiness.
Compare jurisdictions →Externally confirmed evidence
A replay finding became a publisher correction.
Confirmed and corrected
Riigi Teataja restored an omitted phrase in Estonia’s Auditors Activities Act.
LawVM identified that an amendment instruction had not reached the consolidated text. The official publisher reviewed the report and corrected the Estonian consolidation. The corresponding English-translation detail remains a project report pending separate adjudication.
Public correction notice: 27 April 2026. This is one confirmed case, not a general accuracy claim.
The ledger also publishes three New Zealand and two UK candidate findings, each below the confirmation threshold.
The mechanism
Compile the transitions behind the latest document.
LawVM preserves the derivation behind a current text: which source changed which legal unit, when it took effect, what mutation was authorized, and what remained unresolved.
Independent expressions
In multilingual checks, each declared language expression, source manifestation, and legal-time coordinate keeps its own provenance. Authority remains tied to the declared source for each expression.
Total accounting
Accepted operations, rejected candidates, source pathologies, manual frontiers, and comparison disagreements remain visible.
Mutation boundaries
The mutation account compares the declared target and named allowances with the paths that actually changed. Promotion from observation to blocking varies by frontend.
Reproducible artifacts
Source identities, compiler version, state roots, findings, and projections can travel together as an inspectable dossier. Inspect the assurance model →
Read the argument
The civic case and the structural constraint.
The Law in Force Should Be Knowable
Why point-in-time legal state and the transitions behind it belong in public legal infrastructure.
Read the civic essay →Why Law Is Law-Shaped
Why legal software must preserve hierarchy, identity, typed change, time, and jurisdiction-specific authority.
Read the structural essay →Choose your next path
Inspect, evaluate, run, or contribute.
Institution or publisher
Assess one source regime, then define a bounded read-only pilot with inputs, owners, and a completion criterion.
Start the assessment →Reviewer or researcher
Inspect how claims are earned, which artifacts support them, and where the current reliance boundary stops.
Review the assurance model →Developer or maintainer
Install the beta-stage development checkout, run an archive-free evidence pack, or begin a source-specific frontend.
Run LawVM locally →Public reader
Explore point-in-time legal state, watch an amendment compile, or read the civic and structural arguments.
Explore legal history →A current legal text is one state in a history of declared transitions. LawVM keeps that state, the operations behind it, and the unresolved remainder together so the result can be inspected rather than merely trusted.