Guide

No scale-in without GO

Do not scale into a winning (or open) position without a written GO that sets add size, max total risk, and invalidation — pyramid / scale-in is not free just because price moved your way. Pair it with no averaging down without a new thesis, write GO before scale-up, one risk unit per idea, size from sleeve not from hope, write invalidation before entry, and never skip review before place.

By Agent Lane Editorial · Page dated 27 September 2026

Answer first

Before any add / scale-in / pyramid on an open (often winning) position: write a GO — add size, max total risk after the add, and invalidation for the whole position. A green mark is not a GO. Enforce at review in the broker UI against sleeve rules and one risk unit. 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-in / pyramid gate on the shield — no scale-in without GO — so live connectors cannot grow an open winner on “it is working” alone. Pair it with no averaging down without a new thesis, write GO before scale-up, one risk unit per idea, size from sleeve not from hope, write invalidation before entry, never skip review before place, reject duplicate place same thesis, journal every override, and the shared-box checklist.

We are a publisher, not a trading desk. Product screens change; use official venue order tickets and your written notes. We do not invent pyramid menus or Agentic click-paths. You write the scale-in GO and enforce it at review.

No scale-in without GO in plain terms

• Add size written — exact size of the proposed add, not “a little more.”
• Max total risk — open risk + add must stay inside one risk unit and sleeve rules.
• Invalidation for the pyramid — kill line covers prior fills + the add — write invalidation before entry.
• Not a GO — a green mark, chat confidence, FOMO, or “pyramid because it is working.”

Why green-mark pyramid is the failure mode

• Winner → silent adds. Price moved your way; the agent proposes scale-in without new max total risk — one risk unit per idea, never skip review.
• Risk unit gets spent twice. Multiple adds on the same thesis quietly multiply exposure past the written unit — reject duplicate place same thesis, size from sleeve.
• Invalidation was for the first fill only. Pyramid without updating the kill line leaves you improvising exit after size grew — write invalidation before entry.
• Confused with sleeve scale-up. Raising sleeve limits is a different GO — do not treat a green day as permission for either — write GO before scale-up.

Where it sits in the shield stack

1. Write invalidation before entry — kill line before the first place.
2. One risk unit per idea — max loss for this thesis.
3. Size from sleeve not from hope — ticket size under current sleeve rules.
4. No scale-in without GO — written GO before any add on an open / winning position.
5. No averaging down without a new thesis — separate add-size gate on a loser.
6. Write GO before scale-up — sleeve/strategy limits change only after a different GO.
7. Never skip review before place — human gate enforces the scale-in GO.
8. Journal every override — record the GO and any mid-session exception.

Healthy flow: invalidation + risk unit + sleeve rules → open position → agent proposes add → write scale-in GO or do not add → review → place → confirm fills → journal. Skip the GO and a green mark alone will stack risk on the same idea.

How to run no scale-in without GO

1. Keep the open position and risk unit visible. Named thesis, open size, one risk unit, written invalidation. No invented UI.
2. Treat a green mark as not a GO. Pause any agent “add / scale-in / pyramid” until a written scale-in GO exists.
3. Write the scale-in GO. Add size, max total risk after the add, invalidation for the whole pyramid — not “it is working.” Distinct from sleeve scale-up GO and from averaging-down thesis.
4. Check against sleeve and risk unit. Add + open risk ≤ unit and sleeve rules; respect daily/session loss cap. Reject duplicate same-thesis paths — reject duplicate place.
5. Pass review before place. Never skip review; large size → two-person rule; truth in the broker UI, not chat.
6. Confirm fills; journal the GO. Journal every override; session close on log session end checklist; misfire → revoke before you debug.

Practical checklist

• Scale-in GO written — add size, max total risk, invalidation.
• Green mark is not a GO.
• Total risk inside one risk unit and sleeve rules.
• Invalidation covers the whole pyramid — not only the first fill.
• Distinct from averaging-down (loser) and sleeve scale-up (limits change).
• No duplicate same-thesis path while open risk exists.
• Review on — no standing skip for the add.
• GO and overrides journaled.
• No invented UI. Official tickets and your notes; you enforce.
• Shared-box pass. Who can approve a scale-in 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 pyramid menus, scale-in dashboards, or Agentic click-paths.
• We do not set your GO numbers, max total risk, or claim a product “no scale-in” feature.

Related guides

• One order per idea until fill
• No place while unconfirmed fill
• Write max loss before entry
• No averaging down without a new thesis
• Write GO before scale-up
• One risk unit per idea
• Size from sleeve not from hope
• Write invalidation before entry
• Never skip review before place
• Reject duplicate place same thesis
• Stop adding size after a loss day
• Journal every override
• Confirm fills in the broker, not chat
• Two-person rule for large places
• Cap daily loss before session
• Review before place
• Shared-box and connector checklist
• Shield brokerage spend
• Shield crypto spend

FAQ

What does no scale-in without GO mean?

It means: do not scale into a winning or open position without a written GO that sets add size, max total risk after the add, and invalidation for the whole pyramid. Price moving your way is not permission. Pair with no averaging down without a new thesis, write GO before scale-up, one risk unit per idea, size from sleeve not from hope, write invalidation before entry, and never skip review before place.

How is this different from no averaging down without a new thesis?

No averaging down blocks add-size on a loser unless a fresh written thesis passes. No scale-in without GO is the add-size gate on a winner or open position — pyramid is not free because price moved your way. You need both.

How is this different from write GO before scale-up?

Write GO before scale-up is the sleeve/strategy gate before you raise ticket limits, add leverage, open a second strategy, or widen the sleeve. No scale-in without GO is the per-position pyramid gate — add size, max total risk, and invalidation for this open idea.

How is this different from one risk unit per idea?

One risk unit defines the max loss for the idea. Scale-in without GO can quietly spend that unit (or more) across multiple adds. The GO must keep total risk inside the unit and the sleeve rules.

What belongs in a scale-in GO?

Written before the add: add size, max total risk after the add (open risk + new size), and invalidation for the whole position including prior fills. A green mark or agent confidence is not a GO.

Do I invent a broker pyramid or scale-in UI?

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

Does this replace size from sleeve or never skip review?

No. Size from sleeve sizes under current sleeve rules. Write invalidation is the kill line. Never skip review is the human ticket gate. This page is the scale-in / pyramid GO on an open position. You need the stack.

Where do I apply this next?

When the agent proposes add / scale-in / pyramid on an open (often winning) position: require a written GO (add size, max total risk, invalidation) before review. Enforce in the broker UI. 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.