Guide

Stop adding size after a loss day

After a session that hits the sleeve’s daily loss (or a defined loss streak), do not add size or open new risk until a written reset GO — revenge sizing and “make it back” are the failure mode. Pair it with cap daily loss before session, size from sleeve not from hope, no averaging down without a new thesis, write GO before scale-up, and journal every override.

By Agent Lane Editorial · Page dated 27 September 2026

Answer first

After a session that hits the sleeve’s daily loss (or a defined loss streak): freeze adds and new risk until a written reset GO on the named plan. Do not revenge-size or “make it back.” Enforce at review in the official venue UI. Agent Lane publishes the checklist. We do not place trades, hold wallets, invent broker UI, or run your agents.

What this page is

A short operator guide for the loss-day cool-down on the shield — stop adding size after a loss day — so a hit daily stop (or streak) freezes new size and new risk until a written reset GO, not until hope returns. Pair it with cap daily loss before session, size from sleeve not from hope, no averaging down without a new thesis, write GO before scale-up, journal every override, never skip review before place, and the shared-box checklist.

We are a publisher, not a trading desk. Product screens change; read balances and positions on the official page. We do not invent loss-day dashboards or Agentic menus. You write the stop and the reset GO, and enforce them at review.

Loss-day cool-down in plain terms

• Stop trigger — sleeve daily loss hit, and/or a defined loss streak on the named plan — cap daily loss before session.
• Freeze — no larger tickets, no averaging down, no new names or strategies until a written reset GO — size from sleeve not from hope, no averaging down without a new thesis.
• Reset GO — what must be true before new risk (flat/reduced, journaled review, same sleeve rules, dry-run if novelty) — write GO before scale-up, journal every override.
• Not a reset — “make it back,” chat confidence, FOMO, or a green tick after the red day.

Why revenge sizing is the failure mode

• Loss hit → larger tickets. “Make it back” tempts size past sleeve rules exactly when judgment is worst — size from sleeve not from hope, never skip review before place.
• Averaging down without a new thesis. Adding to a loser after the daily stop is still add-size without a written plan — no averaging down without a new thesis.
• New risk while cool-down should be on. Opening a new name or strategy to erase the red day blurs P&L and kills — one strategy, one sleeve, name the strategy before connect.
• Scale-up after a red day without GO. Raising size or leverage to recover is not a scale-up GO — write GO before scale-up, cap daily loss before session.

Where it sits in the shield stack

1. Cap daily loss before session — the stop number that can fire the cool-down.
2. Size from sleeve not from hope — ticket size under current sleeve rules (not hope).
3. No averaging down without a new thesis — no add-size inside a losing thesis.
4. Stop adding size after a loss day — freeze new size and new risk until a written reset GO.
5. Write GO before scale-up — only path to raise limits later (not to “make it back”).
6. Journal every override — record the stop, reset GO, and any early re-open.
7. Never skip review before place — enforce the cool-down in the venue UI.

Healthy flow: written daily loss / streak → stop fires → freeze adds and new risk → written reset GO before next risk → size still from sleeve → journal stop/reset/overrides → review enforces. Skip the cool-down and a hit loss limit will not stop revenge sizing.

How to run stop adding size after a loss day

1. Write the loss-day / streak stop on the named plan. Pair with cap daily loss before session and name the strategy before connect. No invented UI.
2. When the stop fires, freeze adds and new risk. Confirm P&L and positions in the broker, not chat.
3. Do not treat “make it back” as permission. Size from sleeve rules; no averaging down without a new thesis.
4. Write a reset GO before the next risk. Flat/reduced, journaled review, same sleeve rules; novelty needs dry run before first live place. Raising limits needs write GO before scale-up.
5. Enforce at review in the official venue UI. Never skip review before place; large places still get the two-person rule.
6. Journal the stop, reset GO, and any override; honor session end. Journal every override; log session end checklist; empty the sleeve overnight if idle.

Practical checklist

• Loss-day / streak stop written on the named plan with the daily loss cap.
• When stop fires: no adds, no new risk until reset GO.
• “Make it back” is not a GO.
• Size still from sleeve rules — not hope or revenge.
• No averaging down without a new written thesis.
• Reset GO written before the next risk (and scale-up GO if limits rise).
• Stop, reset GO, and overrides journaled.
• Review enforces the cool-down in the official venue UI.
• No invented UI. Official screens and your notes; you enforce.
• Shared-box pass. Who can approve a reset GO on a shared computer — see shared-box.

Brokerage path: Shield brokerage spend. On-chain pay: Shield crypto spend.

What Agent Lane does not do here

• We do not place trades, preview your orders, or babysit your agents.
• We do not hold your funds, run a hot wallet, or settle payments.
• We do not invent loss-day dashboards, revenge menus, or Agentic click-paths.
• We do not set your daily loss, streak rules, or reset GO, or claim a product that auto-resets for you.

Related guides

• No new risk after session end
• Cap daily loss before session
• Size from sleeve not from hope
• No averaging down without a new thesis
• Write GO before scale-up
• Journal every override
• Never skip review before place
• Name the strategy before connect
• One strategy, one sleeve
• Confirm fills in the broker, not chat
• Fund the session ceiling
• Two-person rule for large places
• Dry run before first live place
• Paper before live, same rules
• Log session end checklist
• Session time-box
• Empty the sleeve overnight
• Write invalidation before entry
• Reject duplicate place same thesis
• Confirm symbol before place
• No scale-in without GO
• Flatten all before connector revoke
• One order per idea until fill
• No place while unconfirmed fill
• Write max loss before entry
• Shared-box and connector checklist
• Shield brokerage spend
• Shield crypto spend

FAQ

What does stop adding size after a loss day mean?

It means: after a session that hits the sleeve’s daily loss (or a defined loss streak), do not add size or open new risk until a written reset GO. Revenge sizing and “make it back” are the failure mode. Pair with cap daily loss before session, size from sleeve not from hope, no averaging down without a new thesis, write GO before scale-up, and journal every override.

What counts as the stop trigger?

The sleeve’s written daily loss hit, and/or a defined loss streak you already wrote on the named plan. When either fires, new risk and size adds are off until a written reset GO.

Do I invent a loss-day broker UI?

No. Write the stop and reset GO on the named plan and enforce them at review before place. Use official venue balances and positions. Agent Lane does not invent loss-day dashboards, revenge menus, or Agentic click-paths.

Why is revenge sizing the failure mode?

A hit loss limit tempts larger tickets, averaging down, or new risk to “make it back.” Size then drifts past sleeve rules exactly when judgment is worst and the daily stop already said stop.

Does this replace cap daily loss or write GO before scale-up?

No. Cap daily loss is the session stop number. Stop adding size after a loss day is the cool-down after that stop (or streak) fires. Write GO before scale-up is the gate before limits change upward. Journal every override records deliberate exceptions. You need the stack.

Who writes the reset GO?

You do. Write what must be true before new risk (flat day, journaled review, same sleeve rules, dry-run if novelty). Agent Lane does not prescribe magic numbers or claim a product that auto-resets for you.

Where do I apply this next?

Set the stop: cap daily loss before session. Size under current rules: size from sleeve not from hope. No averaging down without a new thesis. After loss day/streak: no new size or risk until written reset GO. Scale later: write GO before scale-up. Any override: journal. Agent Lane publishes the checklist; we do not place trades or invent broker UI.

Next steps

Before an agent touches real money, review every order before it is placed, shield your brokerage account, and map the trading-agent options. Or browse all Agent Lane guides.