# Flatten all before connector revoke

Before you revoke or disconnect a live trading or spend connector, flatten or cancel working risk in the broker UI first — revoke without flattening can leave orphan working orders or open exposure you can no longer manage through the agent path. Pair with revoke-before-debug, revoke-connectors-when-idle, confirm-cancel-in-broker-not-chat, one-cancel-one-confirm, empty-sleeve-overnight, kill-switch-before-travel. Agent Lane does not place trades, hold wallets, or invent broker UI.

Canonical HTML: https://agentlane.net/guides/flatten-all-before-connector-revoke/

## Answer first

Before any intentional revoke or disconnect of a live trading or spend connector: inventory opens and working orders in the official broker UI. Flatten or cancel that working risk. Confirm cancel or flat in the broker, not chat. Only then revoke the connector.

## Flatten all before connector revoke in plain terms

1. **Inventory first** — opens and working orders from the official venue UI, not chat.
2. **Flatten or cancel working risk** — close exposure the agent path was managing before you cut the connector.
3. **Confirm in the broker** — [confirm-cancel-in-broker-not-chat.md](./confirm-cancel-in-broker-not-chat.md); cadence via [one-cancel-one-confirm.md](./one-cancel-one-confirm.md).
4. **Then revoke** — idle grants and intentional disconnects come after risk is clear (or explicitly held under a written non-agent plan).
5. **Distinct from incident revoke** — [revoke-before-debug.md](./revoke-before-debug.md) is the misfire kill order; this page is the pre-revoke flatten gate.

## Why revoke-first is the failure mode

- **Orphan working orders** — [confirm-cancel-in-broker-not-chat.md](./confirm-cancel-in-broker-not-chat.md), [one-cancel-one-confirm.md](./one-cancel-one-confirm.md).
- **Open exposure without the agent path** — revoke does not flatten; [empty-sleeve-overnight.md](./empty-sleeve-overnight.md) parks cash, does not close amplified opens.
- **Confused with incident revoke** — [revoke-before-debug.md](./revoke-before-debug.md); still treat residual venue risk in the broker UI.
- **Idle revoke without inventory** — [revoke-connectors-when-idle.md](./revoke-connectors-when-idle.md), [kill-switch-before-travel.md](./kill-switch-before-travel.md).

## Shield stack

1. [confirm-cancel-in-broker-not-chat.md](./confirm-cancel-in-broker-not-chat.md) — cancel/flat truth source.
2. [one-cancel-one-confirm.md](./one-cancel-one-confirm.md) — cancel cadence.
3. Flatten all before connector revoke (this page) — clear working risk before you cut the agent path.
4. [revoke-connectors-when-idle.md](./revoke-connectors-when-idle.md) — idle/session-end grant close after risk is handled.
5. [empty-sleeve-overnight.md](./empty-sleeve-overnight.md) — park spendable cash when the run ends.
6. [kill-switch-before-travel.md](./kill-switch-before-travel.md) — travel/offline composite.
7. [revoke-before-debug.md](./revoke-before-debug.md) — incident kill order (still clear residual venue risk in the UI).
8. [log-session-end-checklist.md](./log-session-end-checklist.md) — record flatten, confirms, and revoke.

## How to run flatten all before connector revoke

1. Inventory opens and working orders in the venue UI — official screens only; not chat.
2. Flatten or cancel working risk first — [one-cancel-one-confirm.md](./one-cancel-one-confirm.md).
3. Confirm flat / cancel in the broker, not chat — [confirm-cancel-in-broker-not-chat.md](./confirm-cancel-in-broker-not-chat.md), [confirm-fills-in-broker-not-chat.md](./confirm-fills-in-broker-not-chat.md).
4. Then revoke or disconnect — [revoke-connectors-when-idle.md](./revoke-connectors-when-idle.md); incident → [revoke-before-debug.md](./revoke-before-debug.md).
5. Park cash and close the session if ending the run — [empty-sleeve-overnight.md](./empty-sleeve-overnight.md), [kill-switch-before-travel.md](./kill-switch-before-travel.md).
6. Journal what you flattened and what you revoked — [journal-every-override.md](./journal-every-override.md), [log-session-end-checklist.md](./log-session-end-checklist.md).

## Practical checklist

- Opens and working orders inventoried in the official venue UI.
- Working risk flattened or canceled before revoke.
- Cancel/flat confirmed in the broker — not chat.
- One cancel → one confirm cadence respected.
- Then revoke idle grants or intentional disconnect.
- Distinct from incident revoke-before-debug, idle revoke, news flatten, empty-sleeve cash park, and travel kill-switch.
- Sleeve parked if the session is ending.
- Flatten + revoke journaled.
- Official paths only — no invented broker UI.

Related: [revoke-before-debug.md](./revoke-before-debug.md), [revoke-connectors-when-idle.md](./revoke-connectors-when-idle.md), [confirm-cancel-in-broker-not-chat.md](./confirm-cancel-in-broker-not-chat.md), [one-cancel-one-confirm.md](./one-cancel-one-confirm.md), [empty-sleeve-overnight.md](./empty-sleeve-overnight.md), [kill-switch-before-travel.md](./kill-switch-before-travel.md), [flatten-before-news-unknown.md](./flatten-before-news-unknown.md), [confirm-fills-in-broker-not-chat.md](./confirm-fills-in-broker-not-chat.md), [log-session-end-checklist.md](./log-session-end-checklist.md), [journal-every-override.md](./journal-every-override.md), [one-connector-at-a-time.md](./one-connector-at-a-time.md), [shared-box.md](./shared-box.md).

## FAQ

**What does flatten all before connector revoke mean?**
Before you revoke or disconnect a live trading or spend connector, flatten or cancel working risk in the broker UI first. Revoke without flattening can leave orphan working orders or open exposure you can no longer manage through the agent path. Pair with revoke-before-debug, revoke-connectors-when-idle, confirm-cancel-in-broker-not-chat, one-cancel-one-confirm, empty-sleeve-overnight, kill-switch-before-travel.

**How is this different from revoke before debug / revoke when idle / flatten before news?**
Revoke before debug is the incident kill order. Revoke when idle is the idle grant close. Flatten before news is the catalyst rule. This page is the pre-revoke flatten gate so orphan risk does not outlive the connector.

**Do I invent a flatten-then-revoke broker UI?**
No. Official venue screens and your written rule. Agent Lane does not invent UI or place trades for you.

## Sources

- Canonical HTML: https://agentlane.net/guides/flatten-all-before-connector-revoke/
- 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 read your order tickets.