Development Planning Standard v1.0.0
Open standard for roadmap planning.
The WIA Roadmap Standard defines an open wire format for publishing development roadmaps as signed JSON envelopes rather than free-form prose. The format is designed to coexist with existing narrative roadmap pages: organisations continue to publish human-readable roadmaps for investors, partners, and customers, and additionally emit a parallel signed envelope stream that downstream tooling can consume without re-keying the same facts.
Free-form roadmap prose is unverifiable history. When an organisation quietly drops a previously announced milestone, the only evidence is a screenshot taken before the change, and screenshots are not durable. Signed envelopes change this: every commitment, every revision, and every drop is a signed event with a verifiable timestamp. A regulator, an investor, or a partner examining a 24-month-old commitment can verify both the original commitment and any subsequent revisions without depending on either party
milestone โ a named target with planned date, current confidence, and scopedependency โ declared dependency on a milestone (own or external)release โ a delivered milestone with version, date, and conformance evidenceprogress_update โ periodic status report against active milestonescommitment_change โ explicit revision (slip, scope change, drop)Every envelope is signed with Ed25519 over the canonical JSON form (RFC 8785 JCS) by the publishing organisation#39;s tenant key. Signatures are verifiable against the WIA-OMNI-API trust fabric, which anchors organisational identities to durable cryptographic material rather than to ephemeral DNS or OAuth credentials.
The standard does not prescribe an issue-tracker; instead, Phase 4 defines bridges to GitHub Projects, GitLab Epics, Linear, Jira, and OKR systems so that an organisation continues to use whatever planning system it already has, plus a translator that emits envelopes from that system#39;s native events.