cyb50-quant/research/dragon/v2/openspec/changes/execution-decoupling-rollout-governance/proposal.md

Why

The previous OpenSpec rounds isolated weak-family predicates and added layered metadata, but runtime execution is still physically embedded in dragon_strategy.py, and rollout decisions still rely on manual interpretation of multiple monitoring files. This keeps engineering risk higher than needed for RC1 forward operations.

What Changes

• Physically decouple the compatibility execution runtime loop from dragon_strategy.py into a dedicated runtime module while preserving behavior.
• Add rollout governance gates that evaluate dragon_daily_rc1_manifest.json, dragon_monitor_history.csv, and dragon_branch_divergence_log.csv into one machine-readable decision.
• Generate a rollback runbook and state artifact so forward operation has explicit freeze/fallback guidance.
• Integrate rollout governance generation into the forward observation pipeline.

Capabilities

New Capabilities

• execution-runtime-decoupling: Dedicated compatibility runtime module for event/trade loop execution.
• rollout-governance-gates: Unified rollout gate evaluation with FORWARD_OK / HOLD_AND_REVIEW / ROLLBACK_REVIEW_REQUIRED.
• rollback-runbook-artifacts: Persistent rollback procedure outputs tied to latest monitoring snapshot.

Modified Capabilities

• dragon-strategy-compatibility-facade: Delegates runtime execution to a decoupled module.
• forward-observation-governance: Automatically regenerates rollout governance artifacts on each forward run.

Impact

• Affected code: dragon_strategy.py, new execution runtime module, forward pipeline, rollout governance checker.
• Affected artifacts: dragon_rollout_state.json, dragon_rollout_governance_snapshot.csv, dragon_rollout_governance_report.md, dragon_rollout_rollback_runbook.md.
• Expected runtime impact: no intended RC1 path change; governance outputs become deterministic and reproducible.