Roadmap

Where the standard stands

Milestones for the Typed Standards work, at quarter granularity. Civic AI Tools, the civic reference implementation and the standard's first domain, keeps its own roadmap.

built

Implemented and exercised in production.

designed

A spec, decision record, or detailed plan exists; not yet built.

upcoming

Identified and scoped in concept; no committed horizon.

1. Signed record packages

   built2026 Q2

   Analyses publish as content-addressable, cryptographically signed record packages — Ed25519 signatures over canonical JSON, RFC 3161 timestamps, and a public transparency-log entry for every publish.

2. Shared verification core

   built2026 Q2

   @typedstandards/verify-core is published to npm and consumed by more than one codebase, so every verifier depends on one versioned source that cannot drift.

3. Independent verifier

   built2026 Q2

   typedstandards.org runs a standalone, publisher-agnostic verifier that any host can delegate to. Checks resolve a package's own proofs and re-run them in the reader's browser.

4. Domain-neutral standard

   built2026 Q2

   The reusable core of the system for publishing and verifying signed records carries a neutral, cross-sector name: the Typed Standards specification, the shared verification core, and this site. Civic AI Tools is the civic reference implementation.

5. Public specification

   built2026 Q3

   The Typed Standards Specification is public: a v0.1 working draft, open for external review, under CC BY 4.0. Seven revisions were tagged in the quarter, v0.1.4 through v0.1.10.

6. Lifecycle model and composite bundles

   built2026 Q3

   A record's lifecycle is a chain of signed events — withdrawn, reinstated, superseded, revised — that its bundle carries with the record. The verifier reads the status from that chain, counting an event only when its key is bound to the record's signer, and checks a bundle offline.

7. Author-held keys and third-party attestations

   built2026 Q3

   A record can be signed with a key its author holds, named by a self-certifying did:key, with no registry needed. Anyone with a bound key can sign an attestation that corroborates or contradicts another's record. The verifier states each signing key's trust status, from self-certified to listed in a registry the record names.

8. Deterministic-output profile

   built2026 Q3

   The scripted-recomputation Producer Profile records a script's run over deterministic tool output, and raw-bytes/v1 hashes a file's exact bytes (specification v0.1.9). A public AI benchmark evaluation run is signed under it as a worked example.

9. Command line

   built2026 Q3

   @typedstandards/cli signs, views and verifies records from a terminal, and signs withdrawals and attestations. It verifies each record offline before printing it.

10. Host library and template

    built2026 Q3

    @typedstandards/host-core builds what a static host serves — each record's bundle, the signing key and an index — and checks it. A template repository serves signed records from GitHub Pages with it.

11. Python and notebook publishing

    built2026 Q4

    The typedstandards package on PyPI signs, views and verifies records from Python, and publishes a record from a notebook to a GitHub Pages host as one commit.

12. Graded identity

    upcoming

    Signers bound to an identity above the pseudonymous rung — an OAuth account, an academic identifier, an institution's domain, a notary — surfaced as signals a reader can filter on, as the specification's identity ladder defines.

13. Packages that travel

    upcoming

    Interoperability extensions and registry federation, advanced only as real adopters need them — a package should remain verifiable wherever it ends up.

14. Formal public RFC

    upcoming

    live and in real use — reference implementation + one external adopter — formal public RFC review to follow, no date.