Extend Add Features To Existing Systems With Canon Constraints

To extend existing systems safely, align feature additions with established PATTERNS and VALIDATION invariants before implementation. This prevents non-compliant changes and ensures new features do not introduce regressions across modules.

Canon constraints are governance requirements enforcing canonical naming, structure, and terminology based on PATTERNS and CONCEPT documentation. They ensure system extensions maintain compliance and preserve established behaviors across modules.

Document health updates by recording observable effects in BEHAVIORS and updating HEALTH signals to reflect system changes. This maintains the documentation chain required for governance verification across modules.

The process involves understanding the current state, verifying fit against constraints, implementing with explicit canon naming, and updating the documentation chain. This structured approach satisfies governance requirements and prevents non-compliant changes.

Yes, canon constraints apply to feature additions of any scale across modules. The Skill verifies alignment with PATTERNS, VALIDATION, BEHAVIORS, and HEALTH regardless of feature size to maintain system governance and prevent regressions.

Feature extensions fail governance validation when they violate canon constraints, use non-compliant naming, or break VALIDATION invariants. Verifying alignment with PATTERNS and updating HEALTH documentation prevents these failures.