Guide

One risk unit per idea

Each distinct thesis gets one predefined risk unit (max loss in sleeve terms) — do not stack correlated tickets that quietly multiply the same idea’s risk. Pair it with size from sleeve not from hope, max open positions per sleeve, one strategy, one sleeve, no averaging down without a new thesis, and write GO before scale-up.

By Agent Lane Editorial · Page dated 27 September 2026

Answer first

Before you place (or let an agent propose size): name the thesis, assign one risk unit in sleeve terms, and map correlated tickets to that same unit. Size so if the idea fails, total loss stays inside the unit — not several “small” tickets that quietly stack. 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 one-risk-unit rule on the shield — one risk unit per idea — so a single thesis cannot silently consume multiple units via correlated tickets. Pair it with size from sleeve not from hope, max open positions per sleeve, one strategy, one sleeve, no averaging down without a new thesis, write GO before scale-up, never skip review before place, and the shared-box checklist.

We are a publisher, not a trading desk. Product screens change; read positions on the official page. We do not invent risk-unit dashboards, correlation matrices, or Agentic menus. You write the unit and thesis map, and enforce them at review.

One risk unit in plain terms

• Idea / thesis — one written plan on the named strategy: direction, instruments, invalidation, kill rules — name the strategy before connect.
• Risk unit — predefined max loss for that thesis in sleeve terms (dollars or % of sleeve) — size from sleeve not from hope, one strategy, one sleeve.
• Correlated tickets share the unit — same sector, same catalyst, same underlying via different symbols or legs still count as one idea unless you wrote a distinct thesis for each.
• Not a new unit — averaging down, “one more name in the theme,” or splitting size across legs without a new written thesis — no averaging down without a new thesis.

Why stacking correlated tickets is the failure mode

• Several “small” tickets = several units. Per-ticket size and open-count look fine while the same idea’s max loss multiplies — size from sleeve not from hope, max open positions per sleeve.
• Theme stacking without a new thesis. More names in the same bet is still one idea unless you wrote a distinct thesis — no averaging down without a new thesis, name the strategy before connect.
• Blurred P&L across sleeves. Mixing ideas in one sleeve hides which unit blew — one strategy, one sleeve.
• Scale-up by stacking without GO. Raising effective risk via more correlated tickets is a scale-up — needs a written GO — write GO before scale-up.

Where it sits in the shield stack

1. Name the strategy before connect — written plan including thesis map.
2. One strategy, one sleeve — isolate cash and stops per plan.
3. Size from sleeve not from hope — ticket size under current sleeve rules.
4. Max open positions per sleeve — concurrent-open ceiling.
5. One risk unit per idea — one predefined max loss per distinct thesis; correlated tickets share it.
6. No averaging down without a new thesis — no add-size inside a losing thesis.
7. Write GO before scale-up — only path to raise units or stack more ideas.

Healthy flow: name thesis → assign one risk unit → map correlated tickets → size inside the unit → honor open-position cap → no averaging without new thesis → scale only with GO → review enforces. Skip the unit map and per-ticket caps alone will not stop silent multiplication.

How to run one risk unit per idea

1. Name the thesis on the named plan. Instruments, direction, invalidation, kill rules — name the strategy before connect; isolate with one strategy, one sleeve.
2. Assign one risk unit in sleeve terms. Predefine max loss for that thesis — size from sleeve not from hope, cap daily loss before session. No invented UI.
3. Map correlated tickets to the same unit. Same sector, catalyst, or underlying via different symbols/legs share the unit unless each has a distinct written thesis.
4. Size so the idea’s max loss stays inside the unit. Honor max open positions per sleeve; no averaging down without a new thesis.
5. Enforce at review in the official venue UI. Never skip review before place; confirm opens via confirm fills in the broker, not chat. Large places: two-person rule.
6. Journal overrides; scale only with GO; honor session end. Journal every override; raise units only with write GO before scale-up; log session end checklist.

Practical checklist

• Thesis named on the plan before place.
• One risk unit written in sleeve terms for that thesis.
• Correlated tickets mapped to the same unit.
• Size so max loss stays inside the unit — not hope.
• Open-position cap honored — count does not excuse multiplying one idea.
• No averaging down without a new written thesis.
• Scale-up only with written GO if units or stacking rise.
• Review enforces in the official venue UI — not chat.
• No invented UI. Official screens and your notes; you enforce.
• Shared-box pass. Who can approve a new unit or thesis map 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 risk-unit dashboards, correlation matrices, or Agentic click-paths.
• We do not set your risk units, detect correlation for you, or claim a product that auto-caps idea risk.

Related guides

• Write max loss before entry
• One order per idea until fill
• No place while unconfirmed fill
• 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
• Reject duplicate place same thesis
• Write invalidation before entry
• Size from sleeve not from hope
• Max open positions per sleeve
• One strategy, one sleeve
• No averaging down without a new thesis
• Write GO before scale-up
• Name the strategy before connect
• Cap daily loss before session
• Never skip review before place
• Journal every override
• Stop adding size after a loss day
• Confirm fills in the broker, not chat
• Fund the session ceiling
• Two-person rule for large places
• Log session end checklist
• Flatten before news you cannot size
• 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 one risk unit per idea mean?

It means: each distinct thesis gets one predefined risk unit — a max loss written in sleeve terms. Do not stack correlated tickets that quietly multiply the same idea’s risk. Pair with size from sleeve not from hope, max open positions per sleeve, one strategy, one sleeve, no averaging down without a new thesis, and write GO before scale-up.

What counts as one idea / one thesis?

A single written thesis on the named plan: direction, instruments, invalidation, and kill rules you already accepted. Correlated tickets that express the same bet (same sector, same catalyst, same underlying via different symbols or legs) still count as one idea unless you wrote a distinct thesis for each.

What is a risk unit?

A predefined max loss for that thesis in sleeve terms — dollars, percent of sleeve, or equivalent you already wrote — not a hope number mid-session. Size each ticket so the idea’s total loss if wrong stays inside that unit.

Do I invent a risk-unit broker UI?

No. Write the unit and thesis map on the named plan and enforce them at review before place. Use official venue positions and balances. Agent Lane does not invent risk-unit dashboards, correlation matrices, or Agentic click-paths.

Why is stacking correlated tickets the failure mode?

Several “small” tickets on the same idea can equal several risk units while the sleeve still looks under its open-position or per-ticket caps. When the thesis fails, max loss quietly multiplies.

Does this replace size from sleeve or max open positions?

No. Size from sleeve sets ticket size under sleeve rules. Max open positions caps concurrent names. One risk unit per idea caps how much total loss one thesis may consume. One strategy, one sleeve, no averaging down, and write GO before scale-up are different brakes. You need the stack.

Who writes the risk unit and thesis map?

You do. Write the unit and which tickets share a thesis before the session. Agent Lane does not prescribe magic numbers or claim a product that auto-detects correlation for you.

Where do I apply this next?

Name the thesis and write one risk unit in sleeve terms. Size tickets from sleeve rules so the idea’s max loss stays inside that unit. Cap concurrent opens with max open positions per sleeve. No averaging down without a new thesis. Scale only with write GO before scale-up. Enforce at review in the venue 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.