cyb50-quant/research/dragon/v2/dragon_migration_audit.md

Dragon Migration Audit (Phase 3 Compatibility)

Scope

• phase: rc1-layered-governed-optimization
• objective: preserve RC1 behavior while introducing layered orchestration and structured state migration
• window: 2016-01-01 -> 2025-12-31

Compatibility-Preserving Moves

• Added layered orchestration modules:
  • dragon_rule_engine_v2.py
  • dragon_rules_core.py
  • dragon_rules_secondary.py
  • dragon_rules_bridge.py
• Kept dragon_strategy.py as compatibility facade and legacy behavior source.
• Added structured context metadata fields:
  • entry_reason_layer/family/code
  • last_real_sell_reason_layer/family/code
  • bridge flags for predictive and pending deep-oversold paths.
• Migrated high-risk control checks from raw string coupling to structured state in:
  • predictive reentry gate
  • post-washout gate
  • state crash followthrough gate
  • glued/dual-gold entry-family checks via _entry_reason_is(...)

New Governance Tests

• tests/test_no_silent_path_change.py
• tests/test_bridge_chain_regression.py
• tests/test_deep_oversold_pending_paths.py

Acceptance Gates

Compatibility refactors are accepted only if all pass:

1. golden core hash regression (tests/test_rc1_golden_regression.py)
2. no-silent-path-change layered-vs-legacy regression
3. bridge-chain regression checks
4. signal-pipeline smoke run

Behavior-Change Notes

• No intentional RC1 trade-path change is introduced in compatibility mode.
• Any behavior-changing weak-family optimization remains branch-isolated and must ship added/removed trade attribution.