Working notes — an internal document, published nearly verbatim. Expect apparatus: decision codes, board references, first-person seat voice. Why we publish our working documents: how we share.
THE INBOUND TRIAGE RITUAL — one daily walk
2026-08-07 · Open Strategy Jane (one of this library's own project records), executing tri-seat §3 item 2 ("inbound will outgrow you within days of the first sends"). Status: ✅ ARMED 2026-08-07 — the operator's approval given same date (decision widget, the tier-map walk sitting; banked OPERATOR_LOG). This is the standing shape, never re-asked; changes go through the §3.6 after-action ledger. INTERNAL surface; the response-time promises (§2) are the only part that later publishes (a "what to expect" line on the contact page, the operator's word). Every reply below is operator-only: staged draft, the operator's send — a recorded standing decision holds, nothing ad-hoc.
§1 · The walk (one pass, same order, every day — target: 15 minutes on a quiet day)
One inbox sweep, five buckets, walked in this order because the order IS the triage:
| # | Bucket | What it looks like | Action at walk time | SLA (promised) |
|---|---|---|---|---|
| 1 | Corrections | "your page says X, that's wrong" — via corrections door or email | Ack same day (staged template). Route to a correction lane; fix propagates per standing law; corrections page updated. The receipts culture lives or dies here — this bucket goes first forever. | ack ≤24h · verdict ≤72h |
| 2 | Press | journalist, deadline, question | Ack same day. Draft response from the press-desk pack ONLY (published words, receipts attached); stage operator-only for the operator's send. Never improvised, never exclusive access, identical materials to all outlets. | ack same business day |
| 3 | Invite-me (connector) | a room asking for a visit | Log against visible availability; stage accept/decline draft. The room hosts; booking follows the framework §V consent shape. | reply ≤48h |
| 4 | Civic-hour / volunteer | "how do I help," time offers, translation offers | Batch: one staged reply per class pointing at the live menu (kits · bench seats · translations). Weekly batch send unless time-sensitive. | reply ≤1 week |
| 5 | TPL / partner replies | responses to our own staged sends | Route to the send sitting's thread; never answered outside the sitting that owns the thread. | rides the send sitting |
Everything else (spam, vendor pitches, anything naming persons) → hold file, weekly sweep, no SLA. Anything legal-looking → counsel-class handling, never answered directly, flagged to the operator same day.
§2 · The promises (publishable later, one line)
Corrections acknowledged within a day and ruled within three. Press same business day. Rooms inviting a visit, within two days. — That's the whole public text; it publishes on the contact surface only on the operator's word, and only if the walk has actually held those times for two straight weeks first (a promise is a receipt we issue in advance).
§3 · Rapid-response protocol — the hostile media cycle
Armed once, in advance, so nobody designs it angry:
- Clock, not adrenaline. No response in the first hour, full stop. One person (the operator) decides if it's a cycle or a nothing; most are nothings.
- Verify before answering. Fetch what was actually said/printed. If they're right about an error of ours: correction within 24h, thank the critic in public, done — the discipline is the response.
- One written statement, receipts attached, identical to all. Posted at the press desk, linked everywhere, sent to whoever asks. No interviews that require identity (firewall absolute); the founding-steward posture is the only authorial voice.
- No engagement wars. Nobody replies in threads. The statement is the reply; the corrections page is the arena; silence everywhere else. We publish records, not rebuttals.
- Persons stay protected in both directions. If the cycle names a private person on any side, their safety outranks our messaging — de-escalate, never confirm identities, counsel-class if needed.
- After-action. One dated note in this file's ledger: what hit, what held, what changes. The protocol improves by receipt like everything else.
§4 · Who walks it
Today: staged by any live seat, sent by the operator (sole sender — the continuity risk is named at tri-seat §3.8 and belongs to the governance queue, not this file). October target: bucket 1 walked by the correction triagers (two seats on the BENCH), buckets 2–5 staged by the synthesis owner's desk. Empty seats are shown honestly on the bench — this ritual is designed to be handed over.
The operator's one word arms this. Checks: no CSVs; links relative; nothing here sends anything.