ADR 0058: Verified release composition preserves constituent authority

• Status: Accepted
• Date: 2026-09-10

Context

ADR 0052 deliberately requires complete workspace source authority. Independently authored ordinary workloads are not part of that source. A single immutable publication must not weaken that invariant or assign dbt authority by filename.

Decision

Introduce the explicit dpone.release-set.v3 composition envelope. Keep native release-set.v2 and dbt wire-v2 unchanged inside a typed constituent. Bind the complete ordinary producer inventory, exact flat union, ownership and supported transport in parent identity. Preserve native bytes and verify its detached original tree using the existing complete-source verifier. Runtime resolves the selected workload's authority through the verified parent/constituent binding.

Require already compact native input in the initial scope; the existing public materializer provides that transformation. Only semantically empty ordinary connection projections can use RuntimeConnectionContext transport. Register all source sidecars in delivery inventory and apply aggregate parent budgets.

Explicitly block composition activation until physical admission covers every constituent. Delivery, signatures and offline source checks cannot grant SQL or activation authority. Existing dbt-only mirror/evidence producers reject this outer envelope until they support parent-scoped evidence.

Consequences

Old readers reject v3. Current v1/v2 consumers retain their contracts. Users upgrade readers first and regenerate from complete authoring inputs. Source metadata grows, but native runtime payload bytes are not duplicated. Independent DAG boundaries remain; cross-constituent DAG splicing is outside this decision.

See the approved feature specification for algorithms, failure states, consumer audit, validation and migration.

Admission policy ownership

The review correction separates pure decisions from filesystem and framework adapters. These responsibilities have one canonical owner:

Contract module under dpone.contracts	Responsibility	Adapter retains
release_composition_transport	Detached descriptor pins, parent/native/subject byte binding and total byte budget	Confined acquisition, traversal, read order and repeated-byte verification
release_set_authority	Envelope support, schema-failure classification and native/composition authority decisions	Mandatory registered schema validation before authority admission
dbt_release_admission	Strict native metadata parsing, wire authority, content identity and producer compatibility	Schema checks between admission phases, complete source capture, locks and immutable publication
release_artifact_metadata	Release identity and artifact path/checksum parsing	Inventory membership, actual byte reads and provider pack verification
dbt_semantic_refresh_template_binding	Native execution and pre-release/plan/run/receipt proof binding	Provider fingerprint, topology parsing and projection of verified coordinates

Existing adapters preserve public errors, validation priority, producer bytes and compatibility class exports. Projection and publication keep their distinct legacy checksum spelling rules. No policy result authorizes activation or replaces source, signature or schema admission.

Constructor/function annotations that only describe injected capabilities use TYPE_CHECKING in modules with postponed annotations. Runtime bases, constructors, type checks, dataclass field types and supported reexports remain runtime imports. Raw annotations are unchanged; consumers resolving these internal function annotations with typing.get_type_hints must supply the canonical type namespace. This does not promise compatibility for implicit resolution of incidental imports.