Guide

Size from sleeve not from hope

Position size comes from the sleeve’s written risk rules — max % of sleeve, max loss, open-position cap — not from conviction, FOMO, or “it’ll come back.” Pair it with one strategy, one sleeve, max open positions per sleeve, cap daily loss before session, no averaging down without a new thesis, and no overnight margin without GO.

By Agent Lane Editorial · Page dated 27 September 2026

Answer first

Before you approve a place: check ticket size against the sleeve’s written risk rules — max percent of sleeve cash, max loss for the trade or session, and the open-position cap. Conviction, FOMO, and “it’ll come back” are not size inputs. Count balances and opens in the official venue UI at review. 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 ticket-size brake on the shield — size from sleeve not from hope — so each place is sized from written sleeve rules, not mood. Pair it with one strategy, one sleeve, max open positions per sleeve, cap daily loss before session, no averaging down without a new thesis, no overnight margin without GO, name the strategy before connect, 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 sizing dashboards or Agentic menus. You write the sleeve rules and enforce them at review.

Sleeve risk rules in plain terms

• Max % of sleeve — the largest share of this sleeve’s spendable cash (or buying power you allow) one ticket may use.
• Max loss — the most you accept to lose on a trade and/or the session before size and new opens stop — pairs with cap daily loss before session.
• Open-position cap — how many simultaneous opens this sleeve may hold — max open positions per sleeve.
• Not size inputs — conviction, FOMO, chat confidence, or “it’ll come back.”

Why hope-sized risk is the failure mode

• Conviction scales past the plan. A “sure thing” ticket that ignores max % of sleeve still burns the session — name the strategy before connect, never skip review before place.
• FOMO stacks size and count. Chasing a move can blow past max loss and the open-position cap while cash still looks fine — max open positions, cap daily loss.
• “It’ll come back” is not a thesis. Adding size because price is lower is averaging down without a new written thesis — no averaging down without a new thesis.
• Hope overnight is still open risk. Oversized leveraged holds left while you sleep need a written GO — no overnight margin without GO.

Where it sits in the shield stack

1. Name the strategy before connect — written plan including sleeve risk rules (max %, max loss, open-position cap).
2. One strategy, one sleeve — each named plan gets its own funded sleeve or labeled sub-balance.
3. Fund the session ceiling — cash in this sleeve matches the run.
4. Cap daily loss before session — loss budget + stop rules for this sleeve.
5. Max open positions per sleeve — concurrent-open ceiling.
6. Size from sleeve not from hope — ticket size from those written rules, not conviction/FOMO/hope.
7. Never skip review before place — enforce size against sleeve rules in the venue UI before approving.

Healthy flow: name plan + write sleeve rules → isolate sleeve → fund ceiling → attach loss stop + position-count max → at review size from rules → place only under rules → journal overrides; no averaging-down without thesis; no overnight margin without GO. Skip the size check and cash/loss/count brakes alone will not stop a hope-sized ticket.

How to run size from sleeve not from hope

1. Write sleeve risk rules on the named plan. Max % of sleeve, max loss (trade/session), open-position cap — name the strategy before connect. No invented UI.
2. Isolate one strategy to one sleeve. One strategy, one sleeve; cold capital off-path — separate funding from trading wallet.
3. Attach loss stop and position-count max. Cap daily loss before session; max open positions per sleeve; fund the session ceiling.
4. At review, size from rules not hope. Never skip review before place. Balances and positions from the broker, not chat. Large size: two-person rule.
5. Block hope-sized tickets. Over max % / max loss / open-cap → no place. Add-size on a loser needs a new thesis. Overrides: journal every override.
6. Honor overnight and session close. No overnight margin without GO; log session end checklist; empty the sleeve overnight.

Practical checklist

• Sleeve risk rules written — max % of sleeve, max loss, open-position cap on the named plan.
• Sleeve mapped — rules apply to this sleeve / strategy only.
• Cash ceiling funded; loss stop on; position-count max on.
• Review sizes from rules — venue UI balances/positions, not conviction or chat.
• Hope / FOMO / “it’ll come back” are not size inputs.
• No averaging down without a new written thesis.
• No overnight margin without written GO.
• Any size override journaled.
• No invented UI. Official screens and your notes; you enforce.
• Shared-box pass. Who can raise size rules 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 sizing dashboards, broker menus, or Agentic click-paths.
• We do not set your max %, max loss, or open-position numbers, or claim a product “auto-size” feature.

Related guides

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

FAQ

What does size from sleeve not from hope mean?

It means: ticket size comes from the sleeve’s written risk rules — max percent of sleeve, max loss per trade or session, and open-position cap — not from conviction, FOMO, or hope that a loser will come back. Pair with one strategy, one sleeve, max open positions per sleeve, cap daily loss before session, no averaging down without a new thesis, and no overnight margin without GO.

What are “sleeve risk rules” in plain terms?

Written limits on the named plan for that sleeve: how large one ticket may be as a percent of sleeve cash, how much you may lose on a trade or session, and how many positions may be open at once. Hope, conviction, and FOMO are not size inputs.

Do I invent a broker position-sizing UI?

No. Write the rules on the named plan and enforce them at review before place. Use official venue position and balance screens to check size. Agent Lane does not invent broker dashboards, sizing menus, or Agentic click-paths.

Why is hope-sized risk the failure mode?

Conviction and FOMO scale tickets when rules would say no. “It’ll come back” is averaging-down pressure without a new thesis. Cash left and loss budget left can still hide oversized tickets if size is not tied to sleeve rules at review.

Does this replace max open positions or cap daily loss?

No. Cap daily loss is the loss stop. Max open positions caps concurrent names. Size from sleeve sets how large each ticket may be from written sleeve rules. One strategy, one sleeve isolates the cash those rules apply to. You need the stack.

Who sets the percentages and caps?

You do. Write max percent of sleeve, max loss, and open-position cap on the named plan before connect. Agent Lane does not prescribe magic numbers or claim a product feature that sizes for you.

Where do I apply this next?

Plan: name the strategy and write sleeve risk rules. Isolate: one strategy, one sleeve. Loss stop: cap daily loss. Count: max open positions. Gate: never skip review — check ticket size against sleeve rules, not hope. No averaging down without a new thesis; no overnight margin without GO. Agent Lane publishes the checklist; we do not place trades or invent broker UI.

Next steps

Before an agent touches real money, give the agent its own dedicated wallet, set hard spend caps, and shield your crypto. Or browse all Agent Lane guides.