The vault 146 files

Demo / the vault

Calendar/daily/2026-09-22.md

Tuesday 22 September

Session opened 06:30 on Rowan’s stated time. The twelfth anniversary. The machine clock still reads 5 September (hobbs-bkt, seventeen days at P1); every date here comes from his sentence or from the vault.

Brief delivered first, then the roster.

What Rowan gave, in his words

“You have been a manager with no staff for seventeen days. Every week you tell me the same thing in a different sentence: a dozen of the items you are tracking live in an account or a calendar you cannot read. I want that fixed properly, not one curator every six weeks.”

“Charter the whole team. Not credentials — I know row 2 and I know ADR-20, and I am not handing you a password this morning. I want the charters written and argued now, so that on the day I do hand one over, the scope is already on paper and I am only saying yes to something I have already read.”

“Signal. Priya and Claire reach me there and nowhere else, and it is the only place my sister talks to me as my sister. Tell me whether that should have a curator at all. If your answer is no, write the no down in the file with the reasoning, so nobody reopens it in a year — including me.”

“I fail the people who do not send a second message. That is the reason you exist. If there is a role whose entire job is watching for the quiet ones, charter it.”

“Do not invent findings and hand them to me as real ones. If you have to stand in fake data to show me the shape, label it so plainly that neither of us could ever mistake it for a return.”

Curation log

FileChangeSource
Calendar/briefs/archive/2026-09-22.mdThe tenth brief, first in four daysRowan, 2026-09-22
Efforts/dispositions/2026-09-22-brief.jsonEight asks, written in the same pass as the brief (ADR-29 clause 2)the brief
Atlas/decisions.mdADR-30 — the whole team chartered in one pass; two roles refused or blocked; one needs no credential. Written before the actionRowan, 2026-09-22
Atlas/team/_TEMPLATE.mdThe normative charter template, ten sections in the order they must be readADR-30 clause 2
Atlas/team/quiet.mdWren — the second-message curator. No credential, no blast radius, grantable todayRowan, 2026-09-22
Atlas/team/signal.mdThe refusal, written as a charter, with its only reopening conditionsRowan, 2026-09-22
Atlas/team/calendar-rowan.md · calendar-maya.mdBell and MarshADR-30
Atlas/team/school-calendar.md · voicemail-mobile.md · whatsapp-robotics.mdTerm, Tape, CrowdADR-30
Atlas/team/workspace-halcyon.md · drive-halcyon.md · linear-halcyon.md · slack-halcyon.md · github-halcyon.md · notion-bedrock.mdWard, Shelf, Rail, Hall, Forge, StrataADR-30
Atlas/team/bank-business.md · bank-personal.md · brokerage.md · carta.mdTill (four instances), Coin, Book, SliceADR-30
Atlas/team/INDEX.mdRewritten — eighteen rows, four statuses, the re-set hiring order with a reason per rowADR-30 clause 9
Efforts/reports/specimen-2026-09-23-brief-with-curators.mdThe labelled specimen, and §3’s arithmeticRowan, 2026-09-22
Efforts/feedback.md[SELF-FLAGGED] — a task handle written into a charter before the task existed, and the corrected occurrence countthis session
HOME.mdA Team sectionADR-30

Tasks: hobbs-0w4 (approve Wren) · hobbs-wkj (approve Term) · hobbs-yqx (the hiring order) · hobbs-9k5 (daily rotation, before the third grant). Dispositioned in the same session, per weekly-review step 1.8: hobbs-oou, hobbs-svx, hobbs-78f, hobbs-1hl, hobbs-9cy, hobbs-3ah.

