cyb50-quant/research/dragon/v2/openspec/changes/rc1-layered-governed-optimization/tasks.md

1. Foundation And Guardrails

• 1.1 Freeze RC1 governance boundary and document branch-role constraints.
• 1.2 Add structured reason types, decision types, and reason catalog mapping.
• 1.3 Build RC1 golden baseline manifest with release-window summary and core hashes.
• 1.4 Add baseline tests for golden-hash regression and reason mapping coverage.
• 1.5 Run signal-pipeline smoke replay to ensure compatibility path remains runnable.

2. Layered Rule-Engine Refactor

• 2.1 Add dragon_rule_engine_v2.py orchestrator with explicit core -> secondary -> bridge evaluation order.
• 2.2 Extract core rules into dragon_rules_core.py without behavior drift.
• 2.3 Extract secondary rules into dragon_rules_secondary.py without behavior drift.
• 2.4 Extract bridge/compatibility rules into dragon_rules_bridge.py without behavior drift.
• 2.5 Keep dragon_strategy.py as compatibility facade and rerun golden regression.

3. Structured State Migration

• 3.1 Add structured context fields (entry_*, last_real_sell_*, bridge flags).
• 3.2 Migrate high-risk string-coupled control paths (predictive_*, pending chains) to structured fields.
• 3.3 Block new direct prefix-based control checks in refactored modules.
• 3.4 Verify no-silent-path-change for compatibility mode.

4. Weak-Family Branch Experiments

• 4.1 Create dedicated research branch for weak-family optimization (do not modify RC1 directly).
• 4.2 Implement subtype/confirmation redesign for deep_oversold_* in experiment branch.
• 4.3 Isolate predictive_* as bridge-only family and evaluate structure-preservation cost.
• 4.4 Run added/removed trade attribution pack versus RC1 baseline.
• 4.5 Run execution-stress replay before any promotion recommendation.

5. Test And Reporting Expansion

• 5.1 Add test_no_silent_path_change.py for compatibility-preserving refactors.
• 5.2 Add bridge chain regression tests for split-chain behavior.
• 5.3 Add weak-family path tests for subtype/pending transitions.
• 5.4 Add layered PnL attribution output (core/secondary/bridge) and migration audit note.
• 5.5 Re-run full suite and publish acceptance summary.