Guide

Write GO before scale-up

Before you raise size, add leverage, open a second strategy, or widen the sleeve, write an explicit GO — what changes, max loss, kill criteria — do not scale on a green day alone. Pair it with size from sleeve not from hope, name the strategy before connect, dry run before first live place, two-person rule for large places, and journal every override.

By Agent Lane Editorial · Page dated 27 September 2026

Answer first

Before you raise size, add leverage, open a second strategy, or widen the sleeve: write an explicit GO on the named plan — what changes, the max loss you accept after the change, and kill criteria that stop the scaled run. A green day is not a GO. 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 scale-up gate on the shield — write GO before scale-up — so size, leverage, strategy count, and sleeve width change only after a written GO, not because P&L looked green. Pair it with size from sleeve not from hope, name the strategy before connect, dry run before first live place, two-person rule for large places, 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 scale-up dashboards or Agentic menus. You write the GO and enforce it at review.

Scale-up GO in plain terms

• What changes — higher ticket size, more leverage, a second named strategy, or a wider sleeve / higher funded ceiling.
• Max loss — the most you accept to lose after the change (trade and/or session) — pairs with cap daily loss before session and size from sleeve not from hope.
• Kill criteria — what stops the scaled run: loss hit, odd fill, time-box, error, offline, thesis break — name the strategy before connect.
• Not a GO — a green day, chat confidence, FOMO, or “it’ll keep working.”

Why green-day scale-up is the failure mode

• Winning session → larger tickets. Green P&L tempts size past written sleeve rules without a new max loss — size from sleeve not from hope, never skip review before place.
• Leverage stacks overnight risk. Adding leverage after a win without GO leaves amplified exposure you may not watch — no overnight margin without GO.
• Second strategy without a wall. Opening another play in the same sleeve blurs P&L and kills — one strategy, one sleeve, name the strategy before connect.
• Wider sleeve without rotate/prove. Raising funded ceiling or sleeve width on a green day skips rotate and dry-run brakes — rotate before you raise the balance, dry run before first live place.

Where it sits in the shield stack

1. Name the strategy before connect — written plan the GO attaches to.
2. Size from sleeve not from hope — ticket size under current sleeve rules.
3. Write GO before scale-up — explicit GO before size, leverage, second strategy, or wider sleeve.
4. Dry run before first live place — prove novelty under the new limits.
5. Two-person rule for large places — second human (or hard gate) for large size after scale.
6. Journal every override — record the GO and any mid-session exception.
7. Never skip review before place — enforce GO + sleeve rules in the venue UI before approving.

Healthy flow: named plan + current sleeve rules → write GO before any scale → dry-run novelty → review enforces GO and size rules → large places get two humans → journal the GO/overrides. Skip the GO and a green day alone will not stop oversized or over-levered places.

How to run write GO before scale-up

1. Write what would change. Higher size, more leverage, second strategy, or wider sleeve — on the named plan — name the strategy before connect. No invented UI.
2. Write max loss after the change. Cap daily loss before session; size still from sleeve rules once updated.
3. Write kill criteria. Loss hit, odd fill, time-box, error, offline, thesis break — session time-box, kill switch before travel.
4. Do not treat a green day as the GO. Scale only after the written GO exists. Second strategy needs its own sleeve — one strategy, one sleeve.
5. Enforce at review; large places get two humans. Never skip review before place; balances from the broker, not chat; two-person rule.
6. Journal the GO; dry-run novelty; honor overnight. Journal every override; dry run before first live place; no overnight margin without GO; log session end checklist.

Practical checklist

• Scale-up GO written — what changes, max loss, kill criteria on the named plan.
• Green day is not a GO.
• Current sleeve rules still apply until the GO updates them — size from sleeve.
• Second strategy gets its own sleeve / named plan — not a silent widen.
• Novelty dry-run before first live place under new limits.
• Large places — two-person rule after scale.
• GO and overrides journaled.
• No overnight margin without written GO.
• No invented UI. Official screens and your notes; you enforce.
• Shared-box pass. Who can approve a scale-up 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 scale-up dashboards, broker menus, or Agentic click-paths.
• We do not set your GO numbers, max loss, or kill criteria, or claim a product “auto-scale” feature.

Related guides

• 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
• Write invalidation before entry
• No market order without GO
• Max slippage or cancel
• One risk unit per idea
• No new risk after session end
• Size from sleeve not from hope
• Name the strategy before connect
• Dry run before first live place
• Two-person rule for large places
• Journal every override
• Never skip review before place
• One strategy, one sleeve
• Cap daily loss before session
• No overnight margin without GO
• No averaging down without a new thesis
• Rotate before you raise the balance
• Fund the session ceiling
• Confirm fills in the broker, not chat
• One venue, one agent session
• Log session end checklist
• Session time-box
• Paper before live
• Paper before live, same rules
• Stop adding size after a loss day
• Write invalidation before entry
• Reject duplicate place same thesis
• Confirm symbol before place
• Shared-box and connector checklist
• Shield brokerage spend
• Shield crypto spend

FAQ

What does write GO before scale-up mean?

It means: before you raise size, add leverage, open a second strategy, or widen the sleeve, write an explicit GO — what changes, max loss, and kill criteria. Do not scale on a green day alone. Pair with size from sleeve not from hope, name the strategy before connect, dry run before first live place, two-person rule for large places, and journal every override.

What belongs in a scale-up GO?

Written on the named plan: what changes (size, leverage, strategy count, sleeve width), the max loss you accept after the change, and kill criteria that stop the scaled run. A green P&L day is not a GO.

Do I invent a broker scale-up UI?

No. Write the GO on the named plan and enforce it at review before place. Use official venue balances and positions. Agent Lane does not invent broker dashboards, scale menus, or Agentic click-paths.

Why is green-day scale-up the failure mode?

A winning session tempts larger tickets, more leverage, a second strategy, or a wider sleeve without new written limits. Size and risk then drift past the plan while review still feels optimistic.

Does this replace size from sleeve or journal every override?

No. Size from sleeve is the ticket-size rule under current sleeve limits. Write GO before scale-up is the gate before those limits change. Journal every override records deliberate exceptions. You need the stack.

Who writes the GO and sets max loss?

You do. Write what changes, max loss, and kill criteria before you raise size or widen exposure. Agent Lane does not prescribe magic numbers or claim a product feature that scales for you.

Where do I apply this next?

Plan: name the strategy. Size under current rules: size from sleeve not from hope. Before raising size/leverage/second strategy/wider sleeve: write GO (what changes, max loss, kill criteria). Prove novelty: dry run. Large places: two-person rule. 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.