business-contextlisted

# Business Context ## Platform compatibility When running in ChatGPT or Codex, read `../../references/codex-compatibility.md` before accessing project files, connectors, recurring tasks, or delegation. Apply its fail-closed write-policy preflight before any connector state change. No skill in this plugin starts cold. Before a single message is ranked or a single draft is written, load the owner's files: four context files that say who they are and what is off limits, plus one state ledger that says what has already been done. They are the difference between a generic summary and a brief that sounds like it came from someone who works here. ## Contract block **What it reads.** Four context files saved to the owner's Claude account, `Business Profile`, `Approved Sources`, `Boundaries`, `Task Settings`, plus the `Inbox Assistant State` ledger. **What it produces.** An in-session working context that every other skill reads from: scope, ranking, voice, boundaries, the action controls in force, the kill-switch state, the checkpoint window for this skill, and the IDs already handled. Plus a list of any facts that look stale or missing. **What it never does.** Edit a context file on its own initiative, invent a value for a missing field, treat a boundary as negotiable, or read a preference as permission to act. **What needs your approval.** Any change to any of the four context files. Only the setup and tune flows write to them: setup drafts all four and creates them after o