Grace

A prompt you cannot verify is not infrastructure.

Grace is the coordination layer for Verifiable Agentic Prompt Architecture. Prompts stop being strings pasted between tools and become addressable units: stratt://shared/rule/never-fabricate-citations@0.1.0 has a type, a domain, a version and a fingerprint you can recompute. When a unit changes, the fingerprint stops matching, and the change is visible rather than assumed. Everything else here follows from that one property.

Recompute stratt://shared/rule/never-fabricate-citations@0.1.0

This runs in your browser. It fetches the unit's source, canonicalises it under stratt-canonical-v1, hashes it with BLAKE3, and compares the result to the digest the unit declares. Nothing here is precomputed. Press a variant to run it: the verifier is 105KB and is fetched only when you ask for it.

Unmodified Alter one character Reformat whitespace

Declared

fetching…

Computed

fetching…

Recomputing…

Show the canonical form that was hashed

…

Three surfaces

Protocol

The unit model, the five SPEC layers, fingerprints and failure modes. Start here if you want to know what the thing actually claims.

Registry

Every unit in the corpus, addressable and fingerprinted. Generated from the source repository at build time, never transcribed.

Ledger

Every load-bearing claim in this repository is ratified in a numbered decision, and superseded by a later one rather than edited. Including the claims later proved wrong: DEC-0016 recorded that all four domains sat with a single registrar, on an attestation nobody had checked. DEC-0019 read the registrar and found two.

Why verification, and not trust

An agent system fails quietly. A prompt drifts, a council roster changes, a downstream document keeps asserting the old shape, and nothing surfaces until the output is wrong in a way somebody notices. The usual answer is discipline, and discipline decays.

Grace’s answer is mechanical. Units carry fingerprints. Claims about other repositories carry a derivation path and a read date. Decisions are appended, never edited: a decision that turns out to be wrong is superseded by a later one, and both stay readable. Drift-watches work differently and deliberately so, because a watch is a numbered invariant rather than a record: its number is never reused, and when a watch is disproved it is annotated where it stands with the evidence that disproved it. The register of things this project has got wrong is published on the same footing as the register of things it has got right, because a verification system that only records its successes has not been verified.

Read one unit, recompute its fingerprint, then read the specification that governs it.