Cycle Command Console — Operating Checklist
The 12-step path from Trade_Ledger to Decision Log.
Layer 01 — The checklist
Every cycle, in order.
From the operator manual:
- Enter/update trades with dropdowns, then update Floating R and Active Risk % on opens.
- Verify Open Exposure Risk %; select week, cycle, and 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 02 — Why a fixed sequence
Order is what makes the evidence clean.
Each step depends on the ones before it: exposure must be current before the gate read means anything, and the gate must be confirmed before the throttle packet is honest. Skipping ahead — sizing before exposure is updated, deciding before warnings are read — is how stale trades contaminate a cycle's evidence.
How MARS uses this
The benchmark records the worst drawdown of every simulated path and bins them against the gate ladder. MARS reads live drawdown against these bands and against gate state together: inside the bands is expected pain; beyond the adverse bands is a structural warning that outranks any green dashboard.
How it benefits you
You get a pre-agreed definition of normal pain, decided calmly before the pain started. That single artifact prevents the two classic errors - panic de-risking inside ordinary variance, and denial when damage is genuinely abnormal. You always know which situation you are in.
Distribution of maximum drawdowns across simulated paths, overlaid on the gate zones - from Growth on the left to System Lock territory in the deep-red tail.
Layer 03 — The finish line
No cycle ends unlogged.
Step twelve is not optional: the decision and any override reason go to the log. A cycle that ends without a logged decision is a cycle that can never be audited — and unauditable cycles are where governance quietly dies.
Layer 04 — Checklist philosophy
Twelve steps, because eleven left a gap someone found.
The checklist's length is empirical: each step exists because its absence produced a real failure — a stale gate read, an unverified open-risk sum, an unlogged override. Nothing on it is ceremonial. The console treats the list as a versioned artifact: steps are added by incident and removed only when the structure they guard is retired.
The governing idea
Connected inside MARS
This module doesn't work alone.
Go deeper
Operator briefs on this territory.
Deep dive — 01
The first three steps write. Nothing is read until the fourth.
The console always answers. The checklist's opening steps decide what it is answering about.
Read the full brief →
Deep dive — 02
Three interpretation modes are selected before any result is read.
Each mode interprets the same trades differently. Pick after seeing the results and you have picked the result.
Read the full brief →
Deep dive — 03
Two typed numbers decide the gate, and one of them is remembered rather than observed.
Current equity you can look up. The peak is remembered — and everything downstream is measured from it.
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.