canon-implementation

To implement changes with mutation bounds, author a canonical implementation brief and start a governed run to generate a bounded, auditable implementation packet. This enforces preflight checks and requires system-context existing to ensure safe, aligned modifications.

A governed implementation run is a structured workflow that produces bounded, auditable implementation packets for existing systems. You need it when applying changes that require explicit task mapping, mutation bounds, and completion evidence to maintain strict system governance.

To structure an implementation brief for a governed run, author a canonical document with required sections including Task Mapping, Bounded Changes, Mutation Bounds, and Completion Evidence. This canonical body drives the packet generation and enforces preflight validation.

Yes, system-context existing is strictly required to start the implementation workflow. The governed run enforces preflight checks that validate the existing system context before binding and processing any implementation brief.

Bounded work limits implementation packets to explicitly defined mutation bounds, preventing unscoped system modifications. You should not use this approach for unbounded exploratory changes or tasks that lack a canonical implementation brief with explicit task mapping and completion evidence.

The best way to enforce preflight and validation checks is using a governed run workflow that requires a canonical implementation brief. This ensures tasks are properly scoped, safe, and aligned to the existing system context before authoring the final implementation packet.