Markdown for LLMs

Reference

The source Markdown for this article. Copy it into your assistant or download it as a text file.

# Reference

Every command of the published tool, with its one-line form. The table
is built from the binary's own list — it holds no hand-written rows —
and `law --help` carries every flag behind each line. The same list as
JSON is one call away: `law help --json`.

## Project

| Command | Usage | What it does |
|---|---|---|
| `law init` | `law init <dir> [--name <package>] [--template case\|package] [--json]` | a new case folder or canon package |
| `law add` | `law add <name>[@<version>] \| <file.arxo> [--project <dir>] [--registry <ID=LOCATION>]… [--dry-run] [--json]` | pin a dependency in law.lock and install its bytes |
| `law install` | `law install [--from <file.arxo>] [--project <dir>] [--registry <ID=LOCATION>]… [--offline] [--dry-run] [--recover] [--json]` | restore deps/ from law.lock |
| `law update` | `law update <name>[@<version>] [--project <dir>] [--registry <ID=LOCATION>]… [--dry-run] [--replay <dir>] [--json]` | move a pin, replaying saved answers with --replay |
| `law outdated` | `law outdated [--project <dir>] [--registry <ID=LOCATION>]… [--json]` | pinned vs published versions; the lock is untouched |

## Container

| Command | Usage | What it does |
|---|---|---|
| `law pack` | `law pack --out <dir\|file.arxo> \| --answers … \| --runs … [--project <dir>] [--json]` | release artifact: a directory or a portable .arxo container |
| `law unpack` | `law unpack <file.arxo> --out <dir> [--json]` | check and expand a container tree |
| `law inspect` | `law inspect <document.json\|request.json\|file.arxo> […]` | a saved evaluation document, or a container's contents |
| `law key` | `law key new --out <file>` | a new Ed25519 signing key |
| `law sign` | `law sign <file.arxo> --key <file> [--role publisher\|executor]` | sign a container |
| `law publish` | `law publish <artifact> (--registry <ID>=<dir> \| --candidate <manifest.json> --bytes <dir>) [--json]` | publish into a registry directory or prepare a candidate |

## Ask

| Command | Usage | What it does |
|---|---|---|
| `law ask` | `law ask [<case>] (--query … \| --query-json <file> \| --card <id>) [--out <dir>] [--format json\|text\|brief]` | a question to a case; --out saves the evaluation |
| `law case` | `law case questions\|check\|diff\|document\|facts … [--json]` | questions, facts with provenance, documents, diffs |
| `law eval` | `law eval <dir\|file.arxo> [--answer <id>] [--out <dir>]` | replay a saved evaluation |

## Check

| Command | Usage | What it does |
|---|---|---|
| `law types` | `law types <package> [--out <file>]` | CLIR .d.ts declarations of a package |
| `law fix` | `law fix imports [<package> \| --workspace <root> \| --changed <revision>] [--check] [--json]` | use self::{…} blocks from the resolution journal |
| `law test` | `law test [<package>] [--family <f>]… [--file <path>]… [--grep <substring>] [--json]` | the package's declared scenarios over the law.lock world |
| `law audit` | `law audit [<package>] [--profile static] [--clir <dir>] [--min-bytes <N>] [--json]` | formalization measure of a package; executes no cases |

## Serve

| Command | Usage | What it does |
|---|---|---|
| `law serve` | `law serve --world <dir\|profile.json> (--journal <dir> \| --no-journal) [--host <address>] [--port <N>]` | pinned-world HTTP service: POST /v1/ask |
| `law replay-record` | `law replay-record --world <dir> --journal <dir> [--decision <id>]… [--json]` | replay the decision journal |
| `law check-file` | `law check-file --world <dir> --template <template> --questions <json> --input <csv\|jsonl> --out <dir>` | batch check of a file of cases |

## Engine

| Command | Usage | What it does |
|---|---|---|
| `law engine` | `law engine <command> …` | low-level engine commands |
| `law version` | `law version [--json]` | tool version, semantics lines, binary hash |

## Where next

- The interactive session, `law shell`, is not in the published tool yet:
  [Shell](/cli/shell/).
- `ask`, `case` and `eval` end in an evaluation document: [How to read
  an answer](/guide/reading-an-answer/).
- `serve` answers over HTTP with the same documents: the [Fact
  protocol](/protocols/fact-protocol/) for what goes in, the [Decision
  protocol](/protocols/decision-protocol/) for what comes back.
- `engine check` reports diagnostic codes: every code is explained under
  [Diagnostics](/diagnostics/).
- Questions about the model itself — rules, predicates, sources — belong
  to [LawQL](/lawql/), not to this table.