Notes on the day

  • [SELF-FLAGGED] SL-01, sixth invented handle. hobbs-p9c was written into Atlas/team/quiet.md §10 before any task existed, to fill a slot in a sentence. The real one is hobbs-0w4. Caught before the commit, not before the write. And the first draft of the log entry said “fourth occurrence,” produced from a sense of how many there had been — corrected by grepping the log’s own headings. A miscount inside an entry about producing identifiers. Logged first, per rule 12, and the pre-commit phantom-handle check is in the entry. The template was amended in the same session, because it told its reader to name handles in §10 and did not tell them to create the tasks first — a template that reproduces a known failure in every future charter is the worse defect.

  • Three findings the one-at-a-time pace would not have produced, and they are the argument for having done it in one pass:

    1. ADR-20 is wrong that a calendar curator makes authority row 10 automatic. Moving the all-hands is a write; Bell is calendar.readonly. Granting Bell does not unlock row 10, and anyone reading ADR-20 in six months would conclude otherwise. hobbs-svx updated to say so.
    2. The surface budgets are individually right and collectively impossible. They sum to 33 lines of daily brief against a ~4,000-character cap that today’s brief already overruns with zero curator input. The cap is not the constraint; rotation is — and the safeguard is that Wren is in daily rotation permanently, because a subset chosen for volume is exactly the instinct ADR-10 inverts. hobbs-9k5, and it needs an ADR before the third grant.
    3. Two rows need no credential and neither was on ADR-20’s list, because neither is an account. Wren and Term can start on a sentence.
  • The Signal answer is no, and §5 of that file is why rather than §2. §2 is the decisive argument — every read path carries send, so ADR-04’s guarantee that a compromised curator can at worst misread is false there and true everywhere else on the roster. But §5 is the finding: every Signal-shaped failure in this vault is outbound. hobbs-0dv at seventeen days, hobbs-xkw at nine, hobbs-m9x, hobbs-s7r — all unsent, all his. And the Claire signal does not arrive on Signal either; it arrives on the phone. A reader would not have moved one of them. What the no costs is priced in §6 rather than waved away.

  • What was not done, and it is the whole of the discipline here. No credential was issued. No OAuth flow was run. No runtime file was generated for any of the eighteen — seventeen inert .claude/agents/ files would be seventeen tool surfaces on disk waiting for a token, and generating a runtime is part of a grant, not part of a charter (ADR-30 clause 8). Against the guide’s six-step protocol the vault has moved from steps 1–2 of 6 on one curator to steps 1–2 of 6 on eighteen, and no further.

  • The specimen is not in Calendar/briefs/archive/ and that is deliberate. That directory is every brief ever delivered and is the corpus Wren’s SOP-3 runs on. A fabricated brief in it would poison the one sweep written to catch the half-done. It lives in Efforts/reports/, every invented line is marked [INVENTED], and every back-reference in it is a deliberately impossible string.

  • What the roster does not touch, stated because it is the sharpest thing in today’s brief. hobbs-0dv — Nikhil, the pro-rata, seventeen days, the believed deadline four days gone. No curator on this roster would have moved it. It is one message from Rowan, and the whole apparatus written this morning is silent on it. The specimen’s §5 says the same thing about the six logged failures of the last seventeen days: every one is an attention failure inside a system that already had the fact, and Wren is the only row aimed at that class.

Markdown source
---
type: daily
date: 2026-09-22
day: Tuesday
updated: 2026-09-22
---

# Tuesday 22 September

Session opened 06:30 on Rowan's stated time. **The twelfth anniversary.** The
machine clock still reads 5 September (`hobbs-bkt`, seventeen days at P1); every
date here comes from his sentence or from the vault.

Brief delivered first, then the roster.

## What Rowan gave, in his words

<!-- src: Rowan, Tuesday morning 2026-09-22 -->

> "You have been a manager with no staff for seventeen days. Every week you tell
> me the same thing in a different sentence: a dozen of the items you are tracking
> live in an account or a calendar you cannot read. I want that fixed properly,
> not one curator every six weeks."

> "Charter the whole team. Not credentials — I know row 2 and I know ADR-20, and I
> am not handing you a password this morning. I want the charters written and
> argued now, so that on the day I do hand one over, the scope is already on paper
> and I am only saying yes to something I have already read."

> "Signal. Priya and Claire reach me there and nowhere else, and it is the only
> place my sister talks to me as my sister. Tell me whether that should have a
> curator at all. If your answer is no, write the no down in the file with the
> reasoning, so nobody reopens it in a year — including me."

> "I fail the people who do not send a second message. That is the reason you
> exist. If there is a role whose entire job is watching for the quiet ones,
> charter it."

> "Do not invent findings and hand them to me as real ones. If you have to stand
> in fake data to show me the shape, label it so plainly that neither of us could
> ever mistake it for a return."

## Curation log

| File | Change | Source |
|---|---|---|
| `Calendar/briefs/archive/2026-09-22.md` | The tenth brief, first in four days | Rowan, 2026-09-22 |
| `Efforts/dispositions/2026-09-22-brief.json` | Eight asks, written in the same pass as the brief (ADR-29 clause 2) | the brief |
| `Atlas/decisions.md` | **ADR-30** — the whole team chartered in one pass; two roles refused or blocked; one needs no credential. Written before the action | Rowan, 2026-09-22 |
| `Atlas/team/_TEMPLATE.md` | The normative charter template, ten sections in the order they must be read | ADR-30 clause 2 |
| `Atlas/team/quiet.md` | **Wren** — the second-message curator. No credential, no blast radius, grantable today | Rowan, 2026-09-22 |
| `Atlas/team/signal.md` | **The refusal**, written as a charter, with its only reopening conditions | Rowan, 2026-09-22 |
| `Atlas/team/calendar-rowan.md` · `calendar-maya.md` | **Bell** and **Marsh** | ADR-30 |
| `Atlas/team/school-calendar.md` · `voicemail-mobile.md` · `whatsapp-robotics.md` | **Term**, **Tape**, **Crowd** | ADR-30 |
| `Atlas/team/workspace-halcyon.md` · `drive-halcyon.md` · `linear-halcyon.md` · `slack-halcyon.md` · `github-halcyon.md` · `notion-bedrock.md` | **Ward**, **Shelf**, **Rail**, **Hall**, **Forge**, **Strata** | ADR-30 |
| `Atlas/team/bank-business.md` · `bank-personal.md` · `brokerage.md` · `carta.md` | **Till** (four instances), **Coin**, **Book**, **Slice** | ADR-30 |
| `Atlas/team/INDEX.md` | Rewritten — eighteen rows, four statuses, the re-set hiring order with a reason per row | ADR-30 clause 9 |
| `Efforts/reports/specimen-2026-09-23-brief-with-curators.md` | The labelled specimen, and §3's arithmetic | Rowan, 2026-09-22 |
| `Efforts/feedback.md` | `[SELF-FLAGGED]` — a task handle written into a charter before the task existed, and the corrected occurrence count | this session |
| `HOME.md` | A Team section | ADR-30 |

