Verifiable records
A standard for signed records you can verify yourself.
Typed Standards defines a format for publishing AI-generated answers as records — packages that carry their own cryptographic proof: a signature, a content hash, and a public trust registry. Anyone can check a package independently, without trusting the site that produced it.
Signed at the source
Every package is signed and hashed when it is produced. The signature covers the exact bytes, so any later change is detectable.
Verify independently
The verifier resolves a package's own proofs and re-checks them in your browser — it doesn't take the publisher's word for it.
Shows the math
Each check renders as it resolves: the recomputed hash, the signature result, the registry lookup. Integrity and identity — not a claim of correctness.
In plain language
Typed Standards is an open standard for independent, third-party verification of AI-generated answers. It gives someone else a cryptographically signed way to confirm that an answer is reproducible and verifiable from its inputs — without attesting that any specific answer is correct. Standardized provenance and reproducibility of AI output give others a baseline to evaluate trustworthiness independently, on their own criteria.
See the roadmap for where the standard stands.
Use it
- @typedstandards/verify-corenpm
The specification's verification checks, the same in a browser and on a server. This site's verifier runs it.
- @typedstandards/produce-corenpm
Builds and signs records and their attestations, with no I/O of its own.
- @typedstandards/clinpm
Signs, views and verifies records from a terminal.
- @typedstandards/host-corenpm
Serves signed records from a static site, and checks what it serves. A template does it on GitHub Pages.
- typedstandardsPyPI
Signs a record from Python or a notebook and publishes it to a GitHub Pages site.
Worked examples, each a public repository, show records signed, served and verified.
Civic AI Tools is the civic reference implementation and the standard's first domain. Its domain packages are @typedstandards/civic-typed-harness and @typedstandards/civic-typed-router.
Verification surfaces integrity, identity, timestamp, and transparency — whether a package is intact and who signed it. It does not judge whether the content is correct. The Typed Standards Specification is public: v0.1.12, a working draft open for external review, under CC BY 4.0.
Working on something this could serve, or want to follow along? Get in touch.