# 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 with name-the-strategy-before-connect, separate-funding-from-trading-wallet, fund-session-ceiling, and cap-daily-loss-before-session. Agent Lane does not place trades, hold wallets, or invent broker UI.

Canonical HTML: https://agentlane.net/guides/one-strategy-one-sleeve/

## 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.

## Why a shared sleeve across strategies is the failure mode

- **P&L blurs** — [name-the-strategy-before-connect.md](./name-the-strategy-before-connect.md).
- **Ceilings and kill switches go soft** — [cap-daily-loss-before-session.md](./cap-daily-loss-before-session.md), [fund-session-ceiling.md](./fund-session-ceiling.md).
- **Cold/hot split is not enough alone** — [separate-funding-from-trading-wallet.md](./separate-funding-from-trading-wallet.md).

## What it means

1. One name → one sleeve (sub-account or clearly labeled sub-balance).
2. Attributed P&L — confirm [confirm-fills-in-broker-not-chat.md](./confirm-fills-in-broker-not-chat.md).
3. Ceiling and loss stop per sleeve — [fund-session-ceiling.md](./fund-session-ceiling.md), [cap-daily-loss-before-session.md](./cap-daily-loss-before-session.md).
4. Kill switch per sleeve — empty/park this sleeve on hit.
5. Cold capital still off-path — [separate-funding-from-trading-wallet.md](./separate-funding-from-trading-wallet.md).

## Shield stack

1. [name-the-strategy-before-connect.md](./name-the-strategy-before-connect.md) — written plan.
2. [separate-funding-from-trading-wallet.md](./separate-funding-from-trading-wallet.md) — cold off hot path.
3. One strategy, one sleeve (this page) — isolate each plan’s cash and stops.
4. [fund-session-ceiling.md](./fund-session-ceiling.md).
5. [cap-daily-loss-before-session.md](./cap-daily-loss-before-session.md).
6. [log-session-end-checklist.md](./log-session-end-checklist.md) + [empty-sleeve-overnight.md](./empty-sleeve-overnight.md).

## How to run one strategy, one sleeve

1. Name the strategy first — [name-the-strategy-before-connect.md](./name-the-strategy-before-connect.md).
2. Assign one sleeve per name — official venue features or labeled balances you control; no invented UI.
3. Fund only that sleeve’s ceiling — [fund-session-ceiling.md](./fund-session-ceiling.md), [separate-funding-from-trading-wallet.md](./separate-funding-from-trading-wallet.md).
4. Attach loss stop and kills to the sleeve — [cap-daily-loss-before-session.md](./cap-daily-loss-before-session.md).
5. Keep review on; confirm in venue UI — [never-skip-review-before-place.md](./never-skip-review-before-place.md), [confirm-fills-in-broker-not-chat.md](./confirm-fills-in-broker-not-chat.md), [two-person-rule-for-large-places.md](./two-person-rule-for-large-places.md).
6. Log and empty per sleeve — [log-session-end-checklist.md](./log-session-end-checklist.md), [empty-sleeve-overnight.md](./empty-sleeve-overnight.md); travel: [kill-switch-before-travel.md](./kill-switch-before-travel.md).

## Practical checklist

- Strategy named; kill conditions written.
- Sleeve mapped — name → own funded sleeve or labeled sub-balance.
- No shared hot pool across unrelated plans.
- Ceiling funded only on that sleeve.
- Loss stop on that sleeve.
- Cold capital off-path.
- Review on; fills from venue UI.
- Close and empty per sleeve — no cross-refill without a new plan.
- Official paths only — no invented broker UI.

Related: [one-risk-unit-per-idea.md](./one-risk-unit-per-idea.md), [max-open-positions-per-sleeve.md](./max-open-positions-per-sleeve.md), [name-the-strategy-before-connect.md](./name-the-strategy-before-connect.md), [no-averaging-down-without-new-thesis.md](./no-averaging-down-without-new-thesis.md), [separate-funding-from-trading-wallet.md](./separate-funding-from-trading-wallet.md), [fund-session-ceiling.md](./fund-session-ceiling.md), [cap-daily-loss-before-session.md](./cap-daily-loss-before-session.md), [empty-sleeve-overnight.md](./empty-sleeve-overnight.md), [log-session-end-checklist.md](./log-session-end-checklist.md)., [one-venue-one-agent-session.md](./one-venue-one-agent-session.md)

## FAQ

**What does one strategy, one sleeve mean?**
Give each named strategy its own funded sleeve or clearly labeled sub-balance so P&L, ceilings, and kill switches do not blur. Pair with name-strategy, separate-funding, fund-ceiling, cap-daily-loss.

**Do I invent a broker multi-sleeve UI?**
No. Official venue flows and your notes only. Agent Lane does not invent UI.

**Does this replace naming, fund-ceiling, or daily loss?**
No. Plan, isolation, cash size, and loss stop are different brakes. You need the stack.

## Sources

- Canonical HTML: https://agentlane.net/guides/one-strategy-one-sleeve/
- Related shelf: https://agentlane.net/resources/
- Site index: https://agentlane.net/llms.txt

Agent Lane publishes checklists. We do not place trades, hold wallets, invent broker UI, or set your sleeve map.