A domain PROVIDES modes to the projects that bond it — the third rung, so a component's inspection method is inherited and overridden per workspace instead of re-invented in each one
MEASURED 2026-09-05, registering a client's infrastructure in a consumer spine
A blocker declares what would show it is gone — or declares that nothing could, and names what settles it instead
MEASURED 2026-09-06, in one consumer project, in a single day: FIVE governance
A second-level domain's capability catalog lives in its provider
ADR-073 gave a bond one extension point: `capabilities`, typed as 'reference ids into the
The versioned artefact is the operation dump, not the database that indexes it
The substrate's durable state has been committed to git as a redb database
Difusión Demos Are Demonstration-Scenarios Projected From the Modes, Not a New Kind or Hand-Authored Prose
A difusión proposal asked for concrete 'con y sin ontoref' demos — each facing a
Catalog Discovery Cross-Project — Tier-2 Ops Beyond the Piloto Self-Host
ADR-029 commits the protocol to permanent tier coexistence: any project
Catalog Extensibility Beyond Rust — `kind` Discriminator on `OperationDecl` with ondaod-Pre Required for Non-Rust Kinds
ADR-024 (operations as the agent's only project-touching path) and
Secret Management Operations on the MCP Surface — Observation, Orchestration, and Permanent Exclusions
ADR-017 established that the daemon is structurally excluded from credential resolution: it has no age private key and cannot decrypt sops files. This is load-bearing — any actor with MCP access cann
8 items