Carry LawVM Forward
A zero-to-one proof substrate needs maintainers.
LawVM v0.1 is a proof substrate. It shows that ordinary human-written amendment streams can be compiled into auditable legal text-state at national-corpus scale.
The larger public value is in legal publishers, public institutions, source-authority experts, and domain experts turning the zero-to-one proof into durable infrastructure.
What maintainership can mean
Jurisdiction maintainer
Benchmark maintainer
Institutional adopter
Research maintainer
Maintainer
Funding partner
Who should care
- 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 maintainership lanes
| Lane | Useful outcome | Available project context |
|---|---|---|
| Finland residual review | Turn more replay-vs-Finlex divergences into classified candidate findings or LawVM bug reports. | Provide review protocol, source-witness expectations, and triage boundaries. |
| Estonia frontend | Maintain consistency verification against Riigi Teataja and grow the candidate-finding workflow carefully. | Transfer current frontend context and authority-model caveats. |
| UK frontend | Separate effects-assisted replay, version graph reconstruction, and source-first replay claims. | Explain the current workbench and where not to overclaim. |
| Nordic source acquisition | Improve Norway/Sweden source coverage and define honest replay ceilings. | Share current source-boundary notes and frontend contracts. |
| Public demo and docs | Make the compiler understandable to non-authors without weakening the technical claim. | Review copy and help avoid claims that outpace evidence. |
Maintainer boundary
LawVM will remain available and maintained enough to preserve the proof and answer serious technical questions. Broad jurisdiction completion, institutional adoption, and production-grade public infrastructure will need additional maintainers or institutional support.
The intended mode is adoption with continuity: institutions using LawVM in a real workflow should receive enough architectural context to avoid known traps and maintain the relevant lane. The goal is durable infrastructure where it is useful.
Contact
Email: elias at kunnas.com. Useful messages name the lane you care about, the jurisdiction or institution involved, the source surfaces you can access, and whether you want to replicate, maintain, fund, or adopt.