phase4-ablation

You can attribute main results to component contributions by orchestrating an ablation pipeline that coordinates per-variant spec deltas and code upgrades after Phase 3 evaluations are locked. This process ensures reproducible variant workflows and documented outputs for downstream handoff.

Ablation planning is needed when Phase 3 results have passed and story coherence is established. You invoke the Ablation Designer to generate a structured variant plan and issue a versioned ablation plan document.

You execute per-variant ablation workflows serially through Architect and Confirmer rounds to produce spec deltas, followed by code upgrades for changed modules while carrying forward untouched modules from Phase 3. Execution includes Analyst and Story Advisor context checkpoints.

Yes, untouched code modules from Phase 3 are carried forward during ablation. The pipeline applies Phase 4 code upgrades and fidelity checks only to changed modules, ensuring reproducible execution while preserving previously validated components.

Exit criteria for Phase 4 ablation are defined by a phase4-exit-check that verifies per-variant execution and narrative reconciliation. If the check passes, it triggers a documented handoff to Phase 5 or Phase 6.