Guide

One strategy, one sleeve

Give each named strategy its own funded sleeve (or clearly labeled sub-balance) so P&L, ceilings, and kill switches do not blur across unrelated plays. Pair it with name the strategy before connect, separate funding from trading wallet, fund the session ceiling, and cap daily loss before session.

By Agent Lane Editorial · Page dated 27 September 2026

Answer first

Do not run two named strategies out of one shared hot sleeve. Isolate each plan in its own funded sleeve or clearly labeled sub-balance so P&L, session ceilings, and kill switches stay attributable. A name without its own cash boundary is still improvisation with someone else’s budget. 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 sleeve-isolation gate on the shield — one strategy, one sleeve — so live connectors inherit a named plan and a cash boundary that does not bleed into unrelated plays. Pair it with name the strategy before connect, separate funding from trading wallet, fund the session ceiling, cap daily loss before session, empty the sleeve overnight, agent spend caps, log session end checklist, and the shared-box checklist.

We are a publisher, not a trading desk. Product screens change; use official venue account or sub-account features if they exist, or clearly labeled notes and balances you already control. We do not invent multi-sleeve dashboards or Agentic click-paths. You map name → sleeve and enforce it.

Why a shared sleeve across strategies is the failure mode

• P&L blurs. Strategy A’s loser eats Strategy B’s budget inside one pool — review cannot tell which plan failed — name the strategy before connect.
• Ceilings and kill switches go soft. A stop for one play looks optional while the shared sleeve still has cash — cap daily loss before session, fund the session ceiling.
• Cold/hot split is not enough alone. Keeping funding capital off the hot path still leaves one hot pool for every live plan — separate funding from trading wallet.

What “one strategy, one sleeve” means

• One name → one sleeve. Each written strategy maps to its own funded sleeve, sub-account, or clearly labeled sub-balance.
• Attributed P&L. Fills, fees, and results for that name stay on that sleeve — confirm in the broker UI, not chat.
• Ceiling and loss stop per sleeve. Session ceiling and daily/session loss cap attach to this sleeve, not a blurry shared pool.
• Kill switch per sleeve. Disable, empty, or park this sleeve when its kill conditions hit — without silently funding another plan from leftover cash.
• Cold capital still off-path. Pair with separate funding from trading wallet; do not top the sleeve from long-term holdings mid-streak.

Where it sits in the shield stack

1. Name the strategy before connect — written plan (name, instruments, size, kills).
2. Separate funding from trading wallet — cold/funding capital off the hot path.
3. One strategy, one sleeve — each named plan gets its own funded sleeve or labeled sub-balance.
4. Fund the session ceiling — cash in this sleeve matches the run.
5. Cap daily loss before session — loss budget + stop rules for this sleeve.
6. Log session end checklist + empty the sleeve overnight — close and park per sleeve.

Healthy flow: name strategy → keep cold capital off-path → assign one sleeve per name → fund only that sleeve’s ceiling → attach loss stop → review on → place only under that sleeve’s budget → hard-stop and log on that sleeve. Share one hot pool across names and attribution dies.

How to run one strategy, one sleeve

1. Name the strategy first. Written plan before any live grant — name the strategy before connect.
2. Assign one sleeve per name. Official sub-account/sleeve if your venue shows one, or a clearly labeled sub-balance you control. No invented UI.
3. Fund only that sleeve’s ceiling. Fund the session ceiling for this plan only. Keep cold capital off-path — separate funding from trading wallet.
4. Attach loss stop and kills to the sleeve. Cap daily loss before session; kill conditions from the named plan fire on this sleeve.
5. Keep review on; confirm in the venue UI. Never skip review before place. Confirm fills in the broker, not chat. Large size: two-person rule.
6. Log and empty per sleeve. Log session end checklist; empty the sleeve overnight. Do not refill strategy B from strategy A’s leftover without a new named plan. Travel: kill switch before travel.

Practical checklist

• Strategy named. One job, one name, kill conditions written.
• Sleeve mapped. Name → own funded sleeve or clearly labeled sub-balance.
• No shared hot pool. Unrelated plans do not share one spendable balance.
• Ceiling funded only on that sleeve. No surplus for “the other play.”
• Loss stop on that sleeve. Daily/session cap + stop rules attached.
• Cold capital off-path. Funding wallet separate from trading sleeve.
• Review on; fills from venue UI. Attribution checked outside chat.
• Close and empty per sleeve. Log, park, no cross-refill without a new plan.
• No invented UI. Official venue screens and your notes only; you map and enforce.
• Shared-box pass. Who can merge sleeves or ignore labels 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 multi-sleeve dashboards, sub-account menus, or Agentic click-paths.
• We do not set your sleeve sizes for you or claim a product “one sleeve per strategy” feature.

Related guides

• One risk unit per idea
• No new risk after session end
• Name the strategy before connect
• Separate funding from trading wallet
• Fund the session ceiling
• Cap daily loss before session
• Empty the sleeve overnight
• Agent spend caps
• Dedicated agent wallet
• Never skip review before place
• No averaging down without a new thesis
• Journal every override
• Max open positions per sleeve
• Confirm cancel in the broker, not chat
• No overnight margin without GO
• Confirm fills in the broker, not chat
• Log session end checklist
• Session time-box
• Kill switch before travel
• Two-person rule for large places
• Review before place
• 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
• 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
• Size from sleeve not from hope

FAQ

What does one strategy, one sleeve mean?

It means: give each named strategy its own funded sleeve (or clearly labeled sub-balance) so P&L, session ceilings, and kill switches do not blur across unrelated plays. Pair with name the strategy before connect, separate funding from trading wallet, fund the session ceiling, and cap daily loss before session.

How is this different from separate funding from trading wallet?

Separate funding from trading wallet keeps long-term and cold capital off the hot path the agent can spend. One strategy, one sleeve goes further inside the hot path: each named strategy gets its own sleeve or labeled sub-balance so losses, ceilings, and stops stay attributable. Use both.

Do I invent a broker multi-sleeve UI?

No. Use official venue account or sub-account features if they exist, or clearly labeled notes and balances you already control. Agent Lane does not invent multi-sleeve dashboards, Agentic menus, or product click-paths.

Why is a shared sleeve across strategies the failure mode?

When two named plans share one funded pool, P&L, ceilings, and kill switches blur. A loss from strategy A can silently eat strategy B’s budget; a stop for one play can look optional because the shared sleeve still has cash. Attribution dies and review has nothing honest to check.

Does this replace naming the strategy, fund-ceiling, or daily loss cap?

No. Name the strategy writes the plan. One strategy, one sleeve isolates the cash and stops for that plan. Fund the session ceiling sizes this run. Cap daily loss is the loss stop. You need the stack.

Where do I apply this next?

Plan: name the strategy before connect. Cold vs hot: separate funding from trading wallet. Cash for this run: fund the session ceiling. Loss stop: cap daily loss before session. Close: log session end checklist. 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.