Work with LawVM

Start with a bounded source, review, or integration task.

LawVM is an open-source replay and evidence system for declared legal-source scopes. It records source identity, typed operations, point-in-time state, residuals, and comparison evidence without writing to an official production system.

Start by choosing a bounded corpus, naming the local authority and review roles, and agreeing which result the evidence may support.

Choose a starting point: run a bounded pilot, assess your source regime, maintain a frontend lane, or discuss a partnership. Do not send confidential source files until a processing boundary is agreed.

Ways to participate

Jurisdiction or source maintainer

Maintain one frontend: source acquisition, source authority model, local amendment language, benchmark corpus, and public caveats.

Benchmark maintainer

Freeze corpora, reproduce scores, publish manifests, separate replay defects from comparison-surface problems, and keep results citable.

Institutional adopter

Use LawVM as an audit layer for a legal publication pipeline, a public legal information service, or an internal consolidation QA workflow.

Research reviewer

Replicate a declared replay result, formalize the evidence model, publish comparisons, and stress-test the compiler model in other legal systems.

Module maintainer

Maintain a bounded module, fixture set, artifact release, source pipeline, or jurisdiction workbench when it serves a real adoption path.

Funding partner

Fund frontend hardening, source-pipeline work, publication pilots, or jurisdiction adoption without requiring a full new organization.

Who can use it

Official legal publishers and justice ministries: audit whether consolidated text follows enacted amendments and correction notices.
Legal information institutes: build reproducible point-in-time law and public provenance rather than only current text snapshots.
Legal informatics researchers: study the Finland evidence, improve the evidence model, and compare jurisdiction source regimes.
Civic infrastructure groups: turn replay-vs-witness divergence into public accountability tooling.
Legal technology teams: use typed legal text-state as a provenance substrate below search, analytics, compliance, and AI layers.
Standards and linked-data communities: connect Akoma Ntoso, ELI, versioning, and source-pathology workflows to executable replay.

Good first work packages

Lane	Review outcome	Available project context
Source-first frontend	Advance Japan, South Korea, Poland, Switzerland, or another source regime from acquisition evidence toward a bounded evaluation set.	Provide source access, local authority knowledge, and a named next technical gate.
Consolidation review	Compare a pinned transition corpus with an official or editorial surface and classify each difference.	Provide source witnesses, comparison-surface semantics, and local review.
Publication adapter	Connect one versioned drafting or publication export to read-only target, reference, temporal, and mutation-boundary checks.	Define the export contract and which findings block publication.
Evidence review	Reproduce a declared case, challenge its strongest alternative explanation, and record a disposition.	Use the review protocol and preserve the inspected software and source snapshots.
Public artifacts and docs	Improve the dossier, checker walkthrough, or documentation for a specific reader without broadening the claim.	Review copy and test every linked artifact against the declared snapshot.

First contribution

Choose one bounded owner and phase. Name a source lane, operation family, evidence artifact, or documentation task rather than taking on a whole jurisdiction.
Pin the working context. Record the inspected software and source snapshots, claim ceiling, and the command or test that should remain reproducible.
Add one fixture and one failure path. Demonstrate the intended behavior and preserve a blocked, residual, or invalid case instead of silently repairing it.
Run the smallest relevant check. Start with the repository’s focused test or evidence-pack command, then run the broader CI gate appropriate to the changed area.
Open a focused issue or pull request. Include the source identity, expected disposition, observed result, and remaining limitation in the issue tracker or a pull request.

The repository getting-started guide contains the current smoke-check and archive-free Open Law commands. Treat repository branches and CLI shapes as development surfaces unless a release snapshot is named.

Operating boundary

Each adopted lane needs its own source access, local review, maintenance owner, and evidence boundary. Broader jurisdiction, hosting, and authority claims follow only from those commitments.

The default mode is continuity beside an existing workflow: frozen inputs, local or isolated processing, no production writes, and a reviewable result that can be reproduced against the named snapshot.

Contact

Email: [email protected]. To scope a reply, name the lane, jurisdiction or institution, available source surfaces, and whether you want to replicate, maintain, fund, or adopt.

← LawVM Assurance overview Jurisdictions GitHub