**Tasks:** `hobbs-0w4` (approve Wren) · `hobbs-wkj` (approve Term) · `hobbs-yqx`
(the hiring order) · `hobbs-9k5` (daily rotation, before the third grant).
**Dispositioned in the same session, per weekly-review step 1.8:** `hobbs-oou`,
`hobbs-svx`, `hobbs-78f`, `hobbs-1hl`, `hobbs-9cy`, `hobbs-3ah`.

## Notes on the day

- **[SELF-FLAGGED] SL-01, sixth invented handle.** `hobbs-p9c` was written into
  `Atlas/team/quiet.md` §10 before any task existed, to fill a slot in a sentence.
  The real one is `hobbs-0w4`. Caught before the commit, not before the write.
  **And the first draft of the log entry said "fourth occurrence," produced from a
  sense of how many there had been** — corrected by grepping the log's own
  headings. A miscount inside an entry about producing identifiers. Logged first,
  per rule 12, and the pre-commit phantom-handle check is in the entry.
  **The template was amended in the same session**, because it told its reader to
  name handles in §10 and did not tell them to create the tasks first — a template
  that reproduces a known failure in every future charter is the worse defect.

- **Three findings the one-at-a-time pace would not have produced**, and they are
  the argument for having done it in one pass:

  1. **ADR-20 is wrong that a calendar curator makes authority row 10 automatic.**
     Moving the all-hands is a **write**; Bell is `calendar.readonly`. Granting
     Bell does not unlock row 10, and anyone reading ADR-20 in six months would
     conclude otherwise. `hobbs-svx` updated to say so.
  2. **The surface budgets are individually right and collectively impossible.**
     They sum to **33 lines** of daily brief against a ~4,000-character cap that
     today's brief already overruns with zero curator input. **The cap is not the
     constraint; rotation is** — and the safeguard is that Wren is in daily
     rotation permanently, because a subset chosen for volume is exactly the
     instinct ADR-10 inverts. `hobbs-9k5`, and it needs an ADR before the third
     grant.
  3. **Two rows need no credential and neither was on ADR-20's list**, because
     neither is an account. **Wren** and **Term** can start on a sentence.

- **The Signal answer is no, and §5 of that file is why rather than §2.** §2 is the
  decisive argument — every read path carries send, so ADR-04's guarantee that *a
  compromised curator can at worst misread* is false there and true everywhere
  else on the roster. But **§5 is the finding**: every Signal-shaped failure in
  this vault is **outbound**. `hobbs-0dv` at seventeen days, `hobbs-xkw` at nine,
  `hobbs-m9x`, `hobbs-s7r` — all unsent, all his. **And the Claire signal does not
  arrive on Signal either; it arrives on the phone.** A reader would not have moved
  one of them. **What the no costs is priced in §6 rather than waved away.**

- **What was not done, and it is the whole of the discipline here.** No credential
  was issued. No OAuth flow was run. **No runtime file was generated for any of the
  eighteen** — seventeen inert `.claude/agents/` files would be seventeen tool
  surfaces on disk waiting for a token, and generating a runtime is part of a
  grant, not part of a charter (ADR-30 clause 8). Against the guide's six-step
  protocol the vault has moved **from steps 1–2 of 6 on one curator to steps 1–2
  of 6 on eighteen**, and no further.

- **The specimen is not in `Calendar/briefs/archive/` and that is deliberate.**
  That directory is every brief ever delivered and is the corpus Wren's SOP-3 runs
  on. A fabricated brief in it would poison the one sweep written to catch the
  half-done. It lives in `Efforts/reports/`, every invented line is marked
  `[INVENTED]`, and every back-reference in it is a deliberately impossible string.

- **What the roster does not touch, stated because it is the sharpest thing in
  today's brief.** `hobbs-0dv` — Nikhil, the pro-rata, seventeen days, the believed
  deadline four days gone. **No curator on this roster would have moved it.** It is
  one message from Rowan, and the whole apparatus written this morning is silent
  on it. The specimen's §5 says the same thing about the six logged failures of the
  last seventeen days: every one is an attention failure inside a system that
  already had the fact, and **Wren is the only row aimed at that class.**