The architecture, its threat model, and a synthetic walkthrough of a decision that is refused. Written for evaluators who need the reasoning, the boundaries and the limits.
Each document is a public edition with a document identifier, a version, a publication date and a revision history, published as an accessible HTML page and as a PDF with a SHA-256 checksum. The documents describe the architecture of Verity Command; they do not claim certification, accreditation, compliance status or independent assessment.
Who may act, on what basis and within which boundary — and what happens when that basis cannot be established. The twelve modules, thirteen trust boundaries, the authority decision path, evidence before effect, time, leases, revocation and provenance.
SHA-256 d601b28861a41dea74ec8a72ee36db706831cbe3b7f690fb3b75f32b58650bd7
What the architecture protects, detects and cannot guarantee. Fifteen residual risks stated up front — from sensor spoofing and insiders with valid keys to traffic analysis, stale revocation and physical action outside the enforcement boundary.
SHA-256 2505ed91e06c9154aa0a830d11619be2496a65e1470c6340e1c1b49758143d59
When the correct decision is refusal. An urgent, reasonable proposal is refused for five itemized reasons; no instruction is issued and no effect occurs. Independent evidence and a human quorum then produce a narrower authorization, distributed and enforced at the edge.
SHA-256 f425a66e2b04459c6e5c6e3c7c8ae6af14c18534d9d5483b09a175f4f1ff45e3
Compare the SHA-256 checksum of a downloaded PDF with the value shown here, for example with shasum -a 256 on macOS or Linux, or certutil -hashfile <file> SHA256 on Windows. The checksum is also published as a .sha256 file next to each PDF.
The Hormuz walkthrough is also available as a twenty-step interactive experience: Explore the Hormuz reference scenario.