Guide

Write max loss before entry

Before any live place, write the max loss for that ticket (dollars or % of sleeve) in the review card / plan — so exit size and stop logic are pre-committed; if the place would risk more than that written max, reject. Pair it with write invalidation before entry, one risk unit per idea, size from sleeve not from hope, cap daily loss before session, never skip review before place, and confirm buying power before place.

By Agent Lane Editorial · Page dated 28 September 2026

Answer first

Before a live place: write the max loss for this ticket — dollars or % of sleeve — on the review card or plan. Check that size and stop (or equivalent risk) fit under that number. Missing max, or risk above it → do not place. Distinct from the daily / session loss budget and from invalidation (why you exit). This is the how much you can lose gate before entry. 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 per-ticket max-loss gate on the shield — so a place does not fire without a written ceiling on how much that ticket can lose. Pair it with write invalidation before entry, one risk unit per idea, size from sleeve not from hope, cap daily loss before session, never skip review before place, confirm buying power before place, two-person rule for large places, and the shared-box checklist.

We are a publisher, not a trading desk. Product screens change; read size and buying power on the official page. We do not invent risk dashboards. You write the max and reject when size would breach it.

Write max loss before entry in plain terms

• Write the number — dollars or % of sleeve for this ticket, before place.
• Pre-commit exit size / stop logic so risk is knowable at review.
• Reject over-max — if place would risk more than the written max, do not authorize.
• Not the daily cap — cap daily loss before session is session budget; this is per ticket.
• Not invalidation — write invalidation is why you exit; this is how much you can lose.
• Gate at review — never skip review before place.

Why skipping written max loss is the failure mode

• “We’ll stop somewhere.” No number → stop improvised after you are in — pair with write invalidation.
• Size from hope. Conviction sizing blows past sleeve rules — size from sleeve, one risk unit.
• Daily cap only. Session budget still allows one ticket that is too large — cap daily loss ≠ per-ticket max.
• Invalidation without dollars. You know why you exit but not how much that exit costs at this size.
• Buying power ≠ max loss. Available cash can still fund a ticket that risks more than you intended — confirm buying power.

Where it sits in the shield stack

1. Never skip review before place — human gate before any live place.
2. Name the strategy before connect / one strategy, one sleeve — named plan and sleeve.
3. One risk unit per idea / size from sleeve not from hope — unit and sizing method.
4. Write invalidation before entry — why you exit.
5. Write max loss before entry — how much this ticket can lose (dollars or % of sleeve); reject if size would breach it.
6. Cap daily loss before session — session budget still applies after per-ticket max.
7. Confirm buying power before place — cash/BP from broker UI.
8. Journal every override — write every place that fired without a written max or above it.

Healthy flow: thesis → invalidation → max loss → size check → review → place. Skip the written max and you size on hope.

How to run write max loss before entry

1. Name the ticket. Thesis, symbol, sleeve — one idea.
2. Write max loss. Dollars or % of sleeve on the review card / plan before place.
3. Check size against max. Stop × size (or equivalent) must fit; else reject at review. Method: size from sleeve; unit: one risk unit.
4. Pair with invalidation. Write invalidation separately — why vs how much.
5. Confirm buying power and review. Confirm buying power; respect daily loss cap and two-person rule when size is large.
6. Journal overrides; revoke if misfired. Journal every override; revoke before you debug.

Practical checklist

• Max loss written for this ticket (dollars or % of sleeve).
• Size / stop checked against that max before authorize.
• Missing or over-max → no place at review.
• Invalidation written separately (why you exit).
• Risk unit / sleeve rules respected.
• Daily / session loss cap still in force.
• Buying power from broker UI before place.
• Large size may need second human.
• Overrides journaled if anyone placed without max or above it.
• No invented UI. Official screens and your notes; you enforce.
• Shared-box pass. Who can approve a place with no written max — 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, compute your max loss, or babysit your agents.
• We do not hold your funds, run a hot wallet, or settle payments.
• We do not invent risk dashboards, stop menus, or Agentic click-paths.
• We do not claim a product that auto-rejects places over max loss or read your broker for you.

Related guides

• Write invalidation before entry
• One risk unit per idea
• Size from sleeve not from hope
• Cap daily loss before session
• Never skip review before place
• Confirm buying power before place
• Two-person rule for large places
• Name the strategy before connect
• Journal every override
• No place while unconfirmed fill
• Review before place
• Shared-box and connector checklist
• Shield brokerage spend
• Shield crypto spend

FAQ

What does write max loss before entry mean?

It means: before any live place, write the max loss for that ticket (dollars or % of sleeve) in the review card / plan — so exit size and stop logic are pre-committed; if the place would risk more than that written max, reject. Pair with write invalidation before entry, one risk unit per idea, size from sleeve not from hope, cap daily loss before session, never skip review before place, and confirm buying power before place.

How is this different from cap daily loss before session?

Cap daily loss is the day or session loss budget stop across the sleeve. This page is the per-ticket how-much-you-can-lose figure written before that single place.

How is this different from write invalidation before entry?

Write invalidation is why you exit — price, time, structure, or catalyst fail. This page is how much you can lose on the ticket if that exit (or stop) hits.

How is this different from one risk unit per idea?

One risk unit is the allocation rule that each thesis gets one predefined unit. This page is writing the dollar or % max-loss number on the review card for this place and rejecting if size would breach it.

How is this different from size from sleeve not from hope?

Size from sleeve is the method that size comes from sleeve rules. This page is the explicit max-loss gate on the ticket before entry.

What do I write on the review card?

A clear max loss in dollars or % of sleeve for this ticket — enough that stop distance times size (or equivalent risk) can be checked against it before you authorize place.

Do I invent a max-loss UI?

No. Use your written plan / review notes and official venue screens you already control. Agent Lane does not invent risk dashboards or Agentic click-paths.

Where do I apply this next?

At review before place: if the written max loss is missing, or size/stop would risk more than that max, do not place. 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.