Guide

One cancel, one confirm

For every cancel (or flatten / close) the agent claims, require one human confirm in the broker UI before the next place or size change — one cancel → one confirm; chat is not enough. Pair it with confirm cancel in the broker, not chat, confirm fills in the broker, not chat, no chase after partial fill, never skip review before place, max slippage or cancel, and journal every override.

By Agent Lane Editorial · Page dated 27 September 2026

Answer first

When the agent claims a cancel, flatten, or close — stop before the next place or size change. Open the broker UI, not chat, and confirm that one claim. Only after that human confirm may you run the usual place gates (never skip review, confirm fills, quote, buying power, max slippage or cancel). One cancel → one confirm. 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 1:1 cancel→confirm cadence on the shield — so cancel claims cannot stack into a new place or size change on chat alone. Pair it with confirm cancel in the broker, not chat, confirm fills in the broker, not chat, no chase after partial fill, never skip review before place, max slippage or cancel, journal every override, log session end checklist, and the shared-box checklist.

We are a publisher, not a trading desk. Product screens change; read cancels and flats on the official page. We do not invent cancel dashboards or Agentic click-paths. You enforce one confirm per claimed cancel before the next place or size change.

One cancel, one confirm in plain terms

• One claim → one human broker confirm — each cancel / flatten / close the agent asserts gets its own look in the venue UI.
• Before next place or size change — the confirm clears the gate; chat does not.
• Confirm cancel is the check; this is the cadence — see confirm cancel in the broker.
• Partials still follow no-chase — residual remainder is not “finished” by a cancel claim in chat — no chase after partial fill.
• Then the place stack — never skip review, confirm fills, max slippage or cancel.

Why skipping the confirm between cancel and next place is the failure mode

• Hallucinated flat → new risk. Chat says cancelled; residual still working; you place again — confirm cancel.
• Stacked cancels in chat. Several “cancelled” lines without a venue look each — book never matched before the next ticket.
• Size change on a ghost cancel. Resizing or adding while a working order you thought was dead is still open — never skip review, journal every override.
• Partial remainder treated as done. Cancel claim in chat is not a remainder plan — no chase after partial fill, max slippage or cancel.

Where it sits in the shield stack

1. Never skip review before place — human gate on place and on deliberate cancel/close you approve.
2. Confirm fills in the broker, not chat — venue truth after a place.
3. Confirm cancel in the broker, not chat — venue truth after a cancel or close claim.
4. One cancel, one confirm — cadence: that venue confirm once per claimed cancel before next place or size change.
5. No chase after partial fill — remainder rule when only part of the size printed.
6. Max slippage or cancel — pre-place fill-quality bound; breach means cancel, then confirm.
7. Journal every override — write skips and chat/venue mismatches.
8. Log session end checklist — record confirmed cancels/flats before you walk away.

Healthy flow: cancel claim → one human broker confirm → (only then) next place or size change under review + fills + slippage rules. Skip the cadence and a clean cancel claim still opens new risk on a wrong book.

How to run one cancel, one confirm

1. Treat every cancel claim as unpaid until confirmed. Cancelled / flattened / closed in chat is not clearance for the next place or size change.
2. Open the broker or wallet UI. Official orders / activity / positions for that sleeve — confirm cancel. No invented UI.
3. Confirm that one cancel (or flatten/close). Gone vs still working vs residual; flat vs open — matched to the single claim.
4. Block next place / size change until confirm. Chat does not clear the gate. Shared computer: same profile that owns the sleeve — shared-box, separate browser profile.
5. Then run the usual place gates. Never skip review; fresh quote; buying power; max slippage or cancel; confirm fills after place. Large tickets: two-person rule.
6. Journal skips and mismatches. Journal every override; chat/venue disagree badly: revoke before you debug. Session close: log session end checklist.

Practical checklist

• One cancel claim → one human broker confirm before next place or size change.
• Chat / agent “cancelled” is not the confirm.
• Residuals count — still working is not done; see no chase after partial fill.
• Confirm cancel supplies the venue check; this page supplies the cadence.
• Review before place still on for the next ticket.
• Size changes after a cancel claim need the same confirm first.
• Overrides journaled if anyone skipped the confirm.
• No invented UI. Official cancel/position screens and your notes; you enforce.
• Shared-box pass. Who confirms cancels 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, cancel orders, or babysit your agents.
• We do not hold your funds, run a hot wallet, or settle payments.
• We do not invent cancel dashboards, flatten menus, or Agentic click-paths.
• We do not claim a product that auto-confirms cancels for you or read your broker for you.

Related guides

• Flatten all before connector revoke
• One order per idea until fill
• No place while unconfirmed fill
• Write max loss before entry
• Write invalidation before entry
• Confirm cancel in the broker, not chat
• Confirm fills in the broker, not chat
• No chase after partial fill
• Never skip review before place
• Max slippage or cancel
• Journal every override
• Log session end checklist
• Review before place
• Reject agent place without a fresh quote
• Confirm buying power before place
• No market order without GO
• Two-person rule for large places
• Receipt log after the session
• Revoke before you debug
• Empty the sleeve overnight
• 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
• Shared-box and connector checklist
• Shield brokerage spend
• Shield crypto spend

FAQ

What does one cancel, one confirm mean?

It means: for every cancel, flatten, or close the agent claims, require one human confirm in the broker (or wallet) UI before the next place or size change. One cancel → one confirm; chat is not enough. Pair with confirm cancel, confirm fills, no chase after partial fill, never skip review before place, max slippage or cancel, and journal every override.

How is this different from confirm cancel in the broker, not chat?

Confirm cancel is the venue-truth check after a cancel or close claim. One cancel, one confirm is the cadence rule: that venue confirm must happen once per claimed cancel before any next place or size change — you do not batch several cancel claims and then place on chat. You need both.

Why is skipping the confirm between cancel and next place the failure mode?

Agents can claim cancelled while residual risk is still live, or stack cancel → place → cancel in chat while the book never matched. Without a 1:1 human broker confirm before the next place or size change, you can open new risk on a hallucinated flat or resize while a working order you thought was dead is still open. See confirm cancel and no chase after partial fill.

Does this replace never skip review or confirm fills?

No. Never skip review is the human gate before place. Confirm fills is venue truth after a place. Confirm cancel is venue truth after a cancel claim. No chase after partial fill is the remainder rule. This page is the 1:1 cadence. You need the stack.

What counts as the one confirm?

A human look at the official broker or wallet UI for that sleeve — order cancelled/rejected/still open, position flat or residual — matched to the claim. Chat, agent summaries, and screenshots in the transcript do not count. Agent Lane does not invent a cancel dashboard.

When may I place or change size after a cancel claim?

Only after one human confirm in the broker UI for that cancel (or flatten/close). Then the usual gates still apply: never skip review, fresh quote, buying power, max slippage or cancel, and any size change needs its own GO / thesis rules.

Where do I apply this next?

Whenever the agent claims a cancel, flatten, or close: open the broker UI, confirm once, then — and only then — allow the next place or size change. Log mismatches; journal overrides that skipped the confirm. 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.