Today's session, run like the bot would run it.

The bot isn't automated yet — so this cockpit walks the same process by hand: the account's state picks the policy, the pre-trade framework gates the open, the tracker holds the day inside the firm's limits, and the close updates the account. Everything saves locally in your browser, per day.

1 · The account → today's policy

Stage

Cushion above $50,000 ($)

Next payout #

Qualifying days banked (>$150)

Profit since last payout ($)

Best day since last payout ($)

Typical stop distance (MNQ pts)

Ruin tolerance

Set the account state and compute.

Progress to the +$2,100 floor lock

Payout readiness

2 · The three inputs — raw material before opinions

Yesterday's close

The pre-market

Economic data

3 · The four answers — blank answer, no trading

① Market context — one sentence

② Allowed setups today

Decision zones + long scenario (trigger · wrong · target · what I need to see)

Short scenario (same structure, other side)

③ Risk rules — two numbers, written, frozen

Risk per trade ($) — from the policy

Max loss for the day ($)

④ Entry & exit — before you click

For any trade I'd take: entry trigger, stop, and invalidation are written down. No stop written = no trade.

Targets ≥ 2R only; breakeven at +2R. (The bot enforces this mechanically — today I do.)

Not cleared to trade — answers incomplete.

4 · The live day — execute the plan inside the numbers

Trades

Day P&L vs the limits

5 · The close

Qualifying day (> $150 profit) — add it to the banked count above.

Cushion, profit-since-payout, and best-day updated in section 1 with today's number.

Every trade logged to TradeZella with stage + grade tags (eval / funded-grow / funded-protect + a++/a/b) — the tracking spec.

If the day stop or DLL was hit: the day ended there. No override button is the point of building one.