Next Decision

Do not run a P1 implementation compare yet.

Reason:
- The strongest candidates still require PRE_HARDSTOP_SLOT or another explicit evaluation-stage decision.
- EXISTING_RUNTIME_GATE-only candidates are not supported by this dataset.
- M5/M15 volatility fields are missing from the current P0 logs, so volatility-based timing cannot be adopted from this audit.

Top plans by executable_net_effect_yen:
- 1: TA9_PROTECT_HTE_RECOVERY_BASKETCLOSE | exec_net=32760.00 | stage=POST_HEDGE_SLOT | reject=requires explicit implementation stage review
- 2: TA5_DISTANCE_HS_1500_HTE_NOT_NEAR | exec_net=20063.00 | stage=POST_HEDGE_SLOT | reject=requires explicit implementation stage review
- 3: TA4_DISTANCE_HS_1000_OUTSIDE_HTE | exec_net=14003.00 | stage=POST_HEDGE_SLOT | reject=requires explicit implementation stage review
- 4: TA3_HEDGE90_WEAK_IMPROVE_PNL60_ACCEL | exec_net=0.00 | stage=NOT_IMPLEMENTABLE | reject=no executable ClosePriorityOK candidates
- 5: TA6_PNL30_ACCEL_FLOATING_3000 | exec_net=0.00 | stage=NOT_IMPLEMENTABLE | reject=no executable ClosePriorityOK candidates

Recommended next work:
1. If exit improvement remains the priority, perform a design review for the top PRE_HARDSTOP_SLOT timing plan rather than enabling S2 as-is.
2. If priority-order changes are not acceptable, freeze exit improvement and move to Entry risk-basket exclusion / DefenseHedge position review / time-session-news filter diagnostics.
