Evolution and Supersession

Review this decision when any of the following occurs:

• a remote service or telemetry path becomes part of default operation;
• host-support declarations or native evidence move to an external authority;
• multiple products consume the DX control plane and repository-local ownership no longer fits;
• CLI, MCP, desktop, or hosted service becomes the primary product route;
• a schema or evidence compatibility break cannot be handled by a new major version;
• journey metrics influence release or support policy in a way not covered here;
• the federated model repeatedly causes unresolved ownership conflicts.

A superseding ADR must identify migrated declarations, projections, receipts, compatibility windows, privacy changes, and rollback. Historical evidence and decision ids remain discoverable.