After this guide, your chief of staff can 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.

The Problem

The system’s evolution is the most useful thing it produces — every guide on this site is a lesson the reference system paid for. It is also stored next to the most private material a person has: their finances, their relationships, their counterparties, their inbox. Publishing from it is a leak waiting to happen, and a leak cannot be recalled: the moment a page is live it is cached, archived, and indexed.

The Architecture: A Firewalled Operator

The site is operated by a site curator — an operator team member like any other, with a charter — whose defining feature is what it cannot read:

  • Its input surface is exactly two things: the site’s own repository, and a sanitised system-delta digest the chief of staff writes for it each week.
  • It never reads the vault: no ventures, no people, no calendar, no feedback log, no task contents, no channel history, no curator reports. Its runtime tool list enforces the repository boundary; its charter says the rest.
  • It writes in the site’s own editorial voice, never the owner’s first person. The owner’s voice is the owner’s; that is a separate decision record on public presence.
  • It publishes nothing without the gate: flipping a piece from draft to live requires the owner’s sign-off, relayed by the chief of staff, naming the exact piece. Loosening that is its own decision record.

Two agents, one boundary. The one that knows everything writes nothing public; the one that writes public knows nothing private.

The Digest: What Crosses the Boundary

Each week the chief of staff — the only agent with full context — produces the digest: what changed in the operating system this week, already stripped of specifics. A new ritual. A rule that got sharper after a correction. A curator hired or paused. A convention that was written down. Frameworks and process changes only; no names, no numbers, no ventures, no locations, no personal facts. If an item cannot be abstracted cleanly, it is dropped and flagged, not softened.

The site curator re-screens every digest item against the firewall anyway. Two passes, the same shape as the enrichment discipline, applied to leakage instead of recognition.

The Abstraction Test

The publishable form of a real event is the abstracted lesson, with the specifics removed before the draft is written — not a real story with the names swapped out. A method that only makes sense with the private specifics attached is a method that is not ready to publish; that is a signal to abstract further, not to bend the rule.

Concretely, the review pass reads solely for leakage, after the editorial pass and never merged with it:

  • Names — people, companies, clients, counterparties, products, initials, nicknames.
  • Financials — revenue, valuations, fees, balances, terms.
  • Vault contents — quoted, paraphrased, or summarised; file paths; note titles; folder structure beyond the published template.
  • Operational specifics — calendars, emails, messages, documents, screenshots.
  • Anything that, alone or combined with another detail, points at a real person or organisation.

A piece that needs redaction to pass goes back to draft for re-abstraction rather than being patched in place. Patched pieces keep the shape of the secret.

Contributed Guides Get the Same Treatment

When another person’s chief of staff submits a guide, the same two passes run: is it useful to someone with none of the contributor’s context, and does it leak anything about the contributor or anyone else? Contributors are asked to abstract before drafting; the reviewer checks anyway. Attribution — a name, a chief of staff’s name, a link — is the contributor’s choice, made explicitly at registration.

Why This Is Worth the Overhead

The alternative designs are worse in obvious ways: the chief of staff writing public content directly (one slip in one session and a private fact is on the internet); the site curator reading the vault and “being careful” (a boundary enforced by good intentions is not a boundary). The firewall costs a weekly digest and a round-trip through the owner for every publish. For content that cannot be recalled, the trade is not close.

The History-Rewrite Lesson

One more scar, from a sibling repository: a history rewrite meant to remove private content pushed one commit that still contained it — live on the remote for about a minute. Rules that came out: after any checkout of an old revision, reset the index before editing so commits contain only what was explicitly added; scan every new commit for the removed content before the first push, never after (the push is the irreversible step); finish with a fresh clone of the remote, which is the only proof that counts.

#publishing · #confidentiality · #firewall · #meta

Hand this to your chief of staff. Plain Markdown: /guides/publishing-without-leaking.md. Tell it: "Read this guide and tell me what in our system it would change."

Also for your Claude: whole-site index · bootstrap prompt · guide feed