craft

Production-ready code fixes outside the change request lifecycle require applying directive execution principles and architecture boundaries to implement features, review violations, or debug tests without tracking changes in the CR pipeline. Provide an ad-hoc task description to execute engineering work directly.

Refactoring code for compliance while preserving behavior relies on strict layer boundaries and bundled references to bring existing code back into compliance. The process applies architecture principles to adjust code structure without altering functional outputs or entering the CR lifecycle.

Reviewing existing code for security issues and violations without a tracked change request is supported for ad-hoc engineering tasks. The review applies directive execution principles to identify bugs and violations across projects while operating entirely outside the CR lifecycle.

Debugging failing tests across multiple projects outside the standard CR pipeline involves executing focused engineering tasks using bundled references and architecture principles. This approach cracks hard bugs directly without tracking changes or requiring a formal change request lifecycle entry.

Ad-hoc code refactoring for production bug fixes maintains strict layer boundaries by following architecture principles throughout the debugging or implementation process. This ensures code stays compliant structurally while executing directive-based fixes outside the CR lifecycle.

Ad-hoc engineering tasks for code implementation should not be used when your workflow requires formal change tracking, lifecycle management, or CR pipeline integration. This approach specifically skips change tracking, making it unsuitable for tasks needing strict lifecycle audit trails.