The launch checklist: a memory gate, not an analysis tool.

The problem it solves

Pre-entry is when competence is least available.

The moment before execution is uniquely hostile to thoroughness: a setup is confirming, price is moving, and the operator's attention has collapsed onto the opportunity. This is precisely when the routine verifications — is there news in twenty minutes, is the spread normal, is this pair approved, did the swap cost get considered, is there actually a cycle slot free — are most likely to be skipped, and skipping any one of them occasionally produces the kind of loss that has nothing to do with edge. The checklist is the institutional answer: externalize the memory, sequence the checks, and make clearance a condition of execution. It's not meant to perform deep analysis. It's meant to make forgetting structurally impossible.

What it verifies

The inventory: conditions, authority, and mechanics.

The checklist's items sort into three families. Environmental conditions: session validity, approved asset, news danger, spread and liquidity, ATR regime state. Authority confirmation: current gate and drawdown state, throttle-approved risk for this tier, an open cycle slot, open-exposure capacity — the checklist doesn't compute any of these, it confirms the operator has consulted the modules that do. And execution mechanics: branch selected before entry, exit model matched to the branch, stop logic and volatility distance verified, position size computed, commission and swap exposure understood, and the final unglamorous question — is this loss, at this size, genuinely acceptable? Every item is a look-up or a confirmation. None is a judgment call, which is exactly why the list can be completed under pressure.

The asymmetry

It can block a trade; it can never authorize risk.

The checklist's authority is deliberately one-directional, and the architecture manual states it exactly: it can block a trade but cannot authorize risk beyond throttle. A hard failure — news window, restricted gate, no slot, size above the authorized average — stops the trade regardless of how good the setup looks. But a perfectly cleared checklist grants nothing beyond permission to proceed at the already-authorized size: twenty green checkmarks do not add a tier, expand a pool, or upgrade conviction into capital. This asymmetry is the same shape as the whole system's — protective directions bind, permissive directions don't — applied at the smallest scale. The checklist is a brake pedal with no accelerator, on purpose.

• A cleared checklist means 'nothing forbids this trade at this size' — never 'this trade deserves more.'
• Checklist enthusiasm is explicitly listed among the things the throttle must not be overridden by.
• The block is the product: one prevented hard-failure trade per quarter pays for every clearance ritual in between.

Performing versus using

The failure mode is theatrical compliance.

A checklist degrades in a predictable way: familiarity turns verification into recitation, and the operator starts marking items from expectation rather than observation — the spread is 'always fine,' the news calendar was 'checked this morning,' the swap 'doesn't matter on this pair.' The defense is structural, not motivational. Each item names a concrete look-up, so honest completion has a physical referent: the calendar was opened, the console was consulted, the size was computed. And the capture document closes the loop — a trade that fails in a way a checklist item should have caught leaves a visible reconciliation gap on Saturday, which turns theatrical compliance into a logged adherence finding. The checklist polices the trade; the record polices the checklist.

The key idea

The humblest module in the system, and among the highest-value.

Nothing in the checklist is sophisticated, and that's the design: it delivers coverage, not intelligence, at the exact moment intelligence is least reliable. Its blocked trades never appear on any dashboard — prevented disasters leave no evidence — but a hard failure caught at the gate is worth more than most weeks of clean analytics. In a system built on the premise that discipline fails at predictable moments, the checklist is stationed at the most predictable moment of all.