docs(governance): adopt repository trust policy

ARCHITECTURE.md

@@ -3,12 +3,12 @@ schema: aether.architecture-document/v1
 id: organization-github-architecture
 title: Ego Hygiene .github Architecture
 kind: architecture-document
-version: 0.1.0
+version: 0.2.0
 status: provisional
 owners:
   - egohygiene
 created: 2026-08-19
-updated: 2026-08-19
+updated: 2026-08-21
 governed_by:
   - architecture-architecture
 depends_on:
@@ -59,6 +59,10 @@ The diagram is conceptual. [SYSTEM.md](SYSTEM.md) remains authoritative for resp
 
 ## Dependency rules
 
+- The organization-facing [repository trust policy](TRUST_POLICY.md) defines
+  contribution attestation, signing, provenance, SBOM, exception, and staged
+  adoption requirements. Relay and Realm own implementation mechanics; this
+  repository does not copy them.
 - Sibling domain capabilities integrate through versioned public contracts, not direct access to internals.
 - Generated artifacts never become the canonical source unless an accepted decision explicitly changes ownership.
 - Provider and platform adapters depend on application ports; core behavior does not depend on a provider implementation.
@@ -68,8 +72,9 @@ The diagram is conceptual. [SYSTEM.md](SYSTEM.md) remains authoritative for resp
 ## Ecosystem interfaces
 
 - Hygiene control plane
-- Empathy baseline
-- Relay workflows
+- Empathy golden-consumer baseline
+- Relay trust and release workflows
+- Realm image evidence
 - Aether agent contracts
 
 ## Deployment and portability

DECISIONS.md

@@ -3,12 +3,12 @@ schema: aether.architecture-document/v1
 id: organization-github-decisions
 title: Ego Hygiene .github Decisions
 kind: architecture-document
-version: 0.1.0
+version: 0.2.0
 status: provisional
 owners:
   - egohygiene
 created: 2026-08-19
-updated: 2026-08-19
+updated: 2026-08-21
 governed_by:
   - architecture-decisions
 depends_on:
@@ -40,6 +40,7 @@ Do not rewrite historical context to fit current understanding. Amend a record f
 - ADR-001: Keep ecosystem architecture canonical in Hygiene
 - ADR-002: Use this repository as the organization-facing inbox and defaults surface
 - ADR-003: Avoid duplicating implementation libraries
+- ADR-004: Define trust policy before reusable enforcement
 
 ## ADR-001: Keep ecosystem architecture canonical in Hygiene
 
@@ -68,6 +69,24 @@ Do not rewrite historical context to fit current understanding. Amend a record f
 - **Consequences:** The choice improves ownership and predictability while requiring maintained contracts, validation, and migration discipline.
 - **Reconsider when:** New evidence shows that the boundary prevents standalone usefulness, safety, portability, or maintainability.
 
+## ADR-004: Define trust policy before reusable enforcement
+
+- **Status:** Accepted as the current architectural direction
+- **Date:** 2026-08-21
+- **Context:** Trust-policy issue `ORG-05` and the Relay and Realm implementation
+  issues depend on one another when policy adoption and implementation evidence
+  are treated as one step.
+- **Decision:** The organization-facing [repository trust
+  policy](TRUST_POLICY.md) defines DCO, signing, provenance, SBOM, exception,
+  and staged-adoption requirements first. Relay and artifact-producing
+  repositories implement those requirements through versioned contracts;
+  adoption evidence follows without reopening the policy decision.
+- **Consequences:** Policy requirements can be reviewed without copied workflow
+  code or false implementation claims. Repositories remain non-blocking until
+  an explicit migration state enables enforcement.
+- **Reconsider when:** The ownership boundary prevents independent policy
+  review, reusable implementation, or accurate conformance evidence.
+
 ## Open decisions
 
 - Release and compatibility policy for the first stable version.

README.md

@@ -1,2 +1,9 @@
 # .github
 🧠 Organization-wide standards, templates, and developer experience for Ego Hygiene
+
+## Organization contracts
+
+- [Repository trust policy](TRUST_POLICY.md) — DCO, signing, provenance, SBOM,
+  exceptions, and staged adoption.
+- [Organization issue routing](docs/issue-routing.md) — route work to its
+  narrowest durable owner.

SYSTEM.md

@@ -3,12 +3,12 @@ schema: aether.architecture-document/v1
 id: organization-github-system
 title: Ego Hygiene .github System
 kind: architecture-document
-version: 0.1.0
+version: 0.2.0
 status: provisional
 owners:
   - egohygiene
 created: 2026-08-19
-updated: 2026-08-19
+updated: 2026-08-21
 governed_by:
   - architecture-system
 depends_on:
@@ -34,6 +34,7 @@ This document identifies Ego Hygiene .github's logical systems and responsibilit
 | --- | --- | --- |
 | Organization profile | Target | Owns its bounded portion of the organization-facing GitHub profile, public defaults, contribution entry points, and fallback coordination surface; exposes explicit inputs, outputs, failure states, and evidence. |
 | Community health defaults | Target | Owns its bounded portion of the organization-facing GitHub profile, public defaults, contribution entry points, and fallback coordination surface; exposes explicit inputs, outputs, failure states, and evidence. |
+| Repository trust policy | Active | Defines organization-facing DCO, signing, provenance, SBOM, exception, and staged-adoption requirements while leaving reusable enforcement to Relay and artifact implementation to producing repositories. |
 | Issue and pull-request intake | Target | Owns its bounded portion of the organization-facing GitHub profile, public defaults, contribution entry points, and fallback coordination surface; exposes explicit inputs, outputs, failure states, and evidence. |
 | Agent instruction projection | Target | Owns its bounded portion of the organization-facing GitHub profile, public defaults, contribution entry points, and fallback coordination surface; exposes explicit inputs, outputs, failure states, and evidence. |
 | Coordination queue | Target | Owns its bounded portion of the organization-facing GitHub profile, public defaults, contribution entry points, and fallback coordination surface; exposes explicit inputs, outputs, failure states, and evidence. |