implement-senior

Cross-module refactoring requires applying strict plan-boundary schemas and typed error channels to execute changes while preserving interfaces. This ensures multi-module modifications stay aligned with the approved architect plan and maintain traceability for every code change.

Plan-driven module coordination executes multi-module changes guided by an architect plan, ensuring strict scope enforcement. You need this when implementing complex features across multiple modules where preserving interfaces and maintaining traceable plan anchors for every change are required.

To enforce architect plan boundaries during a controlled refactor, implement changes strictly within the plan's scope without adding new modules or public contracts. Use traceable plan anchors for every edit to ensure no unauthorized public surface is introduced during the internal improvements.

Cross-module implementation works for private internal improvements by applying controlled refactors strictly within a single feature area. It coordinates changes across named modules while preserving interfaces and preventing the introduction of any new public contracts.

The best way to maintain traceability across multiple modules is tying every code edit to specific plan lines using traceable plan anchors. This plan-driven approach guarantees that all cross-module changes remain verifiable and aligned with the approved architect plan.

Typed error channels are required for multi-module plan enforcement to ensure controlled error propagation across modules. They maintain coordination integrity across module boundaries while preserving interfaces and strictly aligning changes with the approved architect plan.