Architecture Decision Records
Numbered records of significant decisions and why they were made. The lifecycle is
Proposed → Accepted → Superseded (ADR-0007):
a Proposed draft may be revised freely; an Accepted record is never edited, only
superseded by a later ADR that references it, and is moved to Accepted only once it
carries no unresolved [OPEN] items. Format follows the lightweight
Nygard template.
Cross-references. A reference to a Wyrd ADR is always written
Wyrd ADR-NNNN; an unprefixedADR-NNNNalways means this (Vord) repository. The two projects number independently — e.g. Wyrd ADR-0018 (reserved identity hooks) and ADR-0018 here (SCIM provisioning) are unrelated.
Index
| # | Title | Status |
|---|---|---|
| 0001 | Project name (Vord), component scheme, and founding constitution | Proposed |
| 0002 | Rust as the implementation language | Proposed |
| 0003 | Credential and token formats (spec-first) | Proposed |
| 0004 | The consistency-token contract | Proposed |
| 0005 | The revocation model | Proposed |
| 0006 | Authorization engine and the Authorizer seam |
Proposed |
| 0007 | Adopt Wyrd's governance model and the status-aware ADR lifecycle | Proposed |
| 0008 | Licensing (Apache-2.0), the DCO, and dependency-selection criteria | Proposed |
| 0009 | The admission plane — name and role (Móðguðr) | Proposed |
| 0010 | The Vör verification contract and the edge-independence property test | Proposed |
| 0011 | The principal and directory data model | Proposed |
| 0012 | The tenant and realm model | Proposed |
| 0013 | Crate and workspace structure | Proposed |
| 0014 | The OAuth 2.0 / OIDC surface and flow set | Proposed |
| 0015 | The authentication-method and credential-verification model | Proposed |
| 0016 | The login session and front-channel SSO model | Proposed |
| 0017 | SAML 2.0 IdP placement and the constitution seam | Proposed |
| 0018 | SCIM 2.0 provisioning and lifecycle | Proposed |
| 0019 | Upstream identity federation (social and external-IdP login) | Proposed |
| 0020 | MFA, step-up, WebAuthn, and passwordless | Proposed |
| 0021 | The admin / management API surface and its authorization | Proposed |
| 0022 | The identity event stream (CQRS) and the Wyrd-ADR-0018 boundary | Proposed |
| 0023 | Key rotation, JWKS publication, and multi-key lifecycle | Proposed |
| 0024 | Deployment substrate and edge topology | Proposed |
| 0025 | Standards conformance posture | Proposed |
| 0026 | The authorization store as a second consistency domain, and the composite consistency token | Proposed |
| 0027 | The threat model and the security-review discipline | Proposed |
| 0028 | Testing strategy | Proposed |
| 0029 | Extensibility: actions/hooks and the execution model | Proposed |
| 0030 | Identity governance (IGA) model | Proposed |
| 0031 | Adaptive authentication: risk signals, device trust, conditional access | Proposed |
| 0032 | Status-list freshness and replay protection | Proposed |
| 0033 | Clock and time-source trust | Proposed |
| 0034 | Right-to-erasure and crypto-shredding | Proposed |
| 0035 | Internal service-to-service trust | Proposed |
| 0036 | Key-compromise emergency response | Proposed |
| 0037 | Consent and the authorization-grant model | Proposed |
| 0038 | The OAuth client model — registration, authentication, and redirect-URI validation | Proposed |
| 0039 | The freshness and time-budget system | Proposed |
| 0040 | Backup, restore, and disaster recovery across the two consistency domains | Proposed |
| 0041 | Privacy threat model (LINDDUN) and privacy-by-design | Proposed |
| 0042 | Post-quantum cryptographic posture and migration | Proposed |
| 0043 | Projection integrity and the distribution-key hierarchy | Proposed |
| 0044 | Refresh tokens, session linkage, and logout | Proposed |
| 0045 | The group model, dynamic membership, and the groups claim | Proposed |
| 0046 | External collaboration — the guest model | Proposed |
| 0047 | Legacy-protocol and adjacent-product posture | Proposed |