Review Session Cockpit
Import repair should be reviewed before trusting the full coaching flow.
Readiness
9/100
Actions
6
Market Context
Observational only
Write Safety
action planning only
Cockpit actions route users to review surfaces without production broker-row writes.
Cost Policy
gross-only feedback
P/L priorities stay execution-only unless a later calibrated path says otherwise.
Market Context
observational only
Market context can explain review priority, not final execution scoring.
Next Best Actions
Fix blocking import issues
Fix the blocking import issues before saving trades.
repair
Open the repair wizard.
Check broker fixture trial
7 of 12 synthetic fixture trials pass without repair.
import
Open import trial results.
Run the guided review
Compare the saved execution replays for ABCD side by side and decide whether a same-symbol cooldown rule is needed.
review
Review the highest-priority behavior cluster.
Require Repair Before Adding Size
Detected from repeated same-symbol saved trades with risk labels or losing outcomes.
rule
Inspect rule lifecycle simulation.
Open trade replay
executions[0].side: Long trades must open with buy-side position before sell-side reductions.
replay
Open the trade and inspect entry, adds, reductions, and exit.
Check progress trend
Recent execution quality is mixed.
progress
Review quality and rule effectiveness trends.
Rule Lifecycle
Review the top rule lifecycle item inside the app.
Require Repair Before Adding Sizereview
Reduce violations for this rule in the next saved report.
Require Repair Before Adding Sizedraft
Reduce violations for this rule in the next saved report.
Repeated risky ABCD trades repeateddraft
Reduce recurrence count below the current alert threshold.
Require Repair Before Adding Sizedraft
Reduce violations for this rule in the next saved report.
Why These Items
Why broker fixture results appear
The app uses representative synthetic CSVs to verify parser, repair, and review behavior before real user imports exist.
Why repair steps appear
Repair steps are generated from parser diagnostics and import quality signals.
Why cockpit priorities appear
Cockpit actions combine import readiness, repair needs, existing review queue, and rule draft readiness.
Why rule lifecycle items appear
Rule lifecycle items are view-model simulations from repeated mistake-to-rule drafts.