Skip to content
docs
Arxo ↗

LPK-E0805 — proposal history or case damaged

For LLMs5 sections

The proposal history and the lock are pinned: every write carries a content hash, and the next command re-checks the bytes against the pin before doing anything. When the bytes no longer match the pin — edited by hand, truncated, or pasted from elsewhere — the tool refuses before recording anything under a damaged history. Nothing is created or changed by the refusal.

Restoring the pinned bytes, or re-checking the syntax of the case and the lock, clears the way.

pkgtest
{"files": {"law.toml": "[package]\nname = \"demo.case\"\nversion = \"0.1.0\"\nlanguage = \"0.2\"\nnamespace = \"urn:law:demo:case\"\n\n[[cases]]\nname = \"Main\"\npath = \"main.lawcase\"\n", "main.lawcase": "language \"law.core\" version \"0.2\";\npackage demo.case version \"0.1.0\";\nnamespace \"urn:law:demo:case\";\n\ncase Main {\n}\n", "law.lock": "NOT JSON{{{", "note.txt": "hello doc\n"}, "cmd": ["case", "document", "add", "note.txt", "--as", "note1", "--type", "ghost.pkg::Thing", "--observed", "2026-01-01T00:00:00Z", "--recorded", "2026-01-02T00:00:00Z", "--project", "."], "expect": "LPK-E0805"}
pkgtest
{"files": {}, "cmd": ["init", ".", "--name", "demo.diag"]}

The tool reports this in its own wording:

Output
law: REFUSAL LPK-E0805: law.lock: expected value at line 1 column 1
→ check contentHash and .lawcase syntax before retrying

Documentation for Arxo. Writings — blog.arxo.io.

Anonymous visit counts on stats.arxo.io, no cookies.