Decision Acceptance Scenarios

The decision is ready for maintainer acceptance when:

• DXS-AC-1: reviewers can distinguish current behavior, target architecture, activation gates, and decision status.
• DXS-AC-2: every persona maps to at least one journey with observable completion and recovery.
• DXS-AC-3: every fact type has one canonical owner, and the DX catalog has no business-judgment ownership.
• DXS-AC-4: command, diagnostic, status, side-effect, privacy, compatibility, and machine-output rules are unambiguous.
• DXS-AC-5: support slices, promotion states, evidence classes, receipts, freshness, and demotion rules are explicit.
• DXS-AC-6: documentation, localization, Preview, contribution, CI, release, support, security, and accessibility are part of the same journey system.
• DXS-AC-7: measurement remains local-first by default and preserves unobserved values.
• DXS-AC-8: each migration phase has an entry purpose, exit gate, rollback, and separate implementation-spec requirement.
• DXS-AC-9: alternatives, consequences, costs, risks, mitigations, and supersession triggers are documented.
• DXS-AC-10: the ADR and matching spec are mutually linked, the ADR index provides a stable route, and architecture/contribution entrypoints identify when this decision applies.
• DXS-AC-11: links, focused document checks, package boundaries, whitespace, and independent architecture review pass with no unresolved P1 or P2.