# Journal every override

Whenever a human overrides the agent’s plan, skips a review gate, or changes size/kill rules mid-session, write it down — why, what changed, what filled — so the next session inherits reality, not hope. Pair with log-session-end-checklist, receipt-log-after-session, never-skip-review-before-place, name-the-strategy-before-connect, no-averaging-down-without-new-thesis. Agent Lane does not place trades, hold wallets, or invent broker UI.

Canonical HTML: https://agentlane.net/guides/journal-every-override/

## Answer first

Mid-session human bends — plan override, review skip, size or kill change — must be written when they happen: why, what changed, what filled in the venue UI. The next session should inherit reality, not hope.

## Why an unlogged override is the failure mode

- **Chat scrolls; named plan stays “true”** — [name-the-strategy-before-connect.md](./name-the-strategy-before-connect.md).
- **Review skip without a note becomes standing skip** — [never-skip-review-before-place.md](./never-skip-review-before-place.md).
- **Next session inherits hope** — [log-session-end-checklist.md](./log-session-end-checklist.md), [receipt-log-after-session.md](./receipt-log-after-session.md).

## What it means

1. Write it when it happens — paper/sheet/note you control; not agent memory alone; no invented broker export.
2. Why — human reason for the bend.
3. What changed — plan, review skip, size, kill rule (numbers/rules after).
4. What filled — venue-confirmed — [confirm-fills-in-broker-not-chat.md](./confirm-fills-in-broker-not-chat.md).
5. Carry into close — [log-session-end-checklist.md](./log-session-end-checklist.md), [receipt-log-after-session.md](./receipt-log-after-session.md).

## Shield stack

1. [name-the-strategy-before-connect.md](./name-the-strategy-before-connect.md) — written plan.
2. [never-skip-review-before-place.md](./never-skip-review-before-place.md) — human gate.
3. [no-averaging-down-without-new-thesis.md](./no-averaging-down-without-new-thesis.md) — add-size gate.
4. Journal every override (this page) — mid-session reality log.
5. [confirm-fills-in-broker-not-chat.md](./confirm-fills-in-broker-not-chat.md) — venue truth.
6. [receipt-log-after-session.md](./receipt-log-after-session.md) + [log-session-end-checklist.md](./log-session-end-checklist.md) — proof and close.

## How to run journal every override

1. Keep the named plan visible — [name-the-strategy-before-connect.md](./name-the-strategy-before-connect.md).
2. Treat every human bend as journalable — plan/review/size/kills; review stays on — [never-skip-review-before-place.md](./never-skip-review-before-place.md); add-size — [no-averaging-down-without-new-thesis.md](./no-averaging-down-without-new-thesis.md).
3. Write why, what changed, what filled — [confirm-fills-in-broker-not-chat.md](./confirm-fills-in-broker-not-chat.md); no invented UI.
4. Map to named strategy and sleeve — [one-strategy-one-sleeve.md](./one-strategy-one-sleeve.md), [cap-daily-loss-before-session.md](./cap-daily-loss-before-session.md).
5. Carry into session close — [log-session-end-checklist.md](./log-session-end-checklist.md), [receipt-log-after-session.md](./receipt-log-after-session.md).
6. Mismatch: stop and revoke before debug — [revoke-before-debug.md](./revoke-before-debug.md); travel: [kill-switch-before-travel.md](./kill-switch-before-travel.md).

## Practical checklist

- Named plan visible.
- Every bend logged when it happens.
- Why + what changed + what filled.
- Venue truth for fills.
- Mapped to strategy/sleeve.
- Carried into close.
- Official paths only — no invented broker UI.

Related: [Write invalidation before entry](./write-invalidation-before-entry.md), [One cancel, one confirm](./one-cancel-one-confirm.md), [confirm-cancel-in-broker-not-chat.md](./confirm-cancel-in-broker-not-chat.md), [log-session-end-checklist.md](./log-session-end-checklist.md), [receipt-log-after-session.md](./receipt-log-after-session.md), [never-skip-review-before-place.md](./never-skip-review-before-place.md), [name-the-strategy-before-connect.md](./name-the-strategy-before-connect.md), [no-averaging-down-without-new-thesis.md](./no-averaging-down-without-new-thesis.md), [confirm-fills-in-broker-not-chat.md](./confirm-fills-in-broker-not-chat.md), [write-go-before-scale-up.md](./write-go-before-scale-up.md)

## FAQ

**What does journal every override mean?**
Write every mid-session human override of plan, review, size, or kills — why, what changed, what filled — so the next session inherits reality, not hope.

**Do I invent a broker override UI?**
No. Official venue tickets and your notes only. Agent Lane does not invent UI.

**Does this replace naming, never-skip-review, or no-averaging-down?**
No. Plan, gate, and add-size rule are different brakes. This page records when a human bent them. You need the stack.

## Sources

- Canonical HTML: https://agentlane.net/guides/journal-every-override/
- Related shelf: https://agentlane.net/resources/
- Site index: https://agentlane.net/llms.txt

Agent Lane publishes checklists. We do not place trades, hold wallets, invent broker UI, or write your override journal.