ai-exchange/docs/AI_ICT_DoctrineKernel_PlaybookRemediationQueue_D9_2026-05-22_v1.md

AI_ICT Doctrine Kernel Playbook Remediation Queue D9 2026-05-22 v1

Scope

D9 turns failed D8 cohorts into a remediation queue. The goal is not to add any new trader-facing signal. The goal is to answer one post-backtest question:

For each failed playbook cohort, which rule family fails most often, and should the next fix start in Strategy Backtest or Study Notes?

ICT Chain Served

D9 still serves the hard mainline chain:

Range / Draw / Location -> Liquidity / Sweep / Inducement / Path -> Displacement / MSS / FVG / Retest / Session -> backtest evidence -> pre-market plan -> intraday unique focus or no-trade reason -> journal / study-notes feedback.

It sits between backtest evidence and journal / study-notes feedback. A D9 queue item is remediation evidence only. It is not a promotion gate bypass and not a live focus signal.

Product Rule

A failed D8 cohort must be reduced to:

• one dominant remediation family,
• one dominant blocker reason code,
• one primary remediation route,
• one Study Notes prompt,
• one Strategy Backtest review prompt.

The queue may route a cohort to:

• strategy_backtest first when the dominant blocker is historical quality evidence,
• study_notes first when the dominant blocker is model definition, liquidity/confirmation chain, session discipline, plan alignment, or risk boundary.

No D9 output may promote a cohort into Trader Cockpit Review Now.

Implemented Surface

Backend:

• DOCTRINE_PLAYBOOK_REMEDIATION_PHASE = D9_PLAYBOOK_REMEDIATION_QUEUE
• summarize_playbook_remediation_queue
• /trading/backtests now returns playbook_remediation_queue_summary

Batch script:

• scripts/run_backtest_batch.py now includes playbook_remediation_queue_summary in JSON output.
• CLI text output prints queued cohort count plus Strategy Backtest first versus Study Notes first.

Frontend:

• Strategy Backtest shows Playbook Remediation Queue.
• Strategy Backtest lists the top queued cohorts with the dominant remediation family and route.

Remediation Families

D9 groups dominant blockers into these families:

• backtest_quality_gate
• model_playbook_contract
• liquidity_path
• pd_array_reaction
• time_session
• trading_plan_alignment
• risk_boundary
• general_study_only

These families are then mapped into the existing Chapter 46-47 feedback classes so the queue can point back to Study Notes instead of inventing a new feedback taxonomy.

Read-Only Boundary

D9 is read-only historical analysis and remediation routing. It does not add order submission, does not change execution_allowed, does not change decision_support_ready, does not change real_live_ready, and does not loosen risk governor / trust bucket / operator confirmation protocol.

Validation Meaning

If D9 routes a cohort to strategy_backtest, the operator should inspect sample size, expectancy, profit factor, drawdown, executed-signal sufficiency, and related cohort evidence before revisiting the playbook.

If D9 routes a cohort to study_notes, the operator should tighten the model definition, confirmation chain, session rule, plan rule, or no-trade boundary before any trader-facing reconsideration.

In both cases the cohort remains study_only until D8 and D7 gates pass again.

Next Slice

D10 should turn D9 queue items into saved remediation artifacts: generate per-cohort Study Notes drafts and Strategy Backtest review prompts so the operator can close the loop without scanning raw reason codes.