ADR index

Architecture Decision Records document important design choices and their consequences.

• ADR 0001: Layered architecture
• ADR 0002: Variant C batch manifest
• ADR 0003: Edge resolver as single source of truth
• ADR 0004: Runtime ports and bootstrap
• ADR 0005: Production runtime connectors
• ADR 0006: Authority and canonical IR
• ADR 0007: Release-set and deployment-set
• ADR 0008: Airflow parse-safe provider
• ADR 0009: Artifact delivery and cache materializer
• ADR 0010: Binding-set and credential resolvers
• ADR 0011: Canonical fingerprints
• ADR 0012: Vault runtime authentication
• ADR 0013: Reproducible rerun and retention
• ADR 0014: Route attestation as production safe-sample trust
• ADR 0015: One compiler for classic, flow, and folder authoring
• ADR 0016: Content-pinned declarative recipes
• ADR 0017: Canonical workload selection algebra
• ADR 0018: Hermetic tests stay outside the production runtime
• ADR 0019: Bounded Airflow mapping projects the dpone backfill ledger
• ADR 0020: Airflow observability correlation composes immutable and observed identity
• ADR 0021: Signed catalog bundles and closed extension conformance
• ADR 0022: Durable target commit journal and fence (Proposed)
• ADR 0023: Confined authoring transactions use atomic exchange and durable recovery
• ADR 0024: Airflow executable init-fetch uses a strict v2 wire boundary
• ADR 0025: Quality-gate authority is explicit and process-local
• ADR 0026: Digest-first runtime image certification and fail-closed GHCR promotion
• ADR 0027: Runtime connections have one logical authority
• ADR 0028: Frozen release policy and irreversible publication boundary
• ADR 0029: Canonical pipeline identity and source reference
• ADR 0030: Self-service capability projection and Studio boundary
• ADR 0031: Domain-first self-service uses canonical discovery and selection
• ADR 0032: Airflow convergence is bound to an exact activation occurrence
• ADR 0033: Airflow deployments use S3 desired-state pull
• ADR 0034: Native dbt self-service uses immutable multi-repo promotion
• ADR 0035: Production Airflow artifacts require deployment-scoped attestation
• ADR 0036: Runtime image certification v2 requires Cosign
• ADR 0037: Agent PR merge closure derives from immutable reviewed-head evidence
• ADR 0038: Nested normalization fails before mutation on lossy or ambiguous identity
• ADR 0039: Airflow activation occurrence is separate from immutable run identity
• ADR 0040: Legacy Airflow pack cache uses receipt authority and bounded generations
• ADR 0041: Airflow cache retention is a reviewed crash-safe transaction
• ADR 0042: Runtime Pod deletion requires pre-mutation evidence
• ADR 0043: Airflow retention binds recovery and approval to occurrences
• ADR 0044: User workloads vs committed .dpone system vs generated gitops
• ADR 0045: Semantic refresh uses fenced multi-boundary operations
• ADR 0046: CI shadow is diagnostic and future PR Gate authority is App-bound
• ADR 0047: Module-size debt is governed by exact non-regression caps
• ADR 0048: Exact-SHA evidence is data-only, attempt-bound, and default-deny
• ADR 0049: Release publication requires newest eligible exact-SHA provider evidence
• ADR 0050: Exact Airflow launch pins may use KPO durable task state
• ADR 0052: A dbt workspace has one complete immutable release authority
• ADR 0053: REST delivery separates intent, remote effect, and durable authority (Proposed)
• ADR 0054: REST delivery uses a resumable runtime and read-only Airflow triggers (Proposed)

• ADR 0055: REST protocol semantics are platform-owned operation profiles (Proposed)

• ADR 0056: Public snapshot debt has observable provenance

New ADRs should include status, context, decision, consequences, and links to related implementation or documentation.

• ADR 0057: Bounded-window publication and recovery authority (Accepted)

• ADR 0058: Verified release composition preserves constituent authority (Accepted)

• ADR 0059: Separate complete parent admission from native constituent authority (Accepted)

• ADR 0060: Explicit authority for isolated synthetic composition execution (Accepted)

• ADR 0061: Qualification and execution share one physical ownership journal (Accepted)

• ADR 0062: SQL Server SWITCH has an explicit activation boundary (Accepted for isolated component)

• ADR 0063: independent native stage limits