execute

Bridging execution from plan to shipped code involves automating pre-flight validation, incremental building, drift detection, and salvage handling. You initiate this by invoking execute once your aim is clear, a solution is chosen, and context is loaded.

Pre-flight checks validate aim clarity, constraints, context, scope, and success criteria before coding starts. They ensure the selected solution is fully scoped and ready for incremental building and delivery.

Drift detection during incremental building continuously compares current work against the original aim. If divergence occurs, it triggers salvage to extract learning and restart with a corrected scope or aim to maintain progress.

Yes, you can persist execution context for long-running workflows using session persistence. It optionally records execution context to .oh session files to support cross-skill handoffs and maintain continuous state.

The best way to salvage a software build when scope diverges is to extract learning from the current drift and restart with a corrected scope or aim. This maintains progress while ensuring the final shipped code aligns with requirements.

Before starting automated solution execution, you need a clear aim, a chosen solution, and loaded context. These prerequisites satisfy the pre-flight validation requirements for scope, constraints, and success criteria.