spec-sync

Propagating specification changes across project documentation requires classifying the change type and enumerating all impacted documents via a propagation matrix to generate consistent update proposals.

A propagation matrix for document consistency checks is a reference framework that comprehensively lists impacted documents and explicitly states update or no-update decisions for each file.

Keeping banned-word and UX sequence updates synchronized involves running integrity checks that validate banned-word compliance, UX ordering consistency, and Constitution alignment across the documentation set.

Spec-sync requires layer-aware impact routing following Layer 1, 2, and 3 rules to separate warnings, proposals with approvers, and auto-updatable areas during document synchronization.

You need a pre-review for API and DB design modifications when changes are classified as P5, triggering a security-sensitive-change-review to ensure safe specification propagation.

Automated specification propagation is limited by layer design boundaries, restricting auto-updates to safe areas while enforcing manual approvals and integrity checks for conflicting or security-sensitive changes.