Why Law Is Law-Shaped

4 hours ago

Law is an incrementally maintained system authored by distributed agents with partial authority over time, requiring stable fine-grained addresses for external reference.
Law is serialized as a tree (due to paper linearity) but operates as a graph due to cross-references, overrides, and dependencies across branches, statutes, and jurisdictions.
Amendments are typed operations (replace, repeal, insert, renumber, text-replace, text-repeal) with target addresses, actions, payloads, and sources, not simple text edits.
Law has multiple temporal axes, including enactment/publication time, legal effect time, and corpus observation time, often with gaps or retroactive effects.
Addressing in law converges on path-based identifiers (e.g., §12(2)) due to stable external references in hierarchical structures, similar to OIDs, filesystem paths, or ELI/FRBR.
Different jurisdictions assign varying legal authority to consolidated texts (e.g., informational in Finland, authoritative in Estonia), affecting the compiler's role as oracle or verifier.
The text layer (compiling accurate provision text) must be separated from the semantic layer (normative meaning) to enable reliable downstream analysis, as in LawVM.
LawVM models law's structural constraints: tree parsing, typed operations, path addressing, graph modeling, multi-dimensional time, and jurisdiction-agnostic core for reproducible text states.

Hasty Briefsbeta