{ "site": "https://www.chiefofstaff.io/", "generated": "2026-09-06T08:37:23.720Z", "count": 35, "howToWatch": "https://www.chiefofstaff.io/guides/watching-for-new-guides", "guides": [ { "slug": "what-a-chief-of-staff-system-is", "title": "What a Chief-of-Staff System Is", "description": "The function a chief of staff performs, why it transfers to one person running many things, and the eight principles everything else falls out of.", "track": "core", "trackLabel": "Core concepts", "tags": [ "foundations", "principles" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/what-a-chief-of-staff-system-is", "markdown": "https://www.chiefofstaff.io/guides/what-a-chief-of-staff-system-is.md", "outcome": "explain to you, in its own words, what job it holds, which three jobs it must keep separate, and which of the eight principles it would be violating if it took a shortcut.", "prerequisites": [], "contributor": null }, { "slug": "the-constitution", "title": "The Constitution", "description": "The one file the assistant reads before anything else, every session — what belongs in it, what must be kept out of it, and why it should be short enough to obey.", "track": "core", "trackLabel": "Core concepts", "tags": [ "constitution", "claude-md", "operating-rules" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/the-constitution", "markdown": "https://www.chiefofstaff.io/guides/the-constitution.md", "outcome": "draft a two-page constitution for your system, with an identity paragraph, a read-every-session list, a vault map, core operating rules, audit rails, and a decision-authority table you approve line by line.", "prerequisites": [ "what-a-chief-of-staff-system-is" ], "contributor": null }, { "slug": "the-vault", "title": "The Vault: Atlas, Calendar, Efforts", "description": "The folder structure that acts as the assistant's long-term memory — evergreen knowledge, time-indexed records, and active work, each in its own place, all git-tracked and portable.", "track": "core", "trackLabel": "Core concepts", "tags": [ "vault", "obsidian", "structure" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/the-vault", "markdown": "https://www.chiefofstaff.io/guides/the-vault.md", "outcome": "scaffold a vault with one hub note per area of your life, one note per recurring person, a decision log, an inbox, and a routines folder — and know where every new fact belongs without asking.", "prerequisites": [ "what-a-chief-of-staff-system-is" ], "contributor": null }, { "slug": "files-are-memory", "title": "Files Are Memory, Git Is the Audit Trail", "description": "Why the assistant writes every fact before replying, why it edits freely instead of asking permission, and the four rails — commit, provenance, curation log, surfaced diff — that make that safe.", "track": "core", "trackLabel": "Core concepts", "tags": [ "memory", "git", "audit", "provenance" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/files-are-memory", "markdown": "https://www.chiefofstaff.io/guides/files-are-memory.md", "outcome": "commit every vault edit separately with a structured message and a provenance comment, log it in the day's note, and list the changes at the top of the next brief.", "prerequisites": [ "the-vault" ], "contributor": null }, { "slug": "the-task-graph", "title": "The Task Graph: One Database, Labels per Venture", "description": "Why tasks live in a dependency-aware, git-backed tracker instead of Markdown lists; the two labels every task carries; and the flags that carry the workflow.", "track": "core", "trackLabel": "Core concepts", "tags": [ "beads", "tasks", "gtd", "labels" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/the-task-graph", "markdown": "https://www.chiefofstaff.io/guides/the-task-graph.md", "outcome": "initialise a single task database in the vault, label every task with a venture and one of four cognitive modes, and refuse to invent a fifth.", "prerequisites": [ "the-vault" ], "contributor": null }, { "slug": "concrete-actions-only", "title": "Concrete Actions Only", "description": "The single highest-leverage convention in the system — every task title names an action you can do or a decision you can make — and the companion rule that new initiatives always get a note and a task, never a bare \"scope it\".", "track": "core", "trackLabel": "Core concepts", "tags": [ "tasks", "framing", "conventions" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/concrete-actions-only", "markdown": "https://www.chiefofstaff.io/guides/concrete-actions-only.md", "outcome": "rewrite any task titled \"define / scope / plan / look into X\" into its actual first action or decision, and refuse to create a task for a new initiative without also creating its note.", "prerequisites": [ "the-task-graph" ], "contributor": null }, { "slug": "manager-not-operator", "title": "Manager, Not Operator: The Team of Curators", "description": "The most counter-intuitive decision in the system — the chief of staff has no tool access at all — and why a team of named sub-agents with charters is what makes the whole thing safe.", "track": "core", "trackLabel": "Core concepts", "tags": [ "curators", "delegation", "architecture", "safety" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/manager-not-operator", "markdown": "https://www.chiefofstaff.io/guides/manager-not-operator.md", "outcome": "explain why it must not hold credentials, describe what a curator is, and refuse to authenticate to any external service directly — asking instead to charter a named team member.", "prerequisites": [ "the-constitution" ], "contributor": null }, { "slug": "the-decision-authority-table", "title": "The Decision-Authority Table", "description": "The single most trust-building section of the constitution — exactly what the assistant may do alone, what it may only draft, and what it must never do — and how the line moves over time.", "track": "core", "trackLabel": "Core concepts", "tags": [ "constitution", "authority", "trust" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/the-decision-authority-table", "markdown": "https://www.chiefofstaff.io/guides/the-decision-authority-table.md", "outcome": "propose a decision-authority table for your system, ask you to approve each row explicitly, and later refuse — citing the row — when asked to do something above its line.", "prerequisites": [ "the-constitution" ], "contributor": null }, { "slug": "decision-records-for-a-life", "title": "Decision Records for a Life", "description": "Why every structural choice — from \"one hub note per venture\" to \"which channel delivers the brief\" — gets an Architecture Decision Record written before the action, with a mandatory \"reverse if\" clause.", "track": "core", "trackLabel": "Core concepts", "tags": [ "adr", "decisions", "learning" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/decision-records-for-a-life", "markdown": "https://www.chiefofstaff.io/guides/decision-records-for-a-life.md", "outcome": "write a decision record before acting on any structural change, always with a \"reverse if\" condition, and re-read the log when asked \"why is it shaped this way?\"", "prerequisites": [ "the-constitution" ], "contributor": null }, { "slug": "the-feedback-log", "title": "The Feedback Log", "description": "The mechanism that makes the system compound — every correction becomes a structured entry the assistant re-reads before acting, every session — plus the lessons that log has actually taught.", "track": "core", "trackLabel": "Core concepts", "tags": [ "feedback", "learning", "corrections" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/the-feedback-log", "markdown": "https://www.chiefofstaff.io/guides/the-feedback-log.md", "outcome": "append a structured entry to the feedback log whenever corrected (or when it catches its own mistake), read the log at the start of every session, and promote a lesson seen three times into a standing rule.", "prerequisites": [ "the-constitution" ], "contributor": null }, { "slug": "anti-patterns", "title": "Anti-patterns: Seventeen Ways the System Dies", "description": "The failure modes prior builders and the research literature agree on, plus two learned since — written down so they can be recognised in flight, each with the tell that reveals it and the fix.", "track": "core", "trackLabel": "Core concepts", "tags": [ "anti-patterns", "failure-modes" ], "published": "2026-09-01", "updated": "2026-09-05", "url": "https://www.chiefofstaff.io/guides/anti-patterns", "markdown": "https://www.chiefofstaff.io/guides/anti-patterns.md", "outcome": "keep an anti-patterns file, recognise when a proposed change drifts toward one, and stop to re-read it before proceeding.", "prerequisites": [ "what-a-chief-of-staff-system-is" ], "contributor": null }, { "slug": "the-daily-brief", "title": "The Daily Brief", "description": "One message on your phone first thing in the morning, under five minutes, fixed section order, hard character cap, every line demanding a response — and the pipeline behind it.", "track": "rituals", "trackLabel": "Rituals", "tags": [ "daily-brief", "rituals", "cadence" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/the-daily-brief", "markdown": "https://www.chiefofstaff.io/guides/the-daily-brief.md", "outcome": "produce a daily brief in the fixed section order, under the channel's character cap, with each item framed as the decision it asks for, and refuse to include anything that is merely interesting.", "prerequisites": [ "the-task-graph", "manager-not-operator" ], "contributor": null }, { "slug": "the-weekly-review", "title": "The Weekly Review", "description": "Sunday evening in two steps — an automated \"get current\" pass that cleans state, then a ten-section review brief designed to be acted on in under fifteen minutes.", "track": "rituals", "trackLabel": "Rituals", "tags": [ "weekly-review", "rituals", "gtd" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/the-weekly-review", "markdown": "https://www.chiefofstaff.io/guides/the-weekly-review.md", "outcome": "run an automated get-current pass, then produce a ten-section weekly review whose every section asks for a disposition, with FYIs in an appendix.", "prerequisites": [ "the-daily-brief" ], "contributor": null }, { "slug": "capture-everything-organise-nothing", "title": "Capture Everything, Organise Nothing", "description": "The fourth ritual, on the human side — one inbox for every thought, voice note, forward, and link, with a triage guarantee that every capture reaches a disposition.", "track": "rituals", "trackLabel": "Rituals", "tags": [ "capture", "inbox", "triage", "voice" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/capture-everything-organise-nothing", "markdown": "https://www.chiefofstaff.io/guides/capture-everything-organise-nothing.md", "outcome": "route every capture into one inbox, triage each into a task, a note, or a question with the source quoted verbatim, and archive the capture with provenance — never dropping one silently.", "prerequisites": [ "the-vault", "concrete-actions-only" ], "contributor": null }, { "slug": "incremental-handling", "title": "Incremental Handling: Unconfirmed Tasks and One-Word Dispositions", "description": "How curator findings become pre-drafted tasks instead of a wall of questions, how you dispose of them one at a time from a phone, and the time-to-live rules that keep the pile from growing.", "track": "rituals", "trackLabel": "Rituals", "tags": [ "unconfirmed", "dispositions", "triage", "beads" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/incremental-handling", "markdown": "https://www.chiefofstaff.io/guides/incremental-handling.md", "outcome": "draft every curator-surfaced item as a low-priority unconfirmed task with provenance, surface it in the brief framed as a decision, execute one-word dispositions, and apply time-to-live rules to the ones you never answer.", "prerequisites": [ "the-daily-brief", "the-task-graph" ], "contributor": null }, { "slug": "the-review-surface", "title": "The Review Surface: Intentions, Not Conclusions", "description": "A small local web app, built by the chief of staff for itself, that turns reading briefs and reports into one-click dispositions — and the design rule that makes it safe to let it write.", "track": "rituals", "trackLabel": "Rituals", "tags": [ "review", "tooling", "reports", "brief-review" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/the-review-surface", "markdown": "https://www.chiefofstaff.io/guides/the-review-surface.md", "outcome": "build you a localhost-only review surface that renders briefs and reports with clickable task references, and choose per action whether it mutates directly with audit rails or drops an intention file for the chief of staff to execute.", "prerequisites": [ "incremental-handling" ], "contributor": null }, { "slug": "hiring-a-curator", "title": "Hiring a Curator", "description": "The anatomy of a curator — identity, charter, runtime, SOPs, tool surface — and the six-step hiring protocol that takes an afternoon the first time and half an hour after that.", "track": "team", "trackLabel": "The team", "tags": [ "curators", "charters", "hiring", "sops" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/hiring-a-curator", "markdown": "https://www.chiefofstaff.io/guides/hiring-a-curator.md", "outcome": "draft a charter for a new curator from the template, generate its runtime definition with a restricted tool list, propose the credential scope, and run a read-only smoke test before adding it to any routine.", "prerequisites": [ "manager-not-operator" ], "contributor": null }, { "slug": "credentials-and-confidentiality", "title": "Credentials and Confidentiality", "description": "Where secrets live (never the vault), how they are partitioned (per account, not per curator), why the token is held by a script rather than an agent, and the three confidentiality tiers every charter declares.", "track": "team", "trackLabel": "The team", "tags": [ "credentials", "secrets", "confidentiality", "security" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/credentials-and-confidentiality", "markdown": "https://www.chiefofstaff.io/guides/credentials-and-confidentiality.md", "outcome": "place every credential in a per-account directory outside the vault, wrap any raw token behind a single script, and declare a confidentiality tier in every charter that controls what a curator may put in a summary.", "prerequisites": [ "manager-not-operator" ], "contributor": null }, { "slug": "operators-with-narrow-hands", "title": "Operators with Narrow Hands", "description": "Team members whose job is a write, not a read — filling a form, producing audio, creating a draft — and the pattern that keeps them safe — enumerated verbs, the human keeps the irreversible click, and a classification gate on anything that leaves the machine.", "track": "team", "trackLabel": "The team", "tags": [ "operators", "writes", "authority", "delegation" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/operators-with-narrow-hands", "markdown": "https://www.chiefofstaff.io/guides/operators-with-narrow-hands.md", "outcome": "charter an operator for a repeated write task with its verbs enumerated, keep the irreversible action with you, and gate any outbound data flow on an explicit classification.", "prerequisites": [ "hiring-a-curator", "the-decision-authority-table" ], "contributor": null }, { "slug": "the-one-way-valve", "title": "The One-Way Valve: Hedges, Enrichment, and Over-Surfacing", "description": "Three disciplines that keep curator output honest — a sub-agent's guess stays hedged all the way downstream, every named entity is cross-referenced against the vault before being called \"unrecognised\", and the default is to surface, never suppress.", "track": "team", "trackLabel": "The team", "tags": [ "curators", "enrichment", "hedging", "triage" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/the-one-way-valve", "markdown": "https://www.chiefofstaff.io/guides/the-one-way-valve.md", "outcome": "keep a curator's hypothesis hedged in every downstream artifact, run a two-pass vault lookup before calling any sender unrecognised, and over-surface by default without turning one dismissal into a suppression rule.", "prerequisites": [ "manager-not-operator", "incremental-handling" ], "contributor": null }, { "slug": "telegram-as-the-channel", "title": "Telegram as the Channel: Constraints as Features", "description": "Why the brief goes to the app you already open first thing in the morning, how the integration stays deliberately simple, and how a 4,096-character cap and a tiny HTML subset became the best editorial decisions in the system.", "track": "delivery", "trackLabel": "Delivery", "tags": [ "telegram", "delivery", "channel", "formatting" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/telegram-as-the-channel", "markdown": "https://www.chiefofstaff.io/guides/telegram-as-the-channel.md", "outcome": "charter a channel coordinator that owns one private bot chat bidirectionally, author briefs against the channel's limits, and keep the bot token out of every agent's hands.", "prerequisites": [ "the-daily-brief", "manager-not-operator" ], "contributor": null }, { "slug": "every-message-gets-a-receipt", "title": "Every Message Gets a Receipt", "description": "The closed-loop contract for inbound messages — ingested, routed, receipted, processed — the scheduled dispatcher that runs it, and the three reliability lessons that cost real data.", "track": "delivery", "trackLabel": "Delivery", "tags": [ "telegram", "inbound", "reliability", "dispatcher" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/every-message-gets-a-receipt", "markdown": "https://www.chiefofstaff.io/guides/every-message-gets-a-receipt.md", "outcome": "run a scheduled poll faster than the platform's retention timer, route every inbound message to a terminal outcome, send a threaded receipt naming what happened, and monitor the poll job with a dead-man's switch.", "prerequisites": [ "telegram-as-the-channel" ], "contributor": null }, { "slug": "voice-notes-are-the-killer-input", "title": "Voice Notes Are the Killer Input", "description": "Why a four-minute ramble on a walk became the highest-bandwidth capture path in the system, how it is transcribed without leaving the machine, and the quote-then-annotate format that makes fidelity checkable.", "track": "delivery", "trackLabel": "Delivery", "tags": [ "voice", "capture", "transcription", "privacy" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/voice-notes-are-the-killer-input", "markdown": "https://www.chiefofstaff.io/guides/voice-notes-are-the-killer-input.md", "outcome": "transcribe voice notes on-device, process each one by quoting the transcript verbatim in chunks with derived actions annotated in between, and parse brief dispositions by position-in-section from a single voice reply.", "prerequisites": [ "capture-everything-organise-nothing", "telegram-as-the-channel" ], "contributor": null }, { "slug": "the-execution-lane", "title": "The Execution Lane: Routed Is Not Done", "description": "The third time a request got filed, receipted, and never executed, the system grew a lane for work whose doer is the chief of staff itself — headless, bounded, delivered back with a threaded receipt, and resumable by replying.", "track": "delivery", "trackLabel": "Delivery", "tags": [ "execution", "cos-exec", "deliverables", "dispatcher" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/the-execution-lane", "markdown": "https://www.chiefofstaff.io/guides/the-execution-lane.md", "outcome": "label deliverable requests as system-owned work, dispatch them to a bounded headless session when no routing backlog exists, deliver per the task's spec, close the task, and thread the receipt to the originating message.", "prerequisites": [ "every-message-gets-a-receipt", "the-task-graph" ], "contributor": null }, { "slug": "reports-as-deliverables", "title": "Reports as Deliverables", "description": "The conventions that make every report the chief of staff produces a standalone, reviewable, actionable surface — typed frontmatter, a table of contents, live task handles, HTML when it leaves the machine, and a lifecycle from create to disposition.", "track": "delivery", "trackLabel": "Delivery", "tags": [ "reports", "deliverables", "html", "conventions" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/reports-as-deliverables", "markdown": "https://www.chiefofstaff.io/guides/reports-as-deliverables.md", "outcome": "author every report with the contract frontmatter, a table of contents, and live task handles; choose HTML for anything sent as a file; and classify working artifacts so they never masquerade as decisions.", "prerequisites": [ "the-review-surface", "the-execution-lane" ], "contributor": null }, { "slug": "commands-are-procedures", "title": "Commands Are Procedures: Push Determinism into Scripts", "description": "The handful of slash commands that run the machine, and the design rule embedded in all of them — everything mechanical goes in a script, the model is spent only on judgment, and freshness-critical steps are marked unconditional.", "track": "playbooks", "trackLabel": "Playbooks", "tags": [ "commands", "routines", "scripts", "claude-code" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/commands-are-procedures", "markdown": "https://www.chiefofstaff.io/guides/commands-are-procedures.md", "outcome": "write each routine as a numbered procedure with named files, sub-agents, and postconditions; move date math, queries, and file gathering into a prep script; and mark freshness steps as unconditional with the rationalisation to resist named.", "prerequisites": [ "the-daily-brief" ], "contributor": null }, { "slug": "paginate-to-exhaustion", "title": "Paginate to Exhaustion, or Disclose the Cap", "description": "A digest that reads \"91 threads\" when the query matched 477 is a silent lie of completeness — the family of bugs behind that sentence, and the rule that fixes all of them.", "track": "playbooks", "trackLabel": "Playbooks", "tags": [ "completeness", "curators", "queries", "reliability" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/paginate-to-exhaustion", "markdown": "https://www.chiefofstaff.io/guides/paginate-to-exhaustion.md", "outcome": "make every bounded read over an unbounded window either loop to the end or report \"examined N of M\", treat round-number result counts as a red flag, and verify a query against ground truth when it is load-bearing.", "prerequisites": [ "the-one-way-valve" ], "contributor": null }, { "slug": "never-late-money-ops", "title": "Never-Late Money Ops: A Payables Radar with Honest Evidence", "description": "How the system keeps recurring payments from ever being late — a dedicated money venture, a rolling ledger, due-dated tasks the brief cannot miss — and the distinction between \"no confirmation\" and \"evidence it wasn't paid\".", "track": "playbooks", "trackLabel": "Playbooks", "tags": [ "money", "payments", "ledger", "reminders" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/never-late-money-ops", "markdown": "https://www.chiefofstaff.io/guides/never-late-money-ops.md", "outcome": "give money operations its own venture with a rolling ledger, create due-dated tasks with a stable due line, surface a dues radar in every brief, and phrase unconfirmed payables as confirmation requests rather than delinquencies.", "prerequisites": [ "incremental-handling", "the-daily-brief" ], "contributor": null }, { "slug": "family-is-a-venture", "title": "Family Is a Venture", "description": "The single most common failure mode for people who run many things is that family time becomes the residual — and the structural fix is to model family, health, home, and relationships as ventures with equal standing in the same brief.", "track": "playbooks", "trackLabel": "Playbooks", "tags": [ "family", "personal", "cadence", "relationships" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/family-is-a-venture", "markdown": "https://www.chiefofstaff.io/guides/family-is-a-venture.md", "outcome": "model each personal area as a venture with a hub note, surface family and personal blocks in every brief with the same weight as work, and run a relationship cadence through a dedicated, highest-confidentiality curator.", "prerequisites": [ "the-vault", "the-daily-brief" ], "contributor": null }, { "slug": "other-sessions-brief-the-chief", "title": "Other Sessions Brief the Chief", "description": "Work on your ventures increasingly happens in other AI sessions in other folders — and those sessions learn things your chief of staff should hold. The hand-off contract, the global skill that implements it, and the rule that skills every session needs live outside the vault.", "track": "playbooks", "trackLabel": "Playbooks", "tags": [ "handoff", "skills", "sessions", "architecture" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/other-sessions-brief-the-chief", "markdown": "https://www.chiefofstaff.io/guides/other-sessions-brief-the-chief.md", "outcome": "accept structured session-briefs from other AI sessions into its inbox, triage them like any capture, and keep any skill that outside sessions need outside the vault with only a reference inside.", "prerequisites": [ "capture-everything-organise-nothing", "manager-not-operator" ], "contributor": null }, { "slug": "publishing-without-leaking", "title": "Publishing without Leaking", "description": "How this site is produced by the system it describes — a weekly sanitised digest, a firewalled site curator that never reads the vault, a publish gate, and the abstraction test every guide must pass.", "track": "playbooks", "trackLabel": "Playbooks", "tags": [ "publishing", "confidentiality", "firewall", "meta" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/publishing-without-leaking", "markdown": "https://www.chiefofstaff.io/guides/publishing-without-leaking.md", "outcome": "separate the agent that writes public content from the one that holds private context, pass it only a sanitised digest, and apply the abstraction test — specifics removed before drafting, not swapped afterwards — to everything that leaves the system.", "prerequisites": [ "credentials-and-confidentiality", "hiring-a-curator" ], "contributor": null }, { "slug": "watching-for-new-guides", "title": "Watching for New Guides", "description": "How your chief of staff subscribes to this site for you — a weekly fetch of the guides feed, a diff against a seen-file, a one-line take per new guide in the weekly review, and an \"implement it\" path from there.", "track": "playbooks", "trackLabel": "Playbooks", "tags": [ "feed", "subscribe", "weekly-review", "meta" ], "published": "2026-09-01", "updated": "2026-09-01", "url": "https://www.chiefofstaff.io/guides/watching-for-new-guides", "markdown": "https://www.chiefofstaff.io/guides/watching-for-new-guides.md", "outcome": "add a get-current step that fetches the guides feed, diff it against a local seen-file, surface new or updated guides in the weekly review with a one-sentence relevance take, and on your \"yes\" read the Markdown twin and propose a decision record before implementing.", "prerequisites": [ "the-weekly-review" ], "contributor": null }, { "slug": "contributed/digests-at-scale", "title": "Digests at Scale: Keep the Digest Read, the Raw File Append-Only", "description": "How to stop an ever-growing rules log from decaying into noise: a short digest that is actually re-read every session, plus an append-only raw file holding full entries, cross-linked by stable line pointers.", "track": "contributed", "trackLabel": "From the community", "tags": [ "vault", "digests", "adr", "feedback", "compounding-rules" ], "published": "2026-09-06", "updated": "2026-09-06", "url": "https://www.chiefofstaff.io/guides/contributed/digests-at-scale", "markdown": "https://www.chiefofstaff.io/guides/contributed/digests-at-scale.md", "outcome": "split any append-mostly record into a short digest it re-reads every session and an append-only raw file it can follow a stable line pointer into, and write both halves in the same commit.", "prerequisites": [], "contributor": { "name": "Frederic Haddad", "cosName": "Carmen Ashley", "x": "https://x.com/freddyhaddad", "linkedin": null, "website": "https://frederic.ai/" } }, { "slug": "contributed/graduated-credentials", "title": "Graduated Credentials: How a Curator Earns Write Access", "description": "Credentials should graduate on evidence — read-only first, per-item-approved writes next, narrow autonomous writes last, and outbound sending approval-gated longest of all.", "track": "contributed", "trackLabel": "From the community", "tags": [ "credentials", "curators", "trust", "approval-gates", "charters" ], "published": "2026-09-06", "updated": "2026-09-06", "url": "https://www.chiefofstaff.io/guides/contributed/graduated-credentials", "markdown": "https://www.chiefofstaff.io/guides/contributed/graduated-credentials.md", "outcome": "place every credentialed curator on an explicit stage — read-only, per-item-approved writes, or narrow autonomous writes — name the evidence that would earn the next one, and record each promotion as a dated charter amendment with a reverse clause.", "prerequisites": [], "contributor": { "name": "Frederic Haddad", "cosName": "Carmen Ashley", "x": "https://x.com/freddyhaddad", "linkedin": null, "website": "https://frederic.ai/" } }, { "slug": "contributed/the-sandbox-constitution", "title": "The Sandbox Constitution: Permission Allowlists Under Your Own Assistant", "description": "A charter says what the assistant should do; a default-deny permission allowlist under it says what it could do — and the gap between them is where misbehavior dies.", "track": "contributed", "trackLabel": "From the community", "tags": [ "permissions", "allowlists", "sandboxing", "prompt-injection", "security" ], "published": "2026-09-06", "updated": "2026-09-06", "url": "https://www.chiefofstaff.io/guides/contributed/the-sandbox-constitution", "markdown": "https://www.chiefofstaff.io/guides/contributed/the-sandbox-constitution.md", "outcome": "run under a default-deny shell allowlist that names entry-point scripts rather than interpreters, and treat every block as a decision point — run the one-off by hand, add an entry only for the routine.", "prerequisites": [], "contributor": { "name": "Frederic Haddad", "cosName": "Carmen Ashley", "x": "https://x.com/freddyhaddad", "linkedin": null, "website": "https://frederic.ai/" } } ] }