Guide

Write invalidation before entry

Before the agent enters a live ticket, write what would invalidate the thesis — price, time, structure, or catalyst fail — so exit is pre-committed, not improvised after you are in. Pair it with name the strategy before connect, one risk unit per idea, no averaging down without a new thesis, flatten before news you cannot size, never skip review before place, and size from sleeve not from hope.

By Agent Lane Editorial · Page dated 27 September 2026

Answer first

Before a live entry: write the invalidation for this ticket — what kills the thesis and what you do when it hits (flatten, cancel working, reduce). Set one risk unit and size from sleeve in the same review step. Do not approve a blank “we’ll see.” Chat hope after fill is not a plan. 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 pre-entry invalidation write-down on the shield — so the agent cannot enter without a kill line the human can enforce. Pair it with name the strategy before connect, one risk unit per idea, no averaging down without a new thesis, flatten before news you cannot size, never skip review before place, size from sleeve not from hope, write GO before scale-up, journal every override, and the shared-box checklist.

We are a publisher, not a trading desk. Product screens change; read orders and positions on the official page. We do not invent stop dashboards or Agentic click-paths. You write the invalidation and enforce it at review and after fill.

Write invalidation before entry in plain terms

• Before place, not after — the kill line is written in the same review step as size and approve.
• What kills the thesis — price level, time stop, structure break, and/or catalyst fail you already named.
• What you do when it hits — flatten, cancel working, or reduce — not “give it room” in chat.
• Risk unit + sleeve size — one risk unit per idea, size from sleeve.
• Gate at review — reject entry if invalidation is blank or vague — never skip review before place.

Why improvising the exit after entry is the failure mode

• Hope rewrites the thesis. Once filled, “give it room” replaces the kill line — journal every override.
• Adds without a new thesis. Averaging down because price is lower — no averaging down without a new thesis.
• Holding into unknown news. No written catalyst fail → overnight hope — flatten before news you cannot size, no overnight margin without GO.
• Size without a kill. Risk unit alone is how much you can lose; without invalidation, the agent has no when — size from sleeve not from hope.

Where it sits in the shield stack

1. Name the strategy before connect — strategy-level plan and kill conditions.
2. One risk unit per idea — max loss for this thesis in sleeve terms.
3. Size from sleeve not from hope — ticket size from written rules.
4. Write invalidation before entry — per-ticket kill line before place.
5. Never skip review before place — human gate rejects blank invalidation.
6. No averaging down without a new thesis — add-size needs fresh thesis + new invalidation.
7. Flatten before news you cannot size — session rule for catalysts outside the written edge.
8. Journal every override — write holds past invalidation and blank-entry skips.

Healthy flow: named strategy → risk unit → size from sleeve → write invalidation → review → place → enforce kill / confirm in broker. Skip the write-down and a well-sized thesis still exits on hope.

How to run write invalidation before entry

1. Name the idea and risk unit. Tie to the named plan — name the strategy before connect; one risk unit. No invented UI.
2. Write the invalidation. Price / time / structure / catalyst fail + action (flatten, cancel, reduce). Same note as size from sleeve rules.
3. Same review step as size and place. Reject if blank or vague — never skip review. Large tickets: two-person rule.
4. Enforce after fill. When invalidation hits, exit per the note; confirm flatten/cancel in the broker UI, not chat. Cadence: one cancel, one confirm.
5. No add without new thesis + new invalidation. No averaging down; scale changes need write GO before scale-up.
6. Journal overrides; respect unknown news. Journal every override; catalysts you cannot size: flatten before news; misfire: revoke before you debug.

Practical checklist

• Invalidation written before approve — price / time / structure / catalyst + action.
• Risk unit + sleeve size set in the same step.
• Reject blank / vague kill lines at review.
• Enforce when it hits — no chat rewrite.
• Confirm flatten/cancel in the broker UI.
• Adds need new thesis + new invalidation.
• Overrides journaled if anyone entered without invalidation or held past it.
• No invented UI. Official order/position screens and your notes; you enforce.
• Shared-box pass. Who can approve entry without a written invalidation 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, set stops, or babysit your agents.
• We do not hold your funds, run a hot wallet, or settle payments.
• We do not invent stop dashboards, invalidation menus, or Agentic click-paths.
• We do not claim a product that auto-writes invalidation for you or read your broker for you.

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
• Confirm symbol before place
• Reject duplicate place same thesis
• Name the strategy before connect
• One risk unit per idea
• No averaging down without a new thesis
• Flatten before news you cannot size
• Never skip review before place
• Size from sleeve not from hope
• Write GO before scale-up
• Journal every override
• One cancel, one confirm
• Confirm cancel in the broker, not chat
• No overnight margin without GO
• Two-person rule for large places
• Review before place
• Shared-box and connector checklist
• Shield brokerage spend
• Shield crypto spend

FAQ

What does write invalidation before entry mean?

It means: before a live entry, write what would kill the thesis for that ticket — a price level, time stop, structure break, or catalyst fail — so exit is pre-committed. Pair with name the strategy before connect, one risk unit per idea, no averaging down without a new thesis, flatten before news you cannot size, never skip review before place, and size from sleeve not from hope.

How is this different from name the strategy before connect?

Name the strategy is the plan before you connect (name, instruments, ceiling, kill conditions at strategy level). Write invalidation before entry is the per-ticket kill line written in the same review step as size and place. You need both.

How is this different from one risk unit per idea?

One risk unit caps max loss in sleeve terms. Invalidation is the trigger that says the thesis is wrong — not only how much you are willing to lose. Size the unit from sleeve rules; write the invalidation before entry.

Why is improvising the exit after entry the failure mode?

Once the agent is in, chat hope and “give it room” rewrite the thesis. Without a written invalidation before place, the human gate has nothing firm to enforce — averaging down, holding into unknown news, or skipping flatten become improvisation. See no averaging down and flatten before news.

Does this replace never skip review or flatten before news?

No. Never skip review is the human ticket gate. Flatten before news is the session rule for catalysts you cannot size. No averaging down is the add-size gate. This page is the pre-entry invalidation write-down. You need the stack.

What belongs in the invalidation note?

Written before approve: what kills the thesis (price / time / structure / catalyst), what you do when it hits (flatten, cancel working, reduce), and that risk unit and sleeve size were set. Chat urgency is not an invalidation.

Where do I apply this next?

At review before place: write invalidation for this ticket, confirm risk unit and size from sleeve, then approve or reject. If invalidation hits later, exit per the note and confirm in the broker 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.