Consolidation assurance
Can the current text be derived from what was enacted?
LawVM independently replays declared amendment sources, compares the resulting state with the published consolidation, and turns each disagreement in that scope into a source-linked review item.
Applicable setting
Independent QA beside an existing publication system.
Official publishers
Review whether amendment instructions reached the right provisions, dates, and versions without giving LawVM production write access.
Legal publishers
Check editorial consolidations against primary amendment sources and preserve an auditable discrepancy record.
Ministries and drafting offices
Test a bounded transition corpus before or after publication and investigate target, payload, and commencement problems.
Researchers and civic infrastructure
Build reproducible evidence about how legal state is derived rather than treating the latest HTML page as complete history.
Evidence path
Every result keeps its source path.
- Inventory authority and sources. Identify original acts, amendments, commencement evidence, consolidated versions, and missing links.
- Compile typed transitions. Parse the instruction, resolve its target, extract its payload, and preserve rejected or ambiguous candidates.
- Check the mutation boundary. Compare the paths that changed with the declared target region and any explicitly owned migration or recovery path.
- Compare without declaring a winner. Classify agreement, LawVM defect, source gap, manual frontier, compare-shape difference, or candidate publication issue.
- Return a review queue. Package source locators, dates, diffs, rules, residuals, reproduction data, and any institutional disposition.
Crosswalk
From invariant to disposition, maturity, and result.
Each result carries the invariant checked, its source and profile scope, the frontend's enforcement mode, and a disposition. A disposition is not a general correctness grade.
| Invariant | Disposition | Frontend maturity | Result means |
|---|---|---|---|
| Source and accounting | Qualified or blocked | Source census or closure check | Declared inputs are accounted for; closure gaps remain visible. |
| Target and mutation | Established within scope or invalid | Observe-only or strict-blocking | Observed paths agree or disagree with the declared footprint; not that prose legally justified it. |
| Temporal selection | Established within scope or unresolved | Profile-specific point-in-time support | The named time model selected a state, or an unresolved commencement or expiry remains. |
| External comparison | Candidate, source pathology, or manual frontier | Comparison surface only | A difference is routed for review; it does not declare a publisher error. |
Read this crosswalk conservatively: strict-blocking failure prevents scoped promotion; observe-only records a finding without blocking. Neither mode replaces source authority, legal interpretation, or editorial sign-off.
First bounded pilot
One source-complete transition corpus.
Source-readiness comes first: freeze a declared, source-complete transition corpus or return a blocked-source map with missing authorities and dates. A comparison result cannot be clean when its source universe is unknown.
Inputs
Original and amending acts, effective-date evidence, before/after consolidations, identifiers, source authority notes, and a local legal reviewer.
Outputs
Source census, replay surface, classified discrepancy ledger, evidence packets, reproducible artifacts, and a recurring-monitor recommendation.
Operating mode
No production writes; frozen source snapshot; narrow operation families; findings remain candidates until reviewed.
Success criterion
Every declared transition receives an explicit disposition or named owner; none is silently dropped or repaired.
Publication boundary: LawVM is a read-only QA layer. It returns a candidate or review result and never writes, publishes, or automatically corrects the official text.