ADR-070: Scoped source evolution and explicit impact acceptance

Date: 2026-10-13 Status: Accepted (shared impact reads; local native acceptance) Author: Rômulo Febasi

Decision

Compose fresh revision adapters with a metadata-only, per-actor lineage and explicit dependency map. Filter source and consumer grants, version and environment before retrieving native consumer identities or generating recipients. Notifications deduplicate exact revisions; unknown gaps reconcile current state without fabricated history. A source change proposes review, not accepted truth.

Pin candidate/patch/native annotation review to exact upstream revision, content, access policy and mapping. Local source-derived note acceptance uses fresh adapter evidence and exact queue digest inside the native transaction; generic/MCP acceptance cannot bypass it. Retain full source/dependency citation in the accepted historical annotation. Shared source-derived publication needs a dedicated authenticated Root host workflow and remains disabled in this slice. All adapters remain upstream read-only.

Consequences and limits

Two authorized squads can see reviewable API-contract impacts through the same library/CLI/MCP surface while restricted/unrelated consumers are excluded. The lineage ledger retains no source bodies or credentials and is operational metadata, not a signed truth proof. Accepted local annotations remain historical records; fresh external passages come from the source API. Host grants must be maintained explicitly; no automatic account-membership inference, notification sending or cross-system atomic transaction is promised.

See contract and verification, ADR-049, ADR-069, SYN-327 (#312) and SYN-335 (#96).