Risk Systems — Cycle Command Console
Closed trades are evidence. Open trades are exposure.
Reference
The benchmark models how often each tier should be used given the gate history. MARS compares live tier deployment against that expectation each review cycle, reading over-use of high tiers as aggression drift and under-use as unmonetized authority - both invisible in raw P&L.
Live risk-tier usage against benchmark expectation, T1 through T7.
Layer 01 — The core distinction
Realized proof versus active burden.
Closed trades produce realized Daily EV and Cycle P&L Direction. Open trades produce Active Risk %, open exposure, remaining capacity, and smart-throughput context. Floating R is unrealized P&L — context only, never treated as evidence.
- A clean completed cycle: all 4 trades closed, Active Risk % = 0, Final Net R entered — clean Throttle EV Input Status.
- Two closed, two open: closed trades feed preliminary evidence, but open trades prevent a clean completed-cycle EV status — the console reports Insufficient Sample honestly.
- Active Risk % means true remaining downside: reduced stop = reduced risk; break-even = zero active risk.
Layer 02 — The handoff
The Throttle_Feed transfer contract.
The console prepares a formal packet for the Throttle Control Panel: gate state, Daily EV Status, Cycle P&L Direction, Open Carryover Trades, Active Open Risk %, Floating R, Min Viable Fresh PT Risk %, and override mode. After the throttle decision, authorized pool and per-trade values round-trip back so the console can size the next cycle around open exposure.
Layer 03 — The 12-step checklist
From Trade_Ledger to Decision Log.
The manual's fast operating checklist: enter/update trades with dropdowns → update Floating R and Active Risk % on opens → verify Open Exposure Risk % → select week/cycle/modes → enter Equity Peak High and current equity, confirm Final Gate Used → read Daily EV Status and warnings → audit open exposure → copy the Throttle_Feed packet → run the throttle decision → mirror authorized values back → execute with effective sizing → log the decision and any override reason.
Layer 04 — Closed versus open
Realized evidence and live exposure are never the same number.
The console's central discipline is the separation of what has finished from what is still breathing. Closed-trade evidence — settled R, final fees, confirmed adherence — is the only input allowed to grade the cycle. Open positions are tracked as exposure, not results: their unrealized P&L is explicitly untrusted, while their stop-distance consumption is fully counted. Most spreadsheet traders blur these two; the console makes the blur structurally impossible.
Layer 05 — The boundary
The console ends where the throttle begins.
Cycle Command's final output is a clean handoff package: cycle risk consumed, pool remaining, gate context, and open-exposure summary — exactly the inputs the Throttle Control Panel needs to compute the next deployment directive. The boundary is deliberate: the console judges and accounts, the throttle sizes and instructs, and neither tool is allowed to do the other's job.
The governing idea
Use cases
Where it earns its place
- ▸Daily/cycle risk structure when weekly review alone is too slow
- ▸Preventing exposure stacking by making open-trade burden explicit before fresh deployment
- ▸Producing honest Insufficient Sample states instead of pretending incomplete cycles prove something
- ▸Feeding the Throttle Control Panel a clean, auditable evidence packet
Edge cases & failure modes
Where it can mislead
- !Treating floating R as realized evidence — the single most common console misuse.
- !Leaving Include-in-Cycle flags wrong: stale trades contaminate the current cycle's evidence.
- !Skipping the round-trip: throttle outputs not mirrored back means next-cycle smart sizing runs blind.
Inside this module
3 pages go deeper than this one.
Connected inside MARS
This module doesn't work alone.
Go deeper
Operator briefs on this territory.
Deep dive — 01
Why the operating unit is one 4-trade concurrent cycle.
Not per-trade, not per-day: why the system's atomic unit of deployment is four concurrent trades under one budget.
Read the full brief →
Deep dive — 02
Two ledgers, two truths: closed versus open cycle accounting.
Settled history and live exposure are different truths with different jobs — and blending them corrupts both.
Read the full brief →
Deep dive — 03
The handoff: what the console passes to the throttle, and in what form.
A fixed payload, a fixed direction, a fixed moment. The contract that connects cycle accounting to deployment authority.
Read the full brief →
Every module ships in the complete MARS package.
One price. Eleven workbooks, three TradingView indicators, and the full manual library — $497.