owner-brieflisted

# Weekly Owner Reset ## Platform compatibility When running in ChatGPT or Codex, read `../../references/codex-compatibility.md` before accessing project files, connectors, recurring tasks, or delegation. Preserve this skill's read-only contract on every platform. 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 daily brief keeps the owner on top of the day. This keeps them on top of the business. One page, read on a Friday afternoon, built on three things: what moved, what stalled, and the decisions only the owner can make. ## Contract block **What it reads.** The past week of mail in the mailboxes in `Approved Sources`, anything listed under trusted sources in that file, the four context files, and `Inbox Assistant State`. Mail comes in through the native Gmail or Outlook connector, which is the primary read route, falling back to Zapier find actions for anything the native connectors do not cover. One route per mailbox per run, or the week's story counts the same thread twice. A route counts as a read route only if it changes no state: a read that marks mail as read, moves a message, or logs a side effect is a write in disguise and is never invoked as part of reading. Keep uncovered-route diagnostics private unless the owner must act. **What it produces.** One page in the owner-brief sche