The daily routine: 15 minutes before the open

1The timeline

Start 20 minutes before your session. The first 5 minutes are your platform and your calendar: daily loss limit on, bracket template loaded, max size set, today's calendar rows copied and turned into an event sheet by the News agent (Guide 03). Then:

Fifteen minutes is the target once the routine is set up. Early runs take 25–30. That's normal.

2Think before the open, check during it

This is the rule that makes the team usable in real time.

All of the slow thinking (structure, rules, both sides, size) happens before the session, when nothing is moving. The output is a conditional card: "IF this happens between these times, THEN this exact order."

During the session, the system does three things:

1. Watch for the trigger on the card, with alerts at the watch zones.
2. Run the in-session check in chat D. One minute.
3. CLEAR: the execution agent places the card exactly as written, as a bracket order. BLOCK: no trade.

In-session check prompt (chat D)

Role: Risk Manager. Mode: TRADE CHECK.

Trigger seen at {hh:mm, time zone}. Card below.
Account state now: loss today {x}, trades taken {n}, losing streak {k}, open positions {none}.
Changed since the day check: {e.g. "nothing" / "a headline at 10:02, pasted below" / "tilt check now AMBER"}

{paste the trade card, unedited}

Run the TRADE CHECK from my risk sheet, all eight lines, arithmetic written out.
First line CLEAR or BLOCK. No comment on the setup. No suggestions after a BLOCK.
If the card's valid window has passed, or the time now is inside a blackout window, BLOCK.

No edits after CLEAR. If you want a different entry, stop or size, it's a new card and it gets checked again. If price moves too fast for a one-minute check, run the check as price approaches the zone and have the execution agent rest the card as a bracket order.

After a loss, the tilt check comes first. Thirty seconds in chat D (Guide 07). If it says TEAM OFF, the session is over.

No other AI during the session. No "quick question about this candle". Mid-session chat is how anchoring gets back in.

3Stop rules: when the routine ends early

The routine ends, correctly, at any of these:

• Step 1 labels the day EVENT DAY with the event inside your window, and your rules say no trading on those.
• Step 2 says NO SETUP TODAY.
• Step 4: the tilt check or the day check says CLOSED.
• Step 6 scores every card 1.

An early end isn't a wasted morning. It's the team doing the most valuable thing it does: staying out of days your own rules say to skip. Log it in the journal as a row with took_trade = N.

4After the session: five minutes

• Run the debrief on every card, taken or not (Guide 08). It sets the card beside the fills and returns MATCH or DEVIATION line by line.
• Copy its journal fields into the row: rules_followed, rule_broken, exit_reason.
• Save the memo (or paste it into the notes column).

That's it. The deeper look happens once a week (Guide 08).

5Short days: the fast team

Some mornings there are only five minutes. The fast team runs every role in one reply, in one chat.

Role: Fast team. Play each seat in order, under its own header, in its own format, and keep each seat in its lane.

Inputs:
- Attached: {screenshots, higher timeframe first, labelled}
- Calendar rows pasted by me: {rows with times and time zone, or "none pasted"}
- Account state: loss today {x}, trades taken {n}, losing streak {k}, state {1–5}.
- Scenario under review: {one line}

You may not, in any seat: invent a price, an event or a number; tell me to buy or sell; praise the plan; let a later seat be softened by an earlier one.

1. NEWS TEAM: events from the pasted rows only, INSIDE or OUTSIDE my session window, and the blackout windows from my news rule.
2. ANALYST: structure per timeframe, up to 3 key levels (tagged chart/data), regime label.
3. RESEARCHER: my setup's context rules, PASS / FAIL / CAN'T TELL each, with evidence. If a no-trade condition is met, stop here and write NO SETUP TODAY.
4. BULL: up to 2 reasons from sections 1–3, and the strongest point against.
5. BEAR: up to 3 points from sections 1–3, and what would prove the Bear wrong. Write this as if section 4 did not exist.
6. RISK MANAGER: DAY CHECK from my risk sheet and the account state only, as if sections 2–5 did not exist. TEAM ON or OFF, risk budget, trades left, blackout windows.
7. TRADER: one conditional trade card inside the budget, with the size maths written out, rounded down, bracket order, valid window.
8. DECIDER: score 1–5 from the rubric in the team setup, quoting the rubric line, and a TAKE IF TRIGGERED or PASS line for the execution agent.

Before you send: check that every price is tagged, the size maths recomputes, the score quotes a rubric line, and the verdict line follows the rubric.

It's weaker: the Bear has read the Bull and the Risk Manager has heard the story. Use it as a fallback. The in-session check still runs in its own clean chat D.

6Optional: schedule a pre-brief

If your tool can run a saved prompt at a set time, schedule a pre-brief for 30 minutes before your session. A scheduled task can't see your chart or your calendar, so keep it to what it can read: your rules, this week's change and your checklist. It doesn't replace the event sheet. The scheduled prompt is in the daily routine template (Guide 16). Check your tool's current help pages for how scheduling works.