Cancel-replace tax: when working the book costs expectancy

[Fairman]

On **Cancel-replace tax: when working the book costs expectancy**, the desk standard stays practical. Working an order with endless cancel/replace can feel professional and still bleed expectancy through missed fills, worse queue priority, and attention fragmentation.

Execution quality is fill-to-plan adverse cents on your names at your TOD buckets — not a brand slogan. Size follows live spread width and session phase.

## Rails that stay on the sheet
- Working the book can cost expectancy.
- Budget replaces.
- Invalidation written in cents or an auditable structure break before entry.

## Framework I will not skip
1. Write the definition before the open (level, trigger, invalidation in cents, size, max loss). Verbal plans do not count.
2. Liquidity and spread gates beat narrative. If live spread exceeds max, observe or cut — the chart can still "look perfect."
3. One clean attempt per idea in a window. Failed attempt means new structure, not revenge.
4. Log adverse cents by TOD bucket (open vs midday) and by ETF vs single-name before changing venue folklore.
5. Tag the trade or the skip the same day — Sunday-you cannot fix what Monday-you did not name.

## Worked example — Cancel-replace spam
Working book with endless replace; miss move; pay fees/latency. Tax: when replace expectancy negative, use fewer working orders or marketable within slip budget.

I keep examples in cents and clock time so Sunday review can tag the behavior — not rewrite it as a mood.

## Failure modes
- Ignoring the rails above on **Cancel-replace tax: when working the book costs expectancy** and substituting confidence.
- Adding size after adverse selection because the story still feels right.
- Paying open microstructure tax that midday memory never modeled.

## When to skip
Skipping is a first-class decision — even when the chart still looks persuasive:
- Checklist incomplete at 09:20 ET — observe or one pre-written A+ only.
- Live spread outside max for that symbol and session bucket.
- Index violently disagrees with a single-name thesis and no reduced-size RS plan is on the sheet.
- Platform, hotkeys, locate, or flatten path unverified after reconnect/update.
- Daily loss, PDT slot, or prop buffer tripwire already touched.
- News/FOMC/CPI window where the size-cut card says stand down.

## Closing
For **Cancel-replace tax: when working the book costs expectancy**, keep operable boredom: written rails, measured cents, index context when relevant, and a skip that needs no apology. Process quality beats ticket volume.

[Fairman]

A follow-up to my cancel-replace post. Writing it made me realize I needed a number instead of a feeling. The number I chose is two: any order can be modified at most twice. After the second edit I either leave it where it is or cancel it. There's no third edit. My order tool enforces this, so I don't have to remember.

## Why two
It isn't based on research. It's just the smallest number that still lets me do the two legitimate things: tighten a stop once the trade has moved, and adjust a resting limit once if the level shifts by a cent or two. Edits beyond that, in my logs, were nearly always me chasing or fidgeting.

## Rails
- The edit counter is per order_id. A cancel followed by a fresh order on the same idea counts against the same budget. The tool links them through a reason tag and a 60-second window.
- Stop edits may only tighten. Loosening a stop doesn't count as an edit because it isn't allowed at all.
- An entry limit can move at most 2 cents from its original price across both edits combined.

## Worked example (illustrative)
10:05 ET, a $53 name. I rest a buy at 53.18 near VWAP. At 10:06 ET VWAP ticks to 53.20 and I edit to 53.20 (edit 1). At 10:07 ET it lifts to 53.26. I want to edit to 53.24, but that's 6 cents from the original, over the 2-cent limit. The tool blocks it. I cancel instead.

It runs to 53.45 without me. Annoying. Then at 10:14 ET it drops back to 53.12. If I'd chased at 53.24 with a stop at 53.10, I'd have been stopped out for 14 cents.

A second trade, 10:40 ET. I'm long 200 at 53.30 with a stop at 53.17. At 10:44 ET I tighten it to 53.25 (edit 1), and at 10:49 ET to 53.34 (edit 2). It stops out at 53.34 at 10:52 ET for +4 cents. No third edit was needed.

## Failure modes
- Getting around the cap by cancelling and re-sending as a "new" order. That's why cancels are linked.
- Using both edits in the first ten seconds out of nerves, which leaves none for managing the trade.
- Thinking the cap costs me trades. It does cost some, and I've accepted that.

## When to skip
- If a level is moving so fast that two edits aren't enough, it's not a level I can trade passively. I either wait or use a capped marketable limit.
- Around news releases, I don't rest passive entries at all.

Diagram: an order ticket with two edit slots and a locked third slot, and an arrow from "edit 3?" to "leave it or cancel."