Overview

One binary, law, carries the whole workflow: write a canon package, check and test it, pin it into a case package, ask the case a question, and replay the saved answer. The tool answers from pinned bytes only — the same inputs give the same document — and every terminal on these pages is a recorded run of tool 0.1.1, not a sketch.

The pages

• Install — get the binary and check the version line.
• Packages and cases — one session from an empty folder to a replayed answer: a parcel tariff, a typo, the fix, the test, the packed canon, the case, the question.
• Shell — the interactive session, which the published tool does not ship yet.
• Reference — every command with its one-line form, built from the binary’s own list.

Where the details live

The command line is one surface over the same core. The rules themselves are written in the Language; what a question sends and what an answer carries is fixed by the protocols; every diagnostic code the check can report is explained under Diagnostics; questions about the model itself belong to LawQL. Readers who meet Arxo through code start with the Guide. Readers who run Arxo as a service — install, tokens, edge, journals, upgrades, backup — continue with Operate.