TypedStandards

Roadmap

Where the standard stands

Milestones for the Typed Standards work, at quarter granularity. They mirror the public roadmap of Civic AI Tools, the civic reference implementation of Typed Standards.

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 evidence packages

    built2026 Q2

    Analyses publish as content-addressable, cryptographically signed evidence 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 evidence system 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

    designed

    The full Typed Standards specification exists and is in pre-launch private review. It is not published here yet.

  6. Lifecycle model and composite bundles

    designed

    An event-history model for the evidence lifecycle, and composite bundles that carry a package and its attestations as one content-addressable artifact — so third-party verifiers need not call a host's separate APIs.

  7. User-signed evidence and identity tiers

    upcoming

    Moving from platform-signed to user-signed evidence with multi-signer attestations, and surfacing identity-strength tiers so readers can calibrate for themselves.

  8. 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.

  9. Formal public RFC

    upcoming

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

Typed Standards is built by Nathan Storey as a personal open-source project. This project is not affiliated with, endorsed by, or representative of Nathan's employer, the City of New York, or any government agency.