Vord

Architecture

9. Build order and roadmap

Living summary. The detailed, authoritative ordering is the implementation-arc proposal (the proposals index is here); for an open-source project the build order is the contribution roadmap.

The strategy (section 4.3; ADR-0010) is a vertical slice that proves the differentiator, then widening by risk. Trait boundaries exist from day one even where crate boundaries do not. The headline property — the Vord analog of Wyrd's commit-atomicity test — is edge-independence: a verification decision completes with the strongly-consistent core unavailable.

Each milestone cuts a tagged release under the release plan (proposal 0029): 0.x minors through M3, 1.0.0 at M4 ★ (rc-soaked, specs stamped v1 in the same cut), minors per milestone after — with support and artifact policy stated there rather than improvised at announcement time.

Three steps, two release points

  • Step 1 — prove the differentiator. M0, the walking skeleton: one auth-code+PKCE login → core issuance → a signed OIDC JWT → stateless edge verification with the core unavailable, single-tenant, all-embedded. The central claim is no longer a claim.
  • Step 2 — a real single-region issuer (→ release point). Production key custody and rotation (M1 — including the distribution key and projection freshness, ADR-0043), the revocation propagation path (M2, gated by the freshness telemetry of proposal 0012), the Forseti authorization engine (M3 — which lands the second consistency domain, the composite token, the DR ordering offset, and the admin-authz cutover), then multi-tenant/realm on a real Wyrd metadata deployment with the 500K+/tenant write-rate target under login-storm and OIDC conformance scoped to basic+config (M4 ★ — the first genuinely useful product, whose release gates include the Vör crate split, delegated admin, migration-lite, and the joint-restore runbook).
  • Step 3 — the platform and global substrate (→ release point). The identity event stream (M5), the SAML IdP (M6), provisioning and strong auth — SCIM, MFA, federation (M7), and the multi-region edge fleet with the millions-per-realm hyperscale write-rate target (M8 ★ — the global identity substrate).

Deferred-with-reserved-seats

Built later, but their hooks exist from the relevant milestone because retrofit is expensive: biscuit attenuation (ADR-0003); DPoP/PAR/FAPI token-shape seats (ADR-0014, ADR-0025); the SAML/token-exchange and amr/acr/sid seats (ADR-0017, ADR-0020, ADR-0044); the status-list reference and projection-freshness fields (ADR-0032, ADR-0043); the custom-domain iss/JWKS seat (proposal 0007); the EventSink emit-points (ADR-0022); the multi-region edge fleet (ADR-0024); the admin web UI (ADR-0021). The per-proposal attachment table lives in the arc proposal and as milestone: front-matter on each proposal.