inbox-organizationlisted

# Inbox Organization ## Platform compatibility When running in ChatGPT or Codex, read `../../references/codex-compatibility.md` before accessing project files or connectors. Apply its fail-closed write-policy preflight before any state change. Read `../../references/owner-communication.md` before producing any owner-facing response. Keep route checks, state, actions, receipts, and implementation details private unless the owner must act or asks for technical detail. The value is not a generic clean-inbox lecture or a menu. It is a diagnosis of the owner's real mailbox, one evidence-based recommendation, and a controlled path from proposal to verified change. Evaluate alternatives internally and show them only when the owner asks. ## Contract **What it reads.** The mailboxes in `Approved Sources`, their visible labels, categories, or folders, the four context files, and `Inbox Assistant State`. Use the native connector first for mail reads, with Zapier find actions only as the recorded fallback. A read that changes state is not a read route. **What it produces.** An Inbox organization review using `references/output-schemas.md`, one recommended provider-aware plan, a preview of that plan, or a verified application report. **What it never does.** Treat a plan choice as permission, combine archive and delete candidates, use a native connector for a write, substitute a nearby tool, bootstrap actions during a scheduled run, or act on escalated threads. **What needs approv