Everything PRAE publishes, in one place.

Install

npm install -g prae-cli                 # the prae command
npm install prae-gate                    # the gate, loaded by the agent harness as a plugin
prae check ./org.prae.json               # validate a policy pack
prae explain ./org.prae.json write path=/etc/hosts
prae console ./ledger.jsonl --out ./console --serve   # the console, and its record API on localhost

The CLI

• prae check — a policy pack against the schema; prae test runs it against security invariants.
• prae explain — why a call is allowed, held or refused, rule by rule.
• prae verify — a decision ledger's hash chain and signatures, offline; prae report renders it.
• prae console — the console as static pages from a ledger, and with --serve its record API on localhost.
• prae mcp — an MCP server over stdio: gated filesystem access for any MCP client, every call judged and sealed.

The API

prae console --serve exposes a JSON API on localhost: the record, the ledger and its verification. The Command Center server adds same-origin mutations — signed with the operator key — for answering a held call and steering a fleet; it ships with the Command Center today, not in prae-cli. Both are described in /openapi.json, with an operationId, a description and typed schemas on every operation, and JSON error bodies throughout.

Policy packs

A pack is a JSON document: rules over tools, paths, commands, data and approvals, each with an effect (allow, require approval, refuse) and a reason the operator reads. Packs can expire, can be signed, and layer: a built-in baseline, your organisation's rules, and a fleet steer an operator applies at runtime. The packs view shows a real one; the playground judges calls against one in your browser.