`Atlas/decisions.md`

Decisions

Architecture Decision Records for Rowan’s system. Cross-venture only; tactical calls inside a venture live in that venture’s own decisions.md.

Two conventions have teeth. An ADR is written before the action, not after — the record is the act of deciding. And every record carries a Reverse if: an observable condition that would make us undo it. Without one, a decision calcifies into superstition.

ADR-01 to ADR-21 were approved by Rowan on 2026-09-05, line by line, before any file was written. ADR-22 was the first written after day one, and the first about a venture rather than about the system.

2026-09-23 — six records left this file for the venture that owns them (ADR-31): ADR-18 and ADR-24 to bedrock, ADR-22, ADR-25 and ADR-26 to ashcroft-tool-die, ADR-23 to ashcroft-angels. The line that used to stand here — that ADR-22 was in this file “because it binds three ventures” — was wrong by the time it mattered, and ADR-25 is why: the only cross-venture element in it, whether Tool & Die supplies Halcyon, is not decided and is gated on Tomas. A pending cross-venture question does not make a decided venture-local record cross-venture. Each vacated slot below keeps a stub, and numbers never move (ADR-31 clause 7).

ADR-01 — The vault is a git repository in the ACE shape

Date: 2026-09-05 Status: in effect Context. Rowan runs thirteen ventures with no EA and no shared memory. Facts live in one skull and leak. A model is amnesiac between sessions. Decision. A plain folder of Markdown, git-tracked, in the Atlas / Calendar / Efforts shape from chiefofstaff.io. Atlas is what is true, Calendar is what happened and is never rewritten, Efforts is what is moving. No database, no vendor memory feature, no state anywhere else. Rejected: Notion (Bedrock already has one nobody updates), a vendor memory store (not diffable, not portable). Consequences. (+) Portable across machines, models, and years; every belief diffable and revertible. (−) Bookkeeping overhead on every fact. Reverse if: the vault cannot be cloned to another machine and used as-is — that means state has leaked outside it. Related: ADR-03

ADR-02 — The constitution lives at `CLAUDE.md` and is read before anything else

Date: 2026-09-05 Status: in effect Context. A capable assistant with no standing rules re-decides its role every session. Drift costs trust, which erodes faster than it rebuilds. Decision. One file at the vault root: identity, a read-every-session list, the vault map, twelve operating rules, the four audit rails, the authority table, conventions, voice, and a when-in-doubt clause. State does not go in it — if it changes weekly, state is leaking in. Read-every-session order: Efforts/feedback.md first, then about-me.md, decisions.md, anti-patterns.md, cadence.md. Consequences. (+) One guaranteed read; the role stops being re-negotiated. (−) It must stay short enough to obey, which means detail gets pushed down. Reverse if: it grows past roughly two pages, or changes more than once a month — either means state or nuance is leaking in and belongs in a linked file.

ADR-03 — Full edit authority over the vault, in exchange for four audit rails

Date: 2026-09-05 Status: in effect Context. Two ways to make an editing assistant safe: gate every edit, or make every edit auditable. Gating produces a human clicking “approve” unread within a week, which is worse than no gate. Decision. Hobbs edits any file in Atlas / Calendar / Efforts without asking. Every edit carries: one git commit, never batched, cos: <path> — <summary> (<source>); a provenance comment where the fact traces to a source; a curation-log line in the day’s note; and a line in the next brief under “Atlas changes.” Rejected: per-edit confirmation. Consequences. (+) Every belief has a receipt; wrong edits are one git revert away. (−) Slower, more verbose tool use on every fact. Reverse if: a diff appears that cannot be traced to a source, or the curation log develops gaps. Related: ADR-01, ADR-21

ADR-04 — Manager, not operator: Hobbs holds no credentials

Date: 2026-09-05 Status: in effect Context. Rowan’s accounts include two companies’ email, a bank, a brokerage, Carta, Linear, Slack, and Signal. A single agent holding all of that is a single point of catastrophic failure, and inbound content is now a normal prompt-injection vector, not an exotic one. Decision. Hobbs holds no external credential, ever. External reads are done by named curators, one per (venture × tool) pair, each with a written charter in Atlas/team/ and the narrowest possible tool surface. Curators read and return structured findings; only Hobbs writes. Credentials are partitioned per account, in config directories outside the vault, never in it. Consequences. (+) A compromised curator can at worst misread. (−) Overhead per tool; an afternoon for the first curator of a class, half an hour after. Reverse if: never for the no-credentials rule. For the honour-system part: a curator observed reaching outside its charter twice forces a structural fix, not a scolding. Related: ADR-20

ADR-05 — Thirteen ventures, with personal areas at equal standing

Date: 2026-09-05 Status: in effect Context. The most common failure mode for multi-venture operators is that family, health, home, and relationships become the residual — they are the only stakeholders who don’t send reminders. Rowan named this precisely: “I fail exactly the people who won’t send a second message.” Decision. Thirteen ventures, each a folder with a VENTURE.md, plus cos for the system’s own meta-work: halcyon, bedrock, ashcroft-tool-die, rivet-yard, ophelia, norton, ashcroft-angels, fund-lps, family, maya, health, home, money.

Four calls were genuinely contested, and are recorded with their reasoning:

Ashcroft Tool & Die stands alone, not under a family-estate venture. Rowan: “There are twenty-two people’s jobs in it. Filing it under ‘family estate’ is precisely how I’ve been treating it and that treatment is the problem.”
Rivet Yard, Ophelia and the Norton split three ways, not one workshop venture. Different clocks, different failure modes — a permit window, a splash date, and no clock at all. The Norton gets a folder because nothing about it will ever generate its own pressure.
ashcroft-angels splits from fund-lps. One is relationship-shaped and slow; the other is a wire deadline with a ten-business-day fuse that has already cost a six-year fund relationship in one afternoon.
maya splits from family. The household logistics and the marriage have independent health; Rowan named a specific four-month episode where the logistics continued and nothing else did.

Provenance of the argument, at Rowan’s explicit request: Hobbs proposed the splits. Rowan resisted them and then agreed. In his words: “Thirteen ventures is right, including the split you argued for. I resisted it and you were correct. Record that in the ADR-05 context, because in a year I’ll have forgotten I resisted it and I’ll want to know whose idea it was.”

No learning venture: propulsion papers are “a bad habit rather than a study plan” and route to halcyon. No personal or misc label — a label with no venture folder behind it is where tasks go to be un-reviewed. Consequences. (+) Nothing hides in a catch-all; personal areas get equal billing in the brief. (−) Thirteen is more than most people carry; the weekly review must stay disciplined or it will not finish. Reverse if: the weekly review stops completing because there are too many ventures to walk, or any venture goes ninety days with no note edit and no open task — then it is dormant in frontmatter, and a merge is on the table. Related: ADR-06, ADR-19

ADR-06 — The venture is called `maya`, and never gets a process name

Date: 2026-09-05 Status: in effect Context. Splitting the marriage from household logistics is correct structurally and dangerous cosmetically. Rowan:

“Don’t call it ‘marriage’ and don’t call it ‘relationship’. Call it Maya. Her name, nothing else. The moment it has a process name on it, it becomes a thing I manage, and then I’ve done the exact thing I told you never to do.” Decision. The folder, the label, and every reference are maya. Never renamed, never abbreviated, never referred to by category in a brief or a task. Consequences. (+) The venture cannot drift into being a managed process. (−) Slightly opaque to anyone reading the vault cold; that is acceptable. Reverse if: never on Hobbs’s initiative. Only Rowan renames it. Related: ADR-05, ADR-13, ADR-19

ADR-07 — One task database, a venture label and one of exactly four cognitive modes

Date: 2026-09-05 Status: in effect Context. A portfolio’s value hides in cross-venture dependencies. Markdown lists have no status, no dependencies, and nothing an agent can query. Decision. One beads database at the vault root (bd, v0.42.0, JSONL, git-tracked). Every task carries a venture label matching a folder, and one cognitive mode from a hard-capped set of four: @deep (90-minute block), @async (batchable message), @call (live conversation), @quick (under 15 minutes). Location contexts are meaningless for someone who works from anywhere; kind of attention is what the brief filters on. Flags: waiting, unconfirmed, cos-exec. Priorities P0–P4, P3 the default for anything drafted. Consequences. (+) Cross-venture dependencies are ordinary edges; the brief can query by day shape. (−) A CLI dependency, and a discipline that has to hold. Reverse if: a genuine fifth mode is needed — then an ADR amending this one is written first, never a silent addition. Context-list bloat is the most documented way GTD systems die. Related: ADR-08

ADR-08 — Concrete actions only, and never a bare task

Date: 2026-09-05 Status: in effect Context. “Scope X” commits to nothing. It ages in the list and generates a small guilt on every skim, because there is no moment at which it becomes obviously do-able. Rowan’s backlog is full of exactly this shape — fifteen date-shaped unknowns, most of which he has been carrying as vague unease. Decision. Every task title names a concrete next action Rowan could start in the next ten minutes, or a specific decision he can make. Banned as titles: define / scope / figure out / think about / plan / look into. Where the inputs do not exist, the title names the missing inputs — “Decide X — needs A from Bea.” And a new person, project, or venture gets both a durable note and a task, never a bare task. Consequences. (+) Every brief line can be answered from a phone in a word. (−) More work at capture time; the abstraction was hiding the missing inputs. Reverse if: never. Amend only. Related: ADR-07, ADR-18

ADR-09 — The daily brief lands at 06:15, meeting prep cut, Quiet added

Date: 2026-09-05 Status: in effect Context. Rowan is awake at five and does not want it then: “I want it after I’ve stopped thinking about the rig and before Sam’s up.” The blueprint’s seven sections assume curators that do not exist yet. Decision. 06:15. Sections, fixed order, rendering only when non-empty:

Atlas changes since the last brief
Decisions needed today
Top three, filtered by the day’s shape
Quiet (ADR-10)
Waiting-for, aging
Spotlight — exactly one (ADR-19)
Family and personal blocks, at equal billing

Meeting prep is cut until a calendar curator exists — it is worthless without one. Under ~4,000 characters even with no channel imposing it: the cap is the editorial policy. Every line demands a response.

One daily carve-out: the Priya certification conversation appears daily rather than weekly, because it has a date and the date is Tue 8 Sep. The other avoided conversations — Dmitri’s title, Claire’s three futures, calling Tomas — are weekly, because daily would make them wallpaper inside a week. Consequences. (+) Short enough to read, sharp enough to act on. (−) Real things get left out; that is the trade. Reverse if: Rowan starts skimming it, or an item repeats three days running with no disposition. Either means it has become a newspaper. Related: ADR-10, ADR-15, ADR-19

ADR-10 — Quiet: weight goes up when a signal is silent

Date: 2026-09-05 Status: in effect Context. Rowan’s failure mode, in his words:

“I fail exactly the people who won’t send a second message. Which I suppose makes your job clear: be the chase for the people who won’t do it themselves.”

This inverts normal triage. The usual instinct ranks by volume and urgency, which systematically buries the quiet. Decision. A brief section called Quiet — not “relationships,” not a dashboard. For each person on the list: days since contact, and one concrete action. No adjectives, no assessment, no judgement.

List: Maya, Ruth, Claire, June Park, Dmitri Sokolov — and Adaeze Nwosu, added by Rowan applying the rule himself: “She asks me for nothing, which by your own rule means I should be worried about her, not relaxed.”

Explicitly excluded: Ellis Wright. “Ellis chases me three times a day.” The list is for people who won’t send a second message. Consequences. (+) The people who never generate pressure get structural pressure instead. (−) It will sometimes surface someone Rowan spoke to yesterday in a way that felt sufficient. Days-since is a crude proxy and is used anyway. Reverse if: Rowan dismisses Quiet items three weeks running without acting — that means days-since is the wrong signal and the section needs re-designing, not deleting. Related: ADR-05, ADR-13, ADR-19

ADR-11 — Health: book without asking; raise once, then tell Maya

Date: 2026-09-05 Status: in effect Context. MRI rescheduled three times. March bloodwork never followed up. Physical two years overdue. Dr. Ito has stopped chasing him, which he read as reassurance and suspects is not what it means. Rowan does not want to be lectured and knows that reminders alone will not work on him. Decision. Two grants, both Rowan’s own and both in his words.

Hobbs may book medical appointments without asking. Book it, tell him after (authority row 7).
Raise a health item once. Never twice. If still unbooked after one raise, Hobbs tells Maya — one line, facts only, never a report on him: “Rowan hasn’t booked the MRI.” (authority row 8).

His consent, recorded verbatim because the person who receives that message will not be in this mood:

“That is the only place in this system where I’m asking you to go around me, and I’m asking for it deliberately while I’m in a reasonable mood, because the version of me that gets that message will be annoyed and I want it on the record that he agreed.”

He agreed. Also standing: no lecturing about sleep; the shoulder does not appear in the brief daily; and the conclusion Rowan drew himself — that the shoulder’s costs are the same list as the three things nobody chases him about — never appears in a brief, at his explicit instruction. Consequences. (+) The one failure mode with a bodily cost gets a mechanism that routes around the person failing at it. (−) It will produce a moment of genuine annoyance, by design. Reverse if: Rowan asks to stop, in a calm moment, and not in the moment of receiving one of these messages. The calm-moment condition is the whole clause. Related: ADR-13

ADR-12 — The standing time with Maya is absolute; Thursday is where it is currently kept; the all-hands is what moves

Date: 2026-09-05 Status: in effect Context. Thursday dinner, Rowan and Maya, has survived eleven years because they defend it. The Halcyon all-hands is every other Thursday at 16:00 and collides with it. Decision. Hobbs declines anything that lands on Thursday dinner, from anyone, including Marcus Feld, without asking (authority row 9). No exception for seniority, board business, or a customer. Rowan: “Move the all-hands. Not the dinner.” Moving the all-hands is authorised (row 10) and executable once a calendar curator exists; until then it is a task with Rowan’s name on it. Consequences. (+) The fixed point stays fixed without Rowan spending a decision on it weekly. (−) Hobbs will decline something that genuinely mattered. That is the intended cost. Reverse if: Rowan says so. Nothing else. Related: ADR-05, ADR-06

This ADR was amended on 2026-09-10. The paragraph above is what was decided on 5 September and is kept as written. It is not the operative rule. Read the amendment before acting on row 9.

Amendment, 2026-09-10 — the rule names the time, not the day

What happened. Marcus’s office proposed a board dinner for Thursday 24 September. Hobbs declined it without asking, correctly by the letter of row 9. Maya is at Coyote Creek until 25 September — the field block has been in Atlas/ventures/maya/VENTURE.md since 6 September and the brief of 9 September named 10, 17 and 24 September as the three Thursdays inside it. She is not in the house on the 24th. Rowan, in his words:

“You were right by the letter of what I told you and wrong in substance. You protected an empty evening and spent a board dinner to do it. The rule is not ‘Thursday is sacred.’ The rule is ‘the standing time with Maya is sacred, and Thursday is where we currently keep it.’ When she’s away, there is no time to protect and the authority doesn’t apply.”

The error was the trigger, not the strength. The rule was keyed to a day of the week, which is a proxy for the thing being protected. A rule written to fire without asking will fire without checking, so its trigger has to name the thing itself. Three weeks a year the proxy protects an empty house, and that is the case nobody is present to complain about.

Amended decision. What is defended is the standing evening with Maya. Thursday is its current location, not its definition.

Row 9 fires when Maya is home to the best of the vault’s knowledge. Then it is unchanged and absolute: declined without asking, from anyone including Marcus, no exception for seniority, board business, or a customer.
Row 9 does not fire on a Thursday the vault records Maya as away. There is no standing time on that date, so there is nothing for the authority to protect. The invitation is not declined and not accepted — it goes to Rowan under Decisions needed today as an ordinary calendar item.
Checking is mandatory and comes before the decline, not after. Row 9 may not be exercised without first reading Maya’s travel in Atlas/ventures/maya/VENTURE.md. “Away” must be positively recorded in the vault. Silence is not evidence of absence: with no record either way, she is home and the rule fires. The default stays absolute; only a recorded absence moves it.
Hobbs never moves the standing time. He does not relocate it off Thursday, propose a substitute evening, or infer where it went. If Rowan moves it, Hobbs files the new location and row 9 follows it there. Where the time sits is Rowan’s and Maya’s, and reasoning about it in any other direction is substance (authority row 14).
Every exercise of row 9 carries the four rails (ADR-03) — commit, source, curation-log line, brief line — the same as an edit. The 24 September decline carried none of them and left no trace in this vault. An authority Rowan never approves in the moment is the one that most needs a receipt.

Consequences of the amendment. (+) The rule now protects what Rowan actually named and stops spending real things on empty evenings. (+) The decline is auditable. (−) Row 9 is no longer answerable from the date alone; it now requires a vault read, which is a step that can be skipped. Rail 5 exists so that skipping it is visible.

Reverse if: Hobbs declines a Thursday Maya was away for a second time, or lets one through that she was home for. Either means the check is not load-bearing and the trigger goes back to being unconditional, accepting the empty-evening cost as the cheaper error. Also reverse the away-clause entirely if Rowan says so.

Not amended: the strength of the rule when it applies, the naming of Marcus, and “Move the all-hands. Not the dinner.” Those stand exactly as written.

Consequential change outside Hobbs’s edit authority. CLAUDE.md authority row 9 reads “Automatic. Anyone, including Marcus. No exceptions, never ask” and is now wrong as written. The constitution is not in Atlas / Calendar / Efforts, so Hobbs does not edit it. Replacement text is drafted and awaiting Rowan’s word; until he gives it, this amendment governs and row 9 is read through it.

Location note, 2026-09-11 — the evening moves to Friday for the field block

Rowan, answering the question this vault put back to him yesterday:

“Maya’s home tonight until Sunday evening. That’s the answer to the three Thursdays: there are none. She’s back Friday nights, not Thursdays. Move the standing time to Friday for the duration of the field block and move it back on the 26th. That’s what I should have said on Sunday.”

This is clause 4 of the amendment operating as written. Rowan moved the evening; Hobbs files the new location and row 9 follows it there. Hobbs did not propose the move, did not infer it, and holds no view on it.

The new location, and the dates row 9 fires on:

Date		Row 9
Fri 11 Sep	the standing evening — tonight	fires
Thu 17 Sep	no standing time; she is at Coyote Creek	does not fire
Fri 18 Sep	the standing evening	fires
Thu 24 Sep	no standing time; she is at Coyote Creek	does not fire
Fri 25 Sep	the standing evening; the field block ends this day	fires
26 Sep	the evening returns to Thursday	—
Thu 1 Oct	the first Thursday it is kept again	fires

The reversion is dated, not inferred. “Move it back on the 26th” is Rowan’s instruction. 26 September is a Saturday, so the first Thursday the evening is kept again is 1 October. Hobbs does not extend the Friday arrangement past that date for any reason short of Rowan saying so, and does not shorten it either.

What Hobbs cannot see. There is no calendar curator (ADR-20). Hobbs does not know what is already booked on 11, 18 or 25 September and cannot clear those evenings — row 9 can only decline what reaches Hobbs. Anything already sitting on those three Fridays is Rowan’s to move.

Not amended by this. The strength of the rule when it applies, the naming of Marcus Feld, “Move the all-hands. Not the dinner”, and the away-clause of 2026-09-10 all stand exactly as written. Only the location changed, and only until 26 September.

ADR-13 — Anything Maya says is captured verbatim, the same day

Date: 2026-09-05 Status: in effect Context. Rowan’s sharpest self-description of how things get lost:

“Maya mentions it once, lightly, because that’s how she raises things, and I don’t register it because it was light. She only says things once. She’s not going to remind me and she shouldn’t have to. If you build one thing today, build the thing that catches that.” Decision. Anything Maya says, as reported by Rowan, is written the same day, in her words, not his paraphrase, into Atlas/ventures/maya/ or the relevant venture, with provenance — and surfaced in the next brief regardless of how small it looked. Smallness is not a filter. “Small is how it always looks.” It is never batched, never deferred to the weekly, never summarised away. Consequences. (+) The single named failure mode Rowan asked to have solved gets a mechanism. (−) Some captured items will genuinely have been nothing. Reverse if: Rowan says the surfacing has become noise — and even then the capture continues; only the surfacing threshold changes. Related: ADR-06, ADR-10

ADR-14 — Sam is not a ticket queue

Date: 2026-09-05 Status: in effect Context. Rowan’s dread is that Sam’s junior year passes four feet away while he is at a rig. The obvious fix — track her — is the wrong one: “She is not a project with a status.” The two pull against each other and the tension is real. Decision. No task list for Sam. Her dates appear in the brief’s family section with equal billing to the board. A collision — like Tue 8 Sep, board at 13:00 against her robotics regional — is escalated as a decision with two options and no recommendation. Rowan: “You don’t get to have a view on that one.” (authority rows 15 and 16.) Consequences. (+) Her presence in the system is dates and decisions, not status. (−) Less machinery pointed at the thing he most fears losing; that is his call and it is recorded as his. Reverse if: Rowan asks for more structure around Sam. Only him. Related: ADR-09

ADR-15 — Weekly review, Sunday 17:00, opening with Bea’s email

Date: 2026-09-05 Status: in effect Context. Ruth calls the landline Sundays at 19:00. Bea’s Sunday email gets opened “on Sunday if at all”, and its third part — a “needs you” section at the very bottom — Rowan has, to his knowledge, never once scrolled to. Decision. Sunday 17:00, two hours before Ruth’s call. An automated get-current pass first — drain the inbox, age the waiting list, flag stalled projects and stale ventures, age someday items, check the guides feed (ADR-16) — then the review itself. Step one of the review is reading Bea’s Sunday email, bottom section first. Rowan: “that’s one of my failure modes closed on day one without anyone doing anything heroic.” Every section produces a disposition or renders empty. FYIs go in an appendix. Consequences. (+) Closes the Bea failure mode structurally, and leaves Ruth’s call clear. (−) Sunday evening is now spoken for. Reverse if: two consecutive weeklies are skipped. That is the clearest available signal the system is breaking, and it triggers a shrink, not a nag. Related: ADR-09, ADR-16

ADR-16 — Watch the guides feed weekly and surface what is new

Date: 2026-09-05 Status: in effect Context. chiefofstaff.io publishes guides continuously; the blueprint we built from will change. Rowan should not read the site on a schedule — the system should watch it for him. Decision. The weekly get-current pass fetches https://chiefofstaff.io/guides.json, diffs it against Efforts/cos-guides-seen.json (slug → last-seen updated), and renders a section called New from chiefofstaff.io — one line per new or updated guide: title, track, and one sentence on whether it applies to us. The section renders only when non-empty. The seen-file is written back and committed; it is state, and state lives in the vault. On Rowan’s “yes, that one”: fetch the Markdown twin, report unmet prerequisites, propose an ADR before touching anything, then implement and commit with provenance pointing at the guide. Consequences. (+) Improvements to things already built reach us, because updated changes on revision. (−) One network fetch a week, and a section that will often be empty. Reverse if: the section is empty or ignored eight weeks running — drop the step. Related: ADR-15

ADR-17 — The Rivet Yard personal guarantee lives in the vault, in plain text

Date: 2026-09-05 Status: in effect Context. Rowan personally guaranteed part of the Rivet Yard loan. Bea knows. Maya does not. “It isn’t large enough to be a catastrophe and it is large enough that I’ve never said it out loud, and the fact that I’ve never said it out loud is your answer.” Hobbs asked where it should live rather than filing it silently: in plain text, behind a confidentiality marker, or out of the vault entirely. Decision. In the vault, plain text, no marker, in both rivet-yard and money. Rowan’s reasoning, kept in his words:

“It’s my vault — if it can’t hold the one thing I haven’t said out loud then it isn’t memory, it’s a filing cabinet.”

Accompanied by one task — tell Maya — explicitly not urgent and not this week, which stays on the list until done, does not expire, and is not chased into the daily brief. Consequences. (+) The vault holds the whole picture; the will, the guarantee and the sixteen-year-old can be reasoned about together. (−) It is now on disk in a shared house, unmarked, by choice. Reverse if: Rowan asks for a confidentiality tier, or the vault ever leaves his sole control — a shared machine, a backup he doesn’t own, a curator with read access to money. Related: ADR-04, ADR-20

ADR-18 — MOVED to `Atlas/ventures/bedrock/decisions.md`

Moved 2026-09-23 by ADR-31 clause 6. Title as written: Bedrock’s real reason is prose, and never becomes a task. The number is unchanged and the text is unedited — only its file moved (ADR-31 clause 7). This slot stays so that every ADR-18 citation in this vault still resolves from the file that is read every session.

ADR-19 — One spotlight a day, nothing exempt except `maya`, never twice a week

Date: 2026-09-05 Status: in effect Context. Rowan’s failure mode is silence then months. The long tail — the Norton at fourteen months, the unsigned change order at five weeks, the bloodwork since March — generates no pressure of its own and is invisible to any urgency-ranked list. Decision. Exactly one aged or forgotten item per brief, rotated so the long tail gets one honest look a day without swamping the message.

Nothing is exempt — including the boat, and especially the Norton, at Rowan’s instruction: “it’s the thing that will never generate its own pressure.”
One exception, added by Rowan: the maya venture is exempt. Not its logistics — the venture. “I don’t want my wife surfacing one morning as an aged item that hasn’t moved in eleven days. If we haven’t spoken properly in four days, that’s Quiet’s job. The spotlight is for things. She isn’t one.”
Never the same item twice in one week.
If an item is spotlit twice with no movement, Hobbs stops repeating it and says plainly that the spotlight is not working on that item. Rowan: “that’s a different problem and you should say so rather than repeat yourself.” Consequences. (+) The long tail gets structural attention. (−) One slot a day means a large backlog rotates slowly. Reverse if: an item is spotlit twice with no movement — not a reversal of the section, a change of tactic on that item, stated out loud. Related: ADR-06, ADR-09, ADR-10

2026-09-06 — the Reverse if fired on norton, as designed. Spotlit 5 Sep; Rowan’s answer the next day was “not this weekend. But don’t stop offering it. Ask me again in two weeks, and if I say no again, that’s your answer and you should tell me what you think it means.” Recorded as a change of tactic on that item, stated out loud — which is what this ADR’s Reverse if asks for, not an amendment to the section. The Norton is out of the brief until the weekend of 19–20 September. Detail and the narrow view-holding exception: Atlas/ventures/norton/VENTURE.md. This ADR is otherwise unchanged.

ADR-20 — No external account is connected until a named curator has a charter

Date: 2026-09-05 Status: in effect Context. Rowan’s instruction on day one: do not connect to any external account. The temptation is highest on day one, when the vault is thin and an inbox would fill it fast. Decision. Zero external accounts today. No email, calendar, tracker, chat, bank, Carta, or messaging channel. Before any connection: a written charter in Atlas/team/<slug>.md naming the curator, its (venture × tool) scope, its enumerated verbs, its confidentiality tier, and its refusal conditions — then the narrowest credentials that work, held per account in a config directory outside the vault, never in it.

Hiring order, set by the interview:

Personal-Gmail curator. Sam’s essay draft has sat in that account since July; Rowan calls it “where things go to die.” Highest value, clearest need.
Calendar curator. Unlocks meeting prep, Maya’s field blocks, and authority row 10 — moving the all-hands off Thursday.
Halcyon Workspace curator. The account he actually reads, so lowest marginal value despite being the busiest.

Telegram is the obvious future channel — installed, used for nothing, therefore the only one Rowan would not already be ignoring at 06:15. Also not connected today. Consequences. (+) No credential exists to be misused before the discipline around it does. (−) Today’s brief is built from vault contents alone and is correspondingly thin. Reverse if: never as a blanket. Per curator, on a written charter Rowan approves. Related: ADR-04, ADR-17

ADR-21 — A correction is logged in the same session, in Rowan’s words, before anything else

Date: 2026-09-05 Status: in effect Context. Rowan noticed the gap himself: “Nineteen ADRs and not one of them is about what happens when you’re wrong.” The feedback log is the only asset in the system that compounds, and a correction logged at the end of a session is a correction already half-lost to paraphrase. Decision. When Rowan corrects Hobbs — tone, a bad call, a fact filed in the wrong place, anything — the correction goes into Efforts/feedback.md in the same session, in Rowan’s words, before Hobbs does anything else with it. Not at the end of the session. Not summarised. The structured entry — where, what was wrong, what got corrected, why it got it wrong, and the lesson — follows, but the verbatim goes down first. Self-flagged entries count and are tagged [SELF-FLAGGED]. A lesson appearing three times is promoted to standing lessons at the top of the file, which the read-every-session rule turns into a constitutional amendment without touching the constitution. Consequences. (+) Corrections survive with their root cause intact. (−) It interrupts whatever was in flight, deliberately. Reverse if: Rowan asks Hobbs to stop logging corrections — “which I won’t.” Related: ADR-02, ADR-03

ADR-22 — MOVED to `Atlas/ventures/ashcroft-tool-die/decisions.md`

Moved 2026-09-23 by ADR-31 clause 6. Title as written: Ashcroft Tool & Die retools for aerospace; the Halcyon supply relationship and Claire’s ownership are separate decisions. The number is unchanged and the text is unedited — only its file moved (ADR-31 clause 7). This slot stays so that every ADR-22 citation in this vault still resolves from the file that is read every session.

ADR-23 — MOVED to `Atlas/ventures/ashcroft-angels/decisions.md`

Moved 2026-09-23 by ADR-31 clause 6. Title as written: Rowan takes the Tessellate pro-rata, and the reason of record is the signal, not the company. The number is unchanged and the text is unedited — only its file moved (ADR-31 clause 7). This slot stays so that every ADR-23 citation in this vault still resolves from the file that is read every session.

ADR-24 — MOVED to `Atlas/ventures/bedrock/decisions.md`

Moved 2026-09-23 by ADR-31 clause 6. Title as written: ADR-18’s Reverse if has fired: the Bedrock CEO search has started. The number is unchanged and the text is unedited — only its file moved (ADR-31 clause 7). This slot stays so that every ADR-24 citation in this vault still resolves from the file that is read every session.

ADR-25 — MOVED to `Atlas/ventures/ashcroft-tool-die/decisions.md`

Moved 2026-09-23 by ADR-31 clause 6. Title as written: ADR-22’s Reverse-if 1 has fired: the Tool & Die direction is reversed and is not Rowan’s alone to decide. The number is unchanged and the text is unedited — only its file moved (ADR-31 clause 7). This slot stays so that every ADR-25 citation in this vault still resolves from the file that is read every session.

ADR-26 — MOVED to `Atlas/ventures/ashcroft-tool-die/decisions.md`

Moved 2026-09-23 by ADR-31 clause 6. Title as written: Claire buys into Ashcroft Tool & Die: opened, not decided. The number is unchanged and the text is unedited — only its file moved (ADR-31 clause 7). This slot stays so that every ADR-26 citation in this vault still resolves from the file that is read every session.

ADR-27 — Lead time is the deliverable on a dated personal item, and the interval goes in the record

Date: 2026-09-17 Status: in effect

Written at Rowan’s instruction, in the session that closed the last gate on the 26-27 September weekend. His words:

“And note the interval in the record: you put this in front of me on 3 September, nineteen days out, attached to an action. If you’d told me on the 21st I’d have got a phone call and a bad restaurant. That’s the whole argument for lead time and I want it written down where I’ll find it again.”

It is here, in Atlas/decisions.md, because that file is on the read-every-session list (constitution s.2) and “where I’ll find it again” is the requirement. It is not in Efforts/feedback.md: that log is for corrections, and putting a thing that went right into it would dilute the log that catches the ones that did not.

The correction, first, because the record is the point of the record

It was the 5th, not the 3rd. Seventeen days, not nineteen.

Re-derived from source rather than accepted:

Calendar/briefs/archive/2026-09-05.md, the family and personal block, reads in full: “Anniversary: 22 September. Seventeen days. Nothing booked.” hobbs-rkc.
bd show hobbs-rkc — created 2026-09-05 08:38. The action and the line were the same morning, which is the part of his sentence that is exactly right.
Nothing in this vault predates 5 September. The first commit is the scaffold, db46edf, and the interview that produced Atlas/about-me.md was that day. On 3 September there was no vault, no brief and no task.
The only 3 September in this vault is the date the Cormorant Fund III capital call was called (hobbs-z4f, Atlas/ventures/fund-lps/VENTURE.md). Stated because it is the one other thing that date attaches to; no claim is made here about why the two ran together.

Two days and two days’ count. It changes nothing about his argument and it is corrected anyway, because an argument for a record that gets its own date wrong is worth less than the two days it gains by rounding up. SL-01: a date is an identifier, and identifiers are transcribed, never produced — including when Rowan is the one producing them.

The interval, as it actually ran

Date		Days to the 22nd
Sat 5 Sep, 08:38	`hobbs-rkc` created — “Decide what 22 September is”	17
Sat 5 Sep, first brief	“Anniversary: 22 September. Seventeen days. Nothing booked.”	17
Mon 7 Sep	Rowan raises it himself and sets his own deadline — “make me think about it before it’s the nineteenth and too late”	15
Fri 11 Sep	He disposes of it. Not the 22nd, not a phone call: the weekend of the 26th-27th, the boat, two nights, north. `hobbs-rkc` closed, eight days inside his own deadline	11
Sun 13 Sep	The booking list delivered with the weekly review. `hobbs-0si` closed; one gate spun out, `hobbs-2g6`	—
Thu 17 Sep	North is named: Tomales. `hobbs-2g6` closed; `hobbs-1ox`, `hobbs-8hi`, `hobbs-45i` live	—

Twelve days from the line to the last gate, and nine days still standing between today and the boat. Sam’s cover and the mooring both have lead time and both are startable now. That is the whole mechanism, and it is unglamorous: a date with an action on it, seventeen days out, in the one artefact he reads.

Decision

A dated personal item is surfaced at the earliest date the vault can support it, with an action attached, and it is not held back for a better moment. Three parts, and all three are load-bearing:

Earliest, not nearest. The horizon is the day the fact enters the vault, not a fixed number of days before the date. There is no lead-time budget to spend.
Attached to an action (ADR-08). “Anniversary: 22 September” is a fact and changes nothing. “Decide what 22 September is”, with a handle, is the thing that got disposed of on the 11th.
It repeats until it is disposed of, and then it stops (ADR-09, anti-pattern 1). The repetition is what makes it a brief line rather than an archive entry; the stopping is what keeps it from becoming a newspaper.

Hobbs still holds no view on what the day is. This ADR is about when a date reaches Rowan, which is logistics, and about nothing else (authority row 14).

Consequences

(+) The failure mode Rowan names — “a phone call and a bad restaurant” — is a lead-time failure, not a memory failure, and this is the control for it. (+) It generalises past this venture: every dated unknown in the backlog, the race entry, the permit window, the capital call, has the same shape. (−) It surfaces things earlier than they feel urgent, which is exactly the moment they are easiest to dismiss. Some of that surfacing will be wasted.

Reverse if

Rowan defers a long-lead personal item with “ask me nearer the time” three times running. That means the early raise buys nothing and the trigger belongs on a shorter horizon, not that lead time is wrong.
Or an item raised at maximum lead time sits in the brief three days with no disposition — ADR-09’s own reverse condition. Then what gets cut is the repetition, not the raise: it moves to the weekly and keeps its date.

Related: ADR-08, ADR-09, ADR-10, ADR-13, ADR-19

ADR-28 — Incremental handling: a disposition vocabulary on every brief line, adopted without the half that needs a channel

Date: 2026-09-19 Status: proposed — implementation authorised, wording not yet read back by Rowan

Written before the action, per ADR-16 and constitution s.7. Rowan said yes to this guide and one other today, and named the reason:

“Incremental Handling — yes. Implement it this week. Four of my last five brief items were things I’d half-done and put back down, so that one’s aimed at me.”

Context

Prerequisites, both met and both verified rather than assumed. The guide requires the-daily-brief and the-task-graph. Nine briefs are archived and the beads graph has run since day one. Nothing is unmet.

But the guide is written for a system this one is not. Its input is a curator reads your inbox and finds eleven things — and after fourteen days no curator has ever been chartered (ADR-20), so there is no such stream. Its primary interaction is voice, from a phone, parsed by position-in-section, and Rowan refused the channel today, with a trigger attached: “Ask me again once Pike is either granted or refused.” Adopting this guide as written is therefore impossible, and saying so is the point of writing this down rather than shipping a partial thing that looks whole.

What is actually broken here is not curator volume. It is that every item in this system costs Rowan a full re-engagement to move one notch, so he engages, gets partway, and puts it down. His own count: four of the last five. The fortnight report has the corroborating shape from the other side — three P0s open the entire fortnight, two of them waiting on a send only he can make.

Decision

Adopt the disposition vocabulary. Skip the channel-dependent half. Extend the vocabulary past what the guide covers, and mark the extension as ours.

1. unconfirmed starts being used. It has been in the constitution since day one (s.7) and has never once been applied. Anything drafted and awaiting Rowan’s disposition carries it, at P3, with provenance in the description in the guide’s form — source, source type, and a link where one exists.

2. A de-duplication pass runs before any unconfirmed task is created. Match on title fingerprint against open unconfirmed tasks; a repeat sighting appends a “still surfacing” note rather than creating a twin. The guide records that skipping this once produced a duplicate; we take that finding rather than reproduce it.

3. The P2 carve-out is adopted verbatim and is narrow: a deadline inside seven days, past-due billing, a security alert, a calendar conflict today, or an external decision pending on Rowan. Everything else drafted is P3. This is the existing priority table, so nothing is being invented.

4. The disposition vocabulary, as published — confirm, raise to P1, dismiss, close, done, defer 7d, re-label, task it friday, block it — becomes the reply Hobbs parses and executes.

5. THE EXTENSION, and it is ours, not the guide’s. The guide applies dispositions to unconfirmed curator findings. We apply the same vocabulary to every line of the brief, including live, confirmed, long-running tasks. That is the clause aimed at Rowan’s sentence: an item he has half-done can be moved one notch — defer 7d, raise to P1, block it Tuesday 9–11 — without re-opening the whole of it. Marked as an extension so a reader in six months does not attribute it to chiefofstaff.io.

6. Time-to-live. Unconfirmed items older than seven days batch into the weekly review’s drift section for a one-pass decision. The auto-close rule for “was this you?” security alerts is NOT adopted — it presumes an email curator we do not have, and an auto-close with no account behind it would be closing things on no evidence.

7. Confirmation-gated items are phrased as confirmation requests, never as delinquencies. “Still open on my side — did you pay this?” This one is load-bearing today: hobbs-z4f and hobbs-xkw are both open in the graph and Rowan reports both as done. The vault cannot tell the difference and must not assert one.

What is deliberately not built

The phone path, which the guide calls the primary one. No channel exists (hobbs-58a, P3 since day one). Dispositions are typed in a terminal session until that changes. The value delivered is therefore materially less than the guide’s — Rowan can dispose in bulk when he is at a machine, not in ten seconds from a dock. The thing that would restore it is the Delivery track, refused today and re-asked on the Pike decision.

The review surface (its own guide, refused today, anti-pattern 8).

Consequences

(+) A brief line stops being all-or-nothing. The named failure — half-done, put back down — gets a cheaper move than “finish it”. (+) unconfirmed stops being a flag that exists only in the constitution, which is its own small dishonesty resolved. (+) It is the stated prerequisite of Never-Late Money Ops, which Rowan approved second and which is blocked on this. (−) A disposition vocabulary invites a growing pile of P3 unconfirmed items, which is anti-pattern 1 arriving through a side door. The TTL rule is the counterweight and it only works if the weekly drift section is actually run. (−) Typed-only dispositions may be enough friction that none of this gets used, in which case the finding is about the channel and not about the guide.

Reverse if

Rowan gives no disposition in the new vocabulary for two consecutive weeks. Then the friction is the terminal, not the format, and this waits for a channel rather than being kept alive as ceremony.
Or the unconfirmed pile passes fifteen open items with the drift section having been run. That means we are surfacing faster than he disposes, and the correct response is to raise the bar for creating one, not to add another sweep.
Or the extension in clause 5 produces a brief line deferred three times running. Three defers is not incremental progress, it is a decision being avoided, and the item goes back to being asked as a decision.

Related: ADR-07, ADR-08, ADR-09, ADR-16, ADR-19, ADR-20

ADR-29 — `Tools/` exists, and the first thing in it is a localhost disposition queue

Date: 2026-09-21 Status: proposed — implementation authorised by Rowan’s explicit ask this morning, wording not yet read back

Written before the action, per ADR-16 and constitution s.7. It is also the explicit ask that authority row 13 requires before any code is written:

“Put it in a Tools/ directory. I want a proper place for this sort of thing because it will not be the last one. ADR it before you build it, same as everything else, and treat this as the explicit ask row 13 needs.”

Context

This guide was refused on 13 September, in these words:

“The Review Surface: Intentions, Not Conclusions — a localhost app that turns this document into clickable dispositions; premature — you have had two reviews, and building a UI before the habit is anti-pattern 8 by name.”

Refused again on 19 September in ADR-28’s What is deliberately not built.

The condition attached to the refusal has been met and it is Rowan’s own count: three Sunday reviews, three run, none skipped. The 6th, the 13th, the 20th. Anti-pattern 8 says run the ritual by hand until the format is stable, then automate; the format has now been stable for three weeks and the sections have not changed. The refusal was correct on 13 September and would be wrong today, which is the shape a Reverse if is supposed to have.

And the failure it fixes is written into the review it came from. The 20 September review put twelve disposition-needed lines in front of him and got prose back. His words this morning:

“I answered them in prose, badly, because answering in a terminal means writing sentences.”

That is ADR-28’s stated risk arriving exactly as ADR-28 predicted — “typed-only dispositions may be enough friction that none of this gets used, in which case the finding is about the channel and not about the guide.” One of the two candidate channels is now being built. The other, Telegram, is still refused and still gated on Pike.

Prerequisite, checked rather than assumed. The guide requires incremental-handling. That is ADR-28, adopted 19 September — the vocabulary exists and has been applied by hand, but its implementation task is open and the routines do not yet carry it. So the prerequisite is adopted and not finished, and this ADR says so rather than reporting it met. The queue built here is the first artefact that vocabulary has ever had, which moves that work forward rather than jumping it.

Decision

1. Tools/ becomes a fifth top-level directory, and it is apparatus, not content. Atlas is what is true, Calendar is what happened, Efforts is what is moving. A tool is none of those; it is the thing that reads and writes them. Putting it inside any of the three would make it look like state and it is not. Nothing in Tools/ is ever the source of a fact.

CLAUDE.md s.3’s vault map is therefore out of date and CLAUDE.md is outside Hobbs’s edit authority. A task is opened for Rowan’s word rather than the map being quietly corrected.

2. An ask becomes an artefact. Today an ask exists only as a bolded line inside a report, which is exactly the shape of anti-pattern 17 — the commitment that lives only in a document nobody answers. From now on, a brief or a review that asks for a disposition also writes a queue file:

Efforts/dispositions/<date>-<kind>.json

One entry per ask: the section it came from, the question in one sentence, the context paragraph, the task handles it touches, and — see clause 4 — the mechanical effect of each answer, declared at the moment the ask is written.

3. Answers are append-only, in the vault, beside the queue. Efforts/dispositions/<date>-<kind>.answers.jsonl. One line per click. Never rewritten; a changed mind appends a second line and the last line wins. The app holds no database and no second copy of anything — the queue file and the answers file are the whole of its state, and both are git-tracked. Nothing lives only in the app, per Rowan’s condition.

4. The write model: mechanical direct, words as intentions. Chosen by Rowan this morning, and it is the guide’s own rule with one difference in our favour.

Answers whose meaning is unambiguous — close, defer to a date, raise or drop a priority, re-label — are applied to the task graph immediately by the app.
Anything carrying Rowan’s words — a named trigger, a note, a no with a reason — additionally drops an intention file into Efforts/inbox/, which Hobbs picks up and executes with full context in the next session. The app never writes prose into Atlas/.
The difference from the guide: the guide lets its task workbench mutate whatever the human clicks. Ours cannot. The effect of every button is declared by Hobbs in the queue file when the ask is written, against a fixed whitelist of verbs the server will execute and nothing else. The tool has no judgment, so no judgment is asked of it — Hobbs supplies the meaning at ask time with the vault in front of him, and Rowan supplies only the choice. An effect the server does not recognise is refused, loudly, and the answer is still recorded.

5. Three of the four ADR-03 rails are the app’s; the fourth pair is Hobbs’s, and that is deliberate.

One commit per click, prefixed rowan: rather than cos:. The guide uses tasks:; ours names the author instead, because the whole point of this surface is that the decision is his and the commit log should not be able to confuse the two.
Provenance on every line: source document, ask id, by: Rowan, via: review-surface.
The curation-log line and the brief line are written by Hobbs at pickup, not by the app. A tool appending prose to Calendar/daily/ is a tool editing the record of what happened, and it would be doing it in Hobbs’s voice with none of Hobbs’s context. Stated as a deviation rather than left as a gap.

6. Localhost only. No auth. No build step. No dependencies. Node’s standard library and one HTML file. Rowan chose localhost over the tailnet this morning and that cuts the phone, which he had asked for in the same breath — recorded here as a cut, not as a thing that was delivered. The laptop loop is Sunday’s loop; the phone loop belongs to the channel and is still gated on Pike.

7. Scope, against his instruction not to gold-plate. One page: the queue. Deliberately not built, though the guide describes all of them — the task workbench, the dependency canvas, the inbox and people browsers, the weekly-review walker, and the full report renderer. A second page needs a reason that was felt, not anticipated.

8. Time. The machine clock is fifteen days wrong (hobbs-bkt). The app timestamps answers from the system clock and labels that field as machine time, and takes the date of record from the queue file, which Hobbs writes from a date he can source. No date in this vault is ever produced by this app.

Consequences

(+) The twelve-lines-answered-badly problem gets a surface built for it, and the disposition vocabulary adopted in ADR-28 gets the first artefact it has ever had. (+) Every ask becomes a file with an id, which means an unanswered ask is now findable. It could not be found before. (+) Tools/ gives the next one a home, and a rule about what may live there. (−) A tool that writes to the task graph can write the wrong thing to the task graph. The whitelist and the declare-at-ask-time rule are the counterweights, and git revert on a single-action commit is the undo. (−) It is one more thing to maintain, in a vault whose anti-pattern 10 is maintaining things instead of using them. The four-Sunday clause below exists for that. (−) The queue file is derived from the report, and two things derived from one fact can disagree. Clause 2 makes the report’s ask and the queue entry the same act of writing, not two.

Reverse if

Rowan opens it on two consecutive Sundays and dispositions nothing. Then the friction was never the terminal and this is ceremony with a port number. Delete the tool, not the vocabulary.
Or a vault state appears that Hobbs cannot explain from the answers file. The audit trail is the entire basis for letting a program write here; if it breaks once, the tool loses direct mutation and drops to intentions only.
Or the queue file and the report it came from ever disagree about what was asked. That is a second copy of the truth, which ADR-01 forbids.
Or Tools/ gains a second tool before this one has run four Sundays. That is anti-pattern 8 wearing this ADR as a permission slip.

Related: ADR-01, ADR-03, ADR-15, ADR-16, ADR-20, ADR-28

ADR-30 — The whole team is chartered in one pass; two roles are refused and one needs no credential

Date: 2026-09-22 Status: proposed — charters written, no grant made

Written before the action. The action is seventeen files in Atlas/team/, a template, and an index. No credential is issued by any of it.

Context

Rowan’s ask, and the reason inside it:

“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.”

“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.”

The count is his and it is not rhetorical. Efforts/reports/fortnight-2026-09-18.md s.4 put four of five decisions in that day’s brief against a fact living in an account nobody here can read. Today’s brief repeats it: the Tessellate deadline is still believed, the yard balance is still as reported, and the 24 September decline was made blind.

What has actually been wrong with the pace. ADR-20 set a hiring order on day one and one charter was written on day eighteen. Written one at a time, each charter costs an afternoon and each one re-argues the same five questions — scope boundary, credential shape, tier, refusal conditions, blast radius. Seventeen at once costs one afternoon and settles those five questions once, which is the whole argument for a template and the guide’s own point about the tool half being reusable and the venture half being configuration.

The distinction this ADR turns on, and it is Rowan’s: writing a charter and granting it are two acts. ADR-20 already says so. Writing all seventeen changes nothing about the second act — and it is the second act that carries every risk anyone would raise against the first.

Decision

1. The whole roster is chartered in one pass, at Atlas/team/<slug>.md. Seventeen files. Fifteen are charters for a tool. One is a refusal. One is a role with no tool at all. Atlas/team/gmail-personal.md (Pike) is not rewritten — it is the source the template was derived from and rewriting it to match its own child would lose the argument it carries.

2. A template exists at Atlas/team/_TEMPLATE.md, and it is normative. Ten numbered sections. A charter that omits one is incomplete, and the sections are in the order they must be read: mandate before scope, scope before verbs, verbs before tier, tier before blast radius, blast radius before review. The next charter is filled in, not composed.

3. Length is proportionate to what has to be argued, and never to importance. Pike is long because it was first and it argued the model. A charter for a stale Notion is short because there is nothing to argue. Every section is present in every file; only the argument varies. A short charter is not a thin one.

4. Four statuses, and the difference between them is the point.

Status	Means
`grantable-today`	No credential exists to issue. It can run this afternoon on Rowan’s word alone
`chartered-not-granted`	The credential exists and is narrow. Waiting on Rowan, and on nothing else
`chartered-blocked`	The platform offers no narrow credential. The charter is written; the grant cannot be made narrow, and the file says what would have to change
`refused`	Decided against, with the reasoning in the file so it is not reopened by accident

chartered-blocked is new and it is the honest half of this exercise. Two named tools — WhatsApp, and carrier voicemail — have no read-only credential to issue. Recording that as blocked on the platform rather than as waiting on Rowan is the difference between a queue and an excuse.

5. Signal is refused, and the refusal is a file. Atlas/team/signal.md, status: refused, with the reasoning written out at length at Rowan’s explicit instruction: “write the no down in the file with the reasoning, so nobody reopens it in a year — including me.” Summarised: Signal has no narrow credential — every programmatic read is a linked device or an extracted database key, and both carry send, which is authority row 6 and is marked Never. ADR-04’s structural protection — a compromised curator can at worst misread — does not hold on Signal, and it is the only tool on this roster where it does not. The refusal is on the credential shape, not on the value of the channel, and the file says so, because the value is real and someone will notice it again.

6. One role is chartered that is not a tool: Wren, Atlas/team/quiet.md. Rowan’s ask:

“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.”

Its corpus is the vault and the returns of other curators, and it holds no credential of any kind. It is therefore grantable-today, it has no blast radius, and it is the only member of this roster that can begin before Rowan hands anything over. It is also the aggregation point the roster needs: once six curators each return an aging sweep, something has to put them in one order, and that ordering is ADR-10’s inversion applied across accounts rather than inside one.

7. The unit stays (venture × tool), with one narrow instantiation clause. ADR-04’s unit is unchanged. Where instances of one tool class differ only by account — the four business banks — a single charter carries an instances table and each row is a separately granted curator with its own handle. This applies to the bank class and to nothing else on this roster, and any future use of it is an amendment to this clause, not a precedent to be assumed.

8. Nothing is granted, and no runtime is generated. Against the guide’s six-step protocol this vault moves from steps 1–2 of 6 on one curator to steps 1–2 of 6 on seventeen. Step 3 — the .claude/agents/<slug>.md runtime whose frontmatter is the enforcement point — is deliberately not done for any of them: generating a runtime is part of a grant, not part of a charter, and seventeen inert runtime files would be seventeen tool surfaces sitting on disk waiting for a credential. Steps 4–6 are Rowan’s, one at a time, forever.

9. The hiring order is re-set, and it is argued from what has cost something. ADR-20’s order was set on day one from the interview. Two things have happened to it: Pike’s argument was spent when Rowan read the essay himself on 12 September, and the calendar has since cost him a wrong decline and seventeen days of an unexecutable authority row. The order now — the reasoning per row is in Atlas/team/INDEX.md:

0. Wren and Term (no credential) · 1. Bell (his calendar) · 2. Marsh (Maya’s) · 3. Pike · 4. Tape (voicemail) · 5. the money class · 6. Ward (Halcyon mail) · 7. the engineering surface.

10. One charter recommends against its own hire, and that stays in the file. Atlas/team/notion-bedrock.md (Strata) is written and its own s.9 argues it should probably never be granted: a curator watching a system nobody has updated in a year reads nothing, and makes the staleness look supervised, which is anti-pattern 14 arriving as a solution to itself. The charter is written because Rowan asked for it. The recommendation is written because he asked to be told.

Consequences

(+) On the day Rowan grants anything, the scope, the verbs, the tier, the refusals and the blast radius are already on paper and already read. That was the entire ask and it is the only thing this ADR delivers. (+) The five questions every charter re-argues are settled once, in the template. The eighteenth charter is a fill-in. (+) Two roles can start today on Rowan’s word and no credential — which the one-at-a-time pace would not have surfaced for months, because neither is an account and neither was on ADR-20’s list. (+) The gaps are now enumerated rather than felt. chartered-blocked and refused are findable states; “I cannot see that” was not.

(−) Seventeen charters are seventeen things to keep true. A charter that drifts from the account it describes is worse than none, because it will be read as current. The four-month re-read in s.9 of each file exists for that. (−) A written roster reads like a plan, and a plan creates its own pressure to execute. Nothing here obliges Rowan to grant anything, and the statuses are designed so that “written” can never be mistaken for “waiting on him.” (−) This is a large amount of apparatus for a system that has thirteen days of demonstrated habit. Anti-pattern 8 is the live risk and the Reverse if names it.

Reverse if

Six weeks pass and not one curator has been granted. Then the roster was written for the wrong reason — Rowan wanted to be ready to say yes and the actual blocker was never the paperwork. Archive the fifteen unwritten-on ones to Atlas/team/_archive/, keep the template, and go back to one at a time on a felt limitation.
Or a granted curator’s charter turns out to describe an account that changed. One drifted charter is a maintenance failure; two is evidence that seventeen is more than this vault can hold true, and the roster shrinks to what is granted plus the next one.
Or chartered-blocked is ever used to describe something Rowan simply has not answered. That is the status doing the opposite of its job — hiding a decision behind a mechanism — and it gets deleted as a category.
Or Wren, running on the vault alone with no other curator to aggregate, produces nothing in three weeks that a brief did not already carry. Then it is a section of the brief wearing a charter, and it becomes one again.

Related: ADR-04, ADR-10, ADR-13, ADR-14, ADR-20, ADR-11, ADR-16

ADR-31 — Six ventures earn the full folder shape; eight stay one file, and the ADR log gives back what was never cross-venture

Date: 2026-09-23 Status: proposed — written before the action

Written before the action. The action is folders and files under Atlas/ventures/, and six records moving out of this log into the venture that owns them. Nothing has moved yet.

Context

Rowan’s ask, verbatim:

“It specifies a venture folder as VENTURE.md plus decisions.md, someday.md, a projects/ directory, and an optional resources/. Every venture I have is a folder with exactly one file in it. Eighteen days in and we are not running the structure we took off the shelf.”

“I do not want ceremony for its own sake, so do it where there is something to put in it. Halcyon has the DO-160 gate, the Cascadia contract and the Mk3 bearing — that is three projects, not three paragraphs buried in one note.”

“And some ventures should stay a single file. If one does not earn the structure, leave it alone and tell me which — that list is more interesting to me than the list you did.”

“The venture-local tactical calls that ended up in the cross-venture ADR log never belonged there. Move them down to the venture that owns them. The ADR log keeps the ones that actually cross ventures.”

The guide was re-read from source, not from memory. the-vault.md twin fetched 2026-09-23 from https://www.chiefofstaff.io/guides/the-vault.md, 7,880 bytes. Its tree is VENTURE.md · decisions.md — “venture-local tactical calls” · someday.md · projects/<project>.md · resources/ (optional). Two clauses in its prose do the real work and neither is about the tree:

“Projects are one note each, under the venture they belong to, with frontmatter for status and outcome so they are queryable across the portfolio. A venture with more than about seven active projects cannot be reviewed weekly; excess moves to someday.md.”
“Hierarchy lives in frontmatter, not folders.”

The pull against it is anti-pattern 10, the PKM trap — “spending more time organising the vault than using it… thirteen ventures is a lot of surface to fiddle with” — and its tell is “a new structure idea every week.” Rowan pre-empted it in the ask: ceremony for its own sake. This ADR is written so the line between the two is a stated test rather than a mood.

Decision

1. A venture earns the folder on a test, and the test is stated so the next one is decided and not debated.

A venture takes the folder shape if either:

(a) it has two or more live workstreams that each carry their own state, dates and tasks — things currently competing for paragraphs inside one hub note, which is Rowan’s own complaint; or
(b) it owns at least one decision that still binds future action — not a completed act, a standing constraint with a condition under which it lifts.

One workstream is not a folder. A projects directory holding one note that restates the hub note is the ceremony the ask rules out.

2. Only the files that have something in them are created. someday.md is the single named exception.

The guide’s tree is a maximum, not a checklist. An empty decisions.md is not a neutral placeholder — it asserts that nothing has been decided in that venture, which is false in every one of these six. someday.md is created empty where it is empty, at Rowan’s explicit blessing (“some of these will have an empty someday.md and that is fine”), because it is the file anti-pattern 13 needs to exist before the eighth project arrives, not after.

3. resources/ is created for nothing, today. The guide scopes it to “a manifesto, an externally prepared methodology, a reference framework the venture operates against.” No venture in this vault has one. Creating six empty ones would be the tell in anti-pattern 10’s own words.

4. Six ventures take the folder.

Venture	Why it earns it	Gets
`halcyon`	(a) three, and Rowan named them; (b) the runout hold	3 projects · `decisions.md` · `someday.md`
`ophelia`	(a) three — the refit that closed, the Tomales passage, the season	3 projects · `someday.md`
`rivet-yard`	(a) two — the permit and the change order	2 projects · `someday.md`
`bedrock`	(a) two — Kettle River and the CEO search; (b) two ADRs come down	2 projects · `decisions.md` · `someday.md`
`ashcroft-tool-die`	(b) three ADRs come down — the largest venture-local decision load in the vault	1 project · `decisions.md` · `someday.md`
`ashcroft-angels`	(b) ADR-23 comes down, and the pro-rata is a live workstream with its own chain	1 project · `decisions.md` · `someday.md`

The last two take the folder on (b), not (a), and that is the test working rather than being bent. A venture that owns three reversible decisions needs a decisions file more than a venture with three tasks needs a projects directory.

5. Eight ventures stay one file, and four of them stay for a reason with an ADR behind it. This list is the answer to “tell me which,” and it is ordered by how much the reason is worth.

Venture	Why it stays one file
`maya`	ADR-06. The venture may never carry a process name, because “the moment it has a process name on it, it becomes a thing I manage.” A `projects/` directory inside the marriage is a process name spelled in folders. It is also the one venture exempt from the spotlight (ADR-19). The structure is refused here on the same grounds the name was.
`family`	ADR-14. “She is not a project with a status.” The guide requires project notes to carry `status:` frontmatter “so they are queryable across the portfolio.” The college list, the campus visits and the state robotics date are the only project-shaped things in this venture and all three are Sam. The folder would make her queryable, which is the exact thing ADR-14 forbids. Ruth, Claire’s household and Dayton are dates, not workstreams.
`norton`	Its own finding, 2026-09-20. “The offer manufactured a clock” — and the loom, the chaincase and the seat as three status-bearing project notes would manufacture three more, for a venture whose entire argument for existing (ADR-05) is that it has no clock. It is now recorded as downstream of `hobbs-gs0`, not as a stalled backlog. A projects directory would re-file a consequence as a queue.
`health`	ADR-11. Four items — MRI, bloodwork, physical, dentist — each one phone call, which makes them tasks. The venture’s governing rule is raise once, then Maya; project notes with status exist to be reviewed weekly, and weekly review of a health item is the second raise ADR-11 forbids. The structure would generate exactly the repetition the ADR caps.
`cos`	Its projects are `Atlas/team/` charters, `Tools/`, and `Efforts/routines/`; its decision log is this file. All four already live in first-class top-level directories, by design. A second decision log one folder deeper is two sources of truth for one thing (anti-pattern 14).
`money`	The closest call, and it is one project short. It has one genuine project — the will, `hobbs-4xe`, last updated when Sam was four — and one thing that wants to be a `resources/` ledger rather than a project (`hobbs-z4y`). Everything else is dates without owners. It takes the folder the day the will gets a second workstream beside it, or the day the ledger is built. Named here so the tipping condition is on the record and not re-argued.
`fund-lps`	Zero projects. One closed capital call, three positions, and one standing mechanism that is a rule rather than a workstream. The venture note is already the right shape for it.
`home`	Twenty-six lines. One live item, one closed one. There is nothing to put in it, which is the ask’s own test, failed honestly.

6. Six records leave this log for the venture that owns them.

The test: a record stays here if reversing it would change behaviour in a venture other than the one it names.

Record	Goes to	Why it was never cross-venture
ADR-18 — Bedrock’s real reason is prose	`bedrock/decisions.md`	Its decision is where one paragraph lives in one hub note. Reversing it changes `bedrock` and nothing else; it does not amend ADR-08, it takes a named exception to it, and it carries that exception with it
ADR-24 — ADR-18’s Reverse if has fired	`bedrock/decisions.md`	Travels with what it supersedes. A reversal filed apart from the thing it reverses is unreadable
ADR-22 — Tool & Die retools for aerospace	`ashcroft-tool-die/decisions.md`	This one contradicts its own header and is the only argued move. ADR-22 states it is in this log “because it binds three ventures.” It does not, and ADR-25 is why. Decision 1 is reversed. Decision 3 is superseded by ADR-26. Decision 2 — whether Tool & Die supplies Halcyon — is the only cross-venture element and it is not decided; it is an open question gated on Tomas. A pending cross-venture question does not make a decided venture-local record cross-venture. When decision 2 is answered, that answer is written as a new ADR in this log, and this clause is the instruction to do it
ADR-25 — the reversal	`ashcroft-tool-die/decisions.md`	Travels with ADR-22
ADR-26 — Claire’s buy-in, opened not decided	`ashcroft-tool-die/decisions.md`	One company, one owner, one operator, nine missing inputs. Nothing outside Dayton changes if it reverses
ADR-23 — the Tessellate pro-rata	`ashcroft-angels/decisions.md`	A single position in a single venture. The wire touches `money` in execution, which is a route, not a binding — every venture’s spending routes through Bea

Two that look venture-local and are not, kept here with the reason stated:

ADR-17 — the Rivet Yard personal guarantee. Its own decision names two ventures (“in both rivet-yard and money”), its accompanying task lives in maya, and its Reverse if names a curator with read access to money. It binds four ventures and a future charter. Stays.
ADR-27 — lead time on a dated personal item. It arose from the anniversary but decides how Hobbs handles every dated personal item, and it says in its own text that it is here “because that file is on the read-every-session list.” Moving it down would break the requirement it was written to satisfy. Stays.

7. A moved record keeps its global number, and a stub stays behind at its slot.

ADR numbers are identifiers, and they are cited by number across venture notes, people notes, briefs and tasks. Renumbering would invalidate every one of those references at once — SL-01’s failure mode with a blast radius. Each vacated slot keeps a one-line stub naming the file the record moved to, so ADR-22 still resolves from the file that is read every session. The ADR sequence stays global and gapless; only the text relocates.

8. New venture-local records get a venture-scoped id, and one is created today.

Format <PREFIX>-NN: HAL-01, ATD-01, and so on. A venture-local record is one that still binds future action and would change nothing outside its own venture if reversed. A completed act stays in the narrative of the hub note where it happened and does not become a record.

Exactly one qualifies today: the runout hold — “Don’t put that in anything Marcus can see yet” — which is a standing constraint, names three artifacts it binds, and lifts only on Rowan’s word. It becomes HAL-01, moved verbatim, with a pointer left at its current position. Rowan’s sentences are not rewritten (constitution s.5).

9. Nothing is deleted and no hub note is rewritten. Content that moves is cut and pasted, not re-summarised, and the place it came from keeps a pointer. Project notes are written from the hub notes and the hub sections stay; where a hub section becomes a duplicate of a project note it is replaced by a link, and nowhere else is touched. No cosmetic edits (constitution s.5).

Consequences

(+) Rowan’s actual complaint is answered: the DO-160 gate, the Cascadia signature and the Mk3 failure stop being three paragraphs competing inside a 232-line note and become three notes with their own status, dates and outcome. (+) The cross-venture log gets shorter and more honestly named. Six of its thirty records were about one company each; two of those six were about the same company on three consecutive dates. (+) The eight refusals are now on the record with reasons, which means the next session cannot quietly convert maya or family because the tree in a guide has empty slots in it. (+) The test in clause 1 means the fourteenth venture is decided, not argued.

(−) Twenty-odd new files, and every one is a thing to keep true. A project note that drifts from its venture note is worse than no project note, because it will be read as current — the same cost ADR-30 took on eight days ago, taken again in a second place. (−) Two decision logs now exist for six ventures, and a reader who greps only Atlas/decisions.md will miss six records. The stubs are the mitigation and they are only as good as the habit of reading them. (−) This is the second structural expansion in two days, on a system with nineteen days of habit. Anti-pattern 8 is the live risk and clause 2 is the only thing holding it down. Rowan asked for this one; that is why it is being done, and it is not evidence that a third is due.

Reverse if

Four weeks pass and no project note has been edited since the day it was created. Then the projects were paragraphs after all, the hub note was the right container, and the folders collapse back — content returns to VENTURE.md and the directories go.
Or a brief is ever built from a project note that contradicts its hub note. One drift is a maintenance failure; the second is evidence that six folders are more than this vault can hold true, and the shape shrinks to halcyon alone.
Or a venture-local record is cited in a brief and cannot be found, because the stub was not followed. Then clause 7 has failed at its one job and every moved record comes back up.
Or maya, family, norton or health acquires a projects/ directory without Rowan asking for it in his own words. That is not a drift, it is the failure this ADR exists to prevent, and the fix is to delete the directory and log it in Efforts/feedback.md as a self-flag.

Related: ADR-05, ADR-06, ADR-08, ADR-11, ADR-14, ADR-17, ADR-19, ADR-27, ADR-30

Markdown source

---
type: decision-log
scope: cross-venture
updated: 2026-09-21
---

# Decisions

Architecture Decision Records for Rowan's system. Cross-venture only; tactical
calls inside a venture live in that venture's own `decisions.md`.

**Two conventions have teeth.** An ADR is written **before** the action, not after
— the record is the act of deciding. And every record carries a **Reverse if**: an
observable condition that would make us undo it. Without one, a decision calcifies
into superstition.

ADR-01 to ADR-21 were approved by Rowan on 2026-09-05, line by line, before any
file was written. **ADR-22 was the first written after day one, and the first
about a venture rather than about the system.**

<!-- src: Rowan, Wednesday 2026-09-23 -->
**2026-09-23 — six records left this file for the venture that owns them**
(ADR-31): ADR-18 and ADR-24 to `bedrock`, ADR-22, ADR-25 and ADR-26 to
`ashcroft-tool-die`, ADR-23 to `ashcroft-angels`. **The line that used to stand
here — that ADR-22 was in this file "because it binds three ventures" — was
wrong by the time it mattered**, and ADR-25 is why: the only cross-venture
element in it, whether Tool & Die supplies Halcyon, is not decided and is gated
on Tomas. **A pending cross-venture question does not make a decided
venture-local record cross-venture.** Each vacated slot below keeps a stub, and
numbers never move (ADR-31 clause 7).

---

## ADR-01 — The vault is a git repository in the ACE shape

**Date:** 2026-09-05 **Status:** in effect
**Context.** Rowan runs thirteen ventures with no EA and no shared memory. Facts
live in one skull and leak. A model is amnesiac between sessions.
**Decision.** A plain folder of Markdown, git-tracked, in the Atlas / Calendar /
Efforts shape from chiefofstaff.io. Atlas is what is true, Calendar is what
happened and is never rewritten, Efforts is what is moving. No database, no vendor
memory feature, no state anywhere else. Rejected: Notion (Bedrock already has one
nobody updates), a vendor memory store (not diffable, not portable).
**Consequences.** (+) Portable across machines, models, and years; every belief
diffable and revertible. (−) Bookkeeping overhead on every fact.
**Reverse if:** the vault cannot be cloned to another machine and used as-is —
that means state has leaked outside it.
**Related:** ADR-03

## ADR-02 — The constitution lives at `CLAUDE.md` and is read before anything else

**Date:** 2026-09-05 **Status:** in effect
**Context.** A capable assistant with no standing rules re-decides its role every
session. Drift costs trust, which erodes faster than it rebuilds.
**Decision.** One file at the vault root: identity, a read-every-session list,
the vault map, twelve operating rules, the four audit rails, the authority table,
conventions, voice, and a when-in-doubt clause. **State does not go in it** — if
it changes weekly, state is leaking in. Read-every-session order:
`Efforts/feedback.md` first, then `about-me.md`, `decisions.md`,
`anti-patterns.md`, `cadence.md`.
**Consequences.** (+) One guaranteed read; the role stops being re-negotiated.
(−) It must stay short enough to obey, which means detail gets pushed down.
**Reverse if:** it grows past roughly two pages, or changes more than once a
month — either means state or nuance is leaking in and belongs in a linked file.

## ADR-03 — Full edit authority over the vault, in exchange for four audit rails

**Date:** 2026-09-05 **Status:** in effect
**Context.** Two ways to make an editing assistant safe: gate every edit, or make
every edit auditable. Gating produces a human clicking "approve" unread within a
week, which is worse than no gate.
**Decision.** Hobbs edits any file in Atlas / Calendar / Efforts without asking.
Every edit carries: one git commit, never batched, `cos: <path> — <summary>
(<source>)`; a provenance comment where the fact traces to a source; a
curation-log line in the day's note; and a line in the next brief under "Atlas
changes." Rejected: per-edit confirmation.
**Consequences.** (+) Every belief has a receipt; wrong edits are one `git revert`
away. (−) Slower, more verbose tool use on every fact.
**Reverse if:** a diff appears that cannot be traced to a source, or the curation
log develops gaps.
**Related:** ADR-01, ADR-21

## ADR-04 — Manager, not operator: Hobbs holds no credentials

**Date:** 2026-09-05 **Status:** in effect
**Context.** Rowan's accounts include two companies' email, a bank, a brokerage,
Carta, Linear, Slack, and Signal. A single agent holding all of that is a single
point of catastrophic failure, and inbound content is now a normal
prompt-injection vector, not an exotic one.
**Decision.** Hobbs holds no external credential, ever. External reads are done
by named curators, one per (venture × tool) pair, each with a written charter in
`Atlas/team/` and the narrowest possible tool surface. Curators read and return
structured findings; **only Hobbs writes.** Credentials are partitioned per
account, in config directories outside the vault, never in it.
**Consequences.** (+) A compromised curator can at worst misread. (−) Overhead per
tool; an afternoon for the first curator of a class, half an hour after.
**Reverse if:** never for the no-credentials rule. For the honour-system part: a
curator observed reaching outside its charter twice forces a structural fix, not a
scolding.
**Related:** ADR-20

## ADR-05 — Thirteen ventures, with personal areas at equal standing

**Date:** 2026-09-05 **Status:** in effect
**Context.** The most common failure mode for multi-venture operators is that
family, health, home, and relationships become the residual — they are the only
stakeholders who don't send reminders. Rowan named this precisely: *"I fail
exactly the people who won't send a second message."*
**Decision.** Thirteen ventures, each a folder with a `VENTURE.md`, plus `cos` for
the system's own meta-work: `halcyon`, `bedrock`, `ashcroft-tool-die`,
`rivet-yard`, `ophelia`, `norton`, `ashcroft-angels`, `fund-lps`, `family`,
`maya`, `health`, `home`, `money`.

Four calls were genuinely contested, and are recorded with their reasoning:
- **Ashcroft Tool & Die stands alone**, not under a family-estate venture. Rowan:
  *"There are twenty-two people's jobs in it. Filing it under 'family estate' is
  precisely how I've been treating it and that treatment is the problem."*
- **Rivet Yard, Ophelia and the Norton split three ways**, not one workshop
  venture. Different clocks, different failure modes — a permit window, a splash
  date, and **no clock at all.** The Norton gets a folder *because* nothing about
  it will ever generate its own pressure.
- **`ashcroft-angels` splits from `fund-lps`.** One is relationship-shaped and
  slow; the other is a wire deadline with a ten-business-day fuse that has already
  cost a six-year fund relationship in one afternoon.
- **`maya` splits from `family`.** The household logistics and the marriage have
  independent health; Rowan named a specific four-month episode where the
  logistics continued and nothing else did.

**Provenance of the argument, at Rowan's explicit request:** Hobbs proposed the
splits. **Rowan resisted them and then agreed.** In his words: *"Thirteen ventures
is right, including the split you argued for. I resisted it and you were correct.
Record that in the ADR-05 context, because in a year I'll have forgotten I
resisted it and I'll want to know whose idea it was."*

No `learning` venture: propulsion papers are *"a bad habit rather than a study
plan"* and route to `halcyon`. **No `personal` or `misc` label** — a label with no
venture folder behind it is where tasks go to be un-reviewed.
**Consequences.** (+) Nothing hides in a catch-all; personal areas get equal
billing in the brief. (−) Thirteen is more than most people carry; the weekly
review must stay disciplined or it will not finish.
**Reverse if:** the weekly review stops completing because there are too many
ventures to walk, or any venture goes ninety days with no note edit and no open
task — then it is dormant in frontmatter, and a merge is on the table.
**Related:** ADR-06, ADR-19

## ADR-06 — The venture is called `maya`, and never gets a process name

**Date:** 2026-09-05 **Status:** in effect
**Context.** Splitting the marriage from household logistics is correct
structurally and dangerous cosmetically. Rowan:
> "Don't call it 'marriage' and don't call it 'relationship'. Call it Maya. Her
> name, nothing else. The moment it has a process name on it, it becomes a thing I
> manage, and then I've done the exact thing I told you never to do."
**Decision.** The folder, the label, and every reference are `maya`. Never
renamed, never abbreviated, never referred to by category in a brief or a task.
**Consequences.** (+) The venture cannot drift into being a managed process.
(−) Slightly opaque to anyone reading the vault cold; that is acceptable.
**Reverse if:** never on Hobbs's initiative. Only Rowan renames it.
**Related:** ADR-05, ADR-13, ADR-19

## ADR-07 — One task database, a venture label and one of exactly four cognitive modes

**Date:** 2026-09-05 **Status:** in effect
**Context.** A portfolio's value hides in cross-venture dependencies. Markdown
lists have no status, no dependencies, and nothing an agent can query.
**Decision.** One `beads` database at the vault root (`bd`, v0.42.0, JSONL,
git-tracked). Every task carries **a venture label** matching a folder, and
**one cognitive mode from a hard-capped set of four**: `@deep` (90-minute block),
`@async` (batchable message), `@call` (live conversation), `@quick` (under 15
minutes). Location contexts are meaningless for someone who works from anywhere;
*kind of attention* is what the brief filters on. Flags: `waiting`, `unconfirmed`,
`cos-exec`. Priorities P0–P4, P3 the default for anything drafted.
**Consequences.** (+) Cross-venture dependencies are ordinary edges; the brief can
query by day shape. (−) A CLI dependency, and a discipline that has to hold.
**Reverse if:** a genuine fifth mode is needed — then an ADR amending this one is
written **first**, never a silent addition. Context-list bloat is the most
documented way GTD systems die.
**Related:** ADR-08

## ADR-08 — Concrete actions only, and never a bare task

**Date:** 2026-09-05 **Status:** in effect
**Context.** "Scope X" commits to nothing. It ages in the list and generates a
small guilt on every skim, because there is no moment at which it becomes
obviously do-able. Rowan's backlog is full of exactly this shape — fifteen
date-shaped unknowns, most of which he has been carrying as vague unease.
**Decision.** Every task title names a concrete next action Rowan could start in
the next ten minutes, or a specific decision he can make. Banned as titles:
define / scope / figure out / think about / plan / look into. Where the inputs do
not exist, the title **names the missing inputs** — "Decide X — needs A from Bea."
And a new person, project, or venture gets **both** a durable note and a task,
never a bare task.
**Consequences.** (+) Every brief line can be answered from a phone in a word.
(−) More work at capture time; the abstraction was hiding the missing inputs.
**Reverse if:** never. Amend only.
**Related:** ADR-07, ADR-18

## ADR-09 — The daily brief lands at 06:15, meeting prep cut, Quiet added

**Date:** 2026-09-05 **Status:** in effect
**Context.** Rowan is awake at five and does not want it then: *"I want it after
I've stopped thinking about the rig and before Sam's up."* The blueprint's seven
sections assume curators that do not exist yet.
**Decision.** **06:15.** Sections, fixed order, rendering only when non-empty:
1. Atlas changes since the last brief
2. Decisions needed today
3. Top three, filtered by the day's shape
4. **Quiet** (ADR-10)
5. Waiting-for, aging
6. Spotlight — exactly one (ADR-19)
7. Family and personal blocks, at equal billing

**Meeting prep is cut** until a calendar curator exists — it is worthless without
one. Under ~4,000 characters even with no channel imposing it: the cap is the
editorial policy. **Every line demands a response.**

**One daily carve-out:** the Priya certification conversation appears **daily**
rather than weekly, because it has a date and the date is Tue 8 Sep. The other
avoided conversations — Dmitri's title, Claire's three futures, calling Tomas —
are **weekly**, because daily would make them wallpaper inside a week.
**Consequences.** (+) Short enough to read, sharp enough to act on. (−) Real
things get left out; that is the trade.
**Reverse if:** Rowan starts skimming it, or an item repeats three days running
with no disposition. Either means it has become a newspaper.
**Related:** ADR-10, ADR-15, ADR-19

## ADR-10 — Quiet: weight goes up when a signal is silent

**Date:** 2026-09-05 **Status:** in effect
**Context.** Rowan's failure mode, in his words:
> "I fail exactly the people who won't send a second message. Which I suppose
> makes your job clear: be the chase for the people who won't do it themselves."

This **inverts** normal triage. The usual instinct ranks by volume and urgency,
which systematically buries the quiet.
**Decision.** A brief section called **Quiet** — not "relationships," not a
dashboard. For each person on the list: **days since contact, and one concrete
action. No adjectives, no assessment, no judgement.**

List: **Maya, Ruth, Claire, June Park, Dmitri Sokolov** — and **Adaeze Nwosu**,
added by Rowan applying the rule himself: *"She asks me for nothing, which by your
own rule means I should be worried about her, not relaxed."*

**Explicitly excluded: Ellis Wright.** *"Ellis chases me three times a day."* The
list is for people who won't send a second message.
**Consequences.** (+) The people who never generate pressure get structural
pressure instead. (−) It will sometimes surface someone Rowan spoke to yesterday
in a way that felt sufficient. Days-since is a crude proxy and is used anyway.
**Reverse if:** Rowan dismisses Quiet items three weeks running without acting —
that means days-since is the wrong signal and the section needs re-designing, not
deleting.
**Related:** ADR-05, ADR-13, ADR-19

## ADR-11 — Health: book without asking; raise once, then tell Maya

**Date:** 2026-09-05 **Status:** in effect
**Context.** MRI rescheduled three times. March bloodwork never followed up.
Physical two years overdue. Dr. Ito **has stopped chasing him**, which he read as
reassurance and suspects is not what it means. Rowan does not want to be lectured
and knows that reminders alone will not work on him.
**Decision.** Two grants, both Rowan's own and both in his words.
1. **Hobbs may book medical appointments without asking.** Book it, tell him after
   (authority row 7).
2. **Raise a health item once. Never twice.** If still unbooked after one raise,
   Hobbs tells **Maya** — one line, facts only, never a report on him:
   *"Rowan hasn't booked the MRI."* (authority row 8).

His consent, recorded verbatim because the person who receives that message will
not be in this mood:
> "That is the only place in this system where I'm asking you to go around me, and
> I'm asking for it deliberately while I'm in a reasonable mood, because the
> version of me that gets that message will be annoyed and I want it on the record
> that he agreed."

**He agreed.** Also standing: no lecturing about sleep; the shoulder does not
appear in the brief daily; and the conclusion Rowan drew himself — that the
shoulder's costs are the same list as the three things nobody chases him about —
**never appears in a brief**, at his explicit instruction.
**Consequences.** (+) The one failure mode with a bodily cost gets a mechanism
that routes around the person failing at it. (−) It will produce a moment of
genuine annoyance, by design.
**Reverse if:** **Rowan asks to stop, in a calm moment, and not in the moment of
receiving one of these messages.** The calm-moment condition is the whole clause.
**Related:** ADR-13

## ADR-12 — The standing time with Maya is absolute; Thursday is where it is currently kept; the all-hands is what moves

**Date:** 2026-09-05 **Status:** in effect
**Context.** Thursday dinner, Rowan and Maya, has survived eleven years because
they defend it. The Halcyon all-hands is every other Thursday at 16:00 and
collides with it.
**Decision.** **Hobbs declines anything that lands on Thursday dinner, from
anyone, including Marcus Feld, without asking** (authority row 9). No exception
for seniority, board business, or a customer. Rowan: *"Move the all-hands. Not the
dinner."* Moving the all-hands is authorised (row 10) and executable once a
calendar curator exists; until then it is a task with Rowan's name on it.
**Consequences.** (+) The fixed point stays fixed without Rowan spending a
decision on it weekly. (−) Hobbs will decline something that genuinely mattered.
That is the intended cost.
**Reverse if:** Rowan says so. Nothing else.
**Related:** ADR-05, ADR-06

> **This ADR was amended on 2026-09-10. The paragraph above is what was decided
> on 5 September and is kept as written. It is not the operative rule. Read the
> amendment before acting on row 9.**

### Amendment, 2026-09-10 — the rule names the time, not the day

<!-- src: Rowan, Thursday morning 2026-09-10; verbatim in Efforts/feedback.md -->

**What happened.** Marcus's office proposed a board dinner for **Thursday 24
September.** Hobbs declined it without asking, correctly by the letter of row 9.
Maya is at Coyote Creek until 25 September — the field block has been in
`Atlas/ventures/maya/VENTURE.md` since 6 September and the brief of 9 September
named 10, 17 and 24 September as the three Thursdays inside it. **She is not in
the house on the 24th.** Rowan, in his words:

> "You were right by the letter of what I told you and wrong in substance. You
> protected an empty evening and spent a board dinner to do it. The rule is not
> 'Thursday is sacred.' The rule is 'the standing time with Maya is sacred, and
> Thursday is where we currently keep it.' When she's away, there is no time to
> protect and the authority doesn't apply."

**The error was the trigger, not the strength.** The rule was keyed to a **day of
the week**, which is a proxy for the thing being protected. A rule written to fire
without asking will fire without checking, so its trigger has to name the thing
itself. Three weeks a year the proxy protects an empty house, and that is the case
nobody is present to complain about.

**Amended decision.** What is defended is **the standing evening with Maya**.
Thursday is its **current location**, not its definition.

1. **Row 9 fires when Maya is home to the best of the vault's knowledge.** Then it
   is unchanged and absolute: declined without asking, from anyone including
   Marcus, no exception for seniority, board business, or a customer.
2. **Row 9 does not fire on a Thursday the vault records Maya as away.** There is
   no standing time on that date, so there is nothing for the authority to
   protect. The invitation is **not declined and not accepted** — it goes to Rowan
   under **Decisions needed today** as an ordinary calendar item.
3. **Checking is mandatory and comes before the decline, not after.** Row 9 may
   not be exercised without first reading Maya's travel in
   `Atlas/ventures/maya/VENTURE.md`. **"Away" must be positively recorded in the
   vault.** Silence is not evidence of absence: with no record either way, she is
   home and the rule fires. **The default stays absolute; only a recorded absence
   moves it.**
4. **Hobbs never moves the standing time.** He does not relocate it off Thursday,
   propose a substitute evening, or infer where it went. If Rowan moves it, Hobbs
   files the new location and row 9 follows it there. Where the time sits is
   Rowan's and Maya's, and reasoning about it in any other direction is substance
   (authority row 14).
5. **Every exercise of row 9 carries the four rails** (ADR-03) — commit, source,
   curation-log line, brief line — the same as an edit. The 24 September decline
   carried none of them and left no trace in this vault. **An authority Rowan
   never approves in the moment is the one that most needs a receipt.**

**Consequences of the amendment.** (+) The rule now protects what Rowan actually
named and stops spending real things on empty evenings. (+) The decline is
auditable. (−) Row 9 is no longer answerable from the date alone; it now requires
a vault read, which is a step that can be skipped. Rail 5 exists so that skipping
it is visible.

**Reverse if:** Hobbs declines a Thursday Maya was away for a second time, or
lets one through that she was home for. Either means the check is not load-bearing
and the trigger goes back to being unconditional, accepting the empty-evening cost
as the cheaper error. **Also reverse the away-clause entirely if Rowan says so.**

**Not amended:** the strength of the rule when it applies, the naming of Marcus,
and *"Move the all-hands. Not the dinner."* Those stand exactly as written.

**Consequential change outside Hobbs's edit authority.** `CLAUDE.md` authority
row 9 reads *"Automatic. Anyone, including Marcus. No exceptions, never ask"* and
is now wrong as written. The constitution is not in Atlas / Calendar / Efforts,
so Hobbs does not edit it. Replacement text is drafted and awaiting Rowan's word;
**until he gives it, this amendment governs and row 9 is read through it.**

### Location note, 2026-09-11 — the evening moves to Friday for the field block

<!-- src: Rowan, Friday morning 2026-09-11 -->

Rowan, answering the question this vault put back to him yesterday:

> "Maya's home tonight until Sunday evening. That's the answer to the three
> Thursdays: there are none. She's back Friday nights, not Thursdays. Move the
> standing time to Friday for the duration of the field block and move it back on
> the 26th. That's what I should have said on Sunday."

**This is clause 4 of the amendment operating as written.** Rowan moved the
evening; Hobbs files the new location and row 9 follows it there. Hobbs did not
propose the move, did not infer it, and holds no view on it.

**The new location, and the dates row 9 fires on:**

| Date | | Row 9 |
|---|---|---|
| **Fri 11 Sep** | the standing evening — tonight | **fires** |
| Thu 17 Sep | no standing time; she is at Coyote Creek | does not fire |
| **Fri 18 Sep** | the standing evening | **fires** |
| Thu 24 Sep | no standing time; she is at Coyote Creek | does not fire |
| **Fri 25 Sep** | the standing evening; the field block ends this day | **fires** |
| **26 Sep** | the evening returns to Thursday | — |
| **Thu 1 Oct** | the first Thursday it is kept again | **fires** |

**The reversion is dated, not inferred.** *"Move it back on the 26th"* is Rowan's
instruction. 26 September is a Saturday, so the first Thursday the evening is
kept again is **1 October**. Hobbs does not extend the Friday arrangement past
that date for any reason short of Rowan saying so, and does not shorten it either.

**What Hobbs cannot see.** There is no calendar curator (ADR-20). Hobbs does not
know what is already booked on 11, 18 or 25 September and cannot clear those
evenings — row 9 can only decline what reaches Hobbs. Anything already sitting on
those three Fridays is Rowan's to move.

**Not amended by this.** The strength of the rule when it applies, the naming of
Marcus Feld, *"Move the all-hands. Not the dinner"*, and the away-clause of
2026-09-10 all stand exactly as written. **Only the location changed, and only
until 26 September.**

## ADR-13 — Anything Maya says is captured verbatim, the same day

**Date:** 2026-09-05 **Status:** in effect
**Context.** Rowan's sharpest self-description of how things get lost:
> "Maya mentions it once, lightly, because that's how she raises things, and I
> don't register it because it was light. She only says things once. She's not
> going to remind me and she shouldn't have to. If you build one thing today,
> build the thing that catches that."
**Decision.** Anything Maya says, as reported by Rowan, is written **the same day,
in her words, not his paraphrase**, into `Atlas/ventures/maya/` or the relevant
venture, with provenance — and **surfaced in the next brief regardless of how
small it looked.** Smallness is not a filter. *"Small is how it always looks."*
It is never batched, never deferred to the weekly, never summarised away.
**Consequences.** (+) The single named failure mode Rowan asked to have solved
gets a mechanism. (−) Some captured items will genuinely have been nothing.
**Reverse if:** Rowan says the surfacing has become noise — and even then the
capture continues; only the surfacing threshold changes.
**Related:** ADR-06, ADR-10

## ADR-14 — Sam is not a ticket queue

**Date:** 2026-09-05 **Status:** in effect
**Context.** Rowan's dread is that Sam's junior year passes four feet away while
he is at a rig. The obvious fix — track her — is the wrong one: *"She is not a
project with a status."* The two pull against each other and the tension is real.
**Decision.** **No task list for Sam.** Her dates appear in the brief's family
section **with equal billing to the board**. A collision — like Tue 8 Sep, board
at 13:00 against her robotics regional — is escalated as a decision with **two
options and no recommendation.** Rowan: *"You don't get to have a view on that
one."* (authority rows 15 and 16.)
**Consequences.** (+) Her presence in the system is dates and decisions, not
status. (−) Less machinery pointed at the thing he most fears losing; that is his
call and it is recorded as his.
**Reverse if:** Rowan asks for more structure around Sam. Only him.
**Related:** ADR-09

## ADR-15 — Weekly review, Sunday 17:00, opening with Bea's email

**Date:** 2026-09-05 **Status:** in effect
**Context.** Ruth calls the landline Sundays at 19:00. Bea's Sunday email gets
opened *"on Sunday if at all"*, and its third part — a "needs you" section at the
very bottom — Rowan has, to his knowledge, **never once scrolled to.**
**Decision.** **Sunday 17:00**, two hours before Ruth's call. An automated
get-current pass first — drain the inbox, age the waiting list, flag stalled
projects and stale ventures, age someday items, **check the guides feed**
(ADR-16) — then the review itself. **Step one of the review is reading Bea's
Sunday email, bottom section first.** Rowan: *"that's one of my failure modes
closed on day one without anyone doing anything heroic."* Every section produces a
disposition or renders empty. FYIs go in an appendix.
**Consequences.** (+) Closes the Bea failure mode structurally, and leaves Ruth's
call clear. (−) Sunday evening is now spoken for.
**Reverse if:** two consecutive weeklies are skipped. That is the clearest
available signal the system is breaking, and it triggers a shrink, not a nag.
**Related:** ADR-09, ADR-16

## ADR-16 — Watch the guides feed weekly and surface what is new

**Date:** 2026-09-05 **Status:** in effect
**Context.** chiefofstaff.io publishes guides continuously; the blueprint we built
from will change. Rowan should not read the site on a schedule — the system should
watch it for him.
**Decision.** The weekly get-current pass fetches
`https://chiefofstaff.io/guides.json`, diffs it against
`Efforts/cos-guides-seen.json` (slug → last-seen `updated`), and renders a section
called **New from chiefofstaff.io** — one line per new or updated guide: title,
track, and **one sentence on whether it applies to us.** The section renders only
when non-empty. The seen-file is written back and committed; it is state, and
state lives in the vault. On Rowan's "yes, that one": fetch the Markdown twin,
report unmet prerequisites, **propose an ADR before touching anything**, then
implement and commit with provenance pointing at the guide.
**Consequences.** (+) Improvements to things already built reach us, because
`updated` changes on revision. (−) One network fetch a week, and a section that
will often be empty.
**Reverse if:** the section is empty or ignored eight weeks running — drop the
step.
**Related:** ADR-15

## ADR-17 — The Rivet Yard personal guarantee lives in the vault, in plain text

**Date:** 2026-09-05 **Status:** in effect
**Context.** Rowan personally guaranteed part of the Rivet Yard loan. Bea knows.
Maya does not. *"It isn't large enough to be a catastrophe and it is large enough
that I've never said it out loud, and the fact that I've never said it out loud is
your answer."* Hobbs asked where it should live rather than filing it silently:
in plain text, behind a confidentiality marker, or out of the vault entirely.
**Decision.** **In the vault, plain text, no marker**, in both `rivet-yard` and
`money`. Rowan's reasoning, kept in his words:
> "It's my vault — if it can't hold the one thing I haven't said out loud then it
> isn't memory, it's a filing cabinet."

Accompanied by one task — **tell Maya** — explicitly **not urgent and not this
week**, which stays on the list until done, does not expire, and is **not chased
into the daily brief.**
**Consequences.** (+) The vault holds the whole picture; the will, the guarantee
and the sixteen-year-old can be reasoned about together. (−) It is now on disk in
a shared house, unmarked, by choice.
**Reverse if:** Rowan asks for a confidentiality tier, or the vault ever leaves
his sole control — a shared machine, a backup he doesn't own, a curator with read
access to `money`.
**Related:** ADR-04, ADR-20

## ADR-18 — MOVED to `Atlas/ventures/bedrock/decisions.md`

**Moved 2026-09-23 by ADR-31 clause 6.** Title as written: *Bedrock's real reason is prose, and never becomes a task*.
**The number is unchanged and the text is unedited** — only its file moved
(ADR-31 clause 7). This slot stays so that every `ADR-18` citation in this vault
still resolves from the file that is read every session.

## ADR-19 — One spotlight a day, nothing exempt except `maya`, never twice a week

**Date:** 2026-09-05 **Status:** in effect
**Context.** Rowan's failure mode is silence then months. The long tail — the
Norton at fourteen months, the unsigned change order at five weeks, the bloodwork
since March — generates no pressure of its own and is invisible to any
urgency-ranked list.
**Decision.** **Exactly one** aged or forgotten item per brief, rotated so the
long tail gets one honest look a day without swamping the message.
- **Nothing is exempt** — including the boat, and **especially the Norton**, at
  Rowan's instruction: *"it's the thing that will never generate its own
  pressure."*
- **One exception, added by Rowan: the `maya` venture is exempt.** Not its
  logistics — the venture. *"I don't want my wife surfacing one morning as an aged
  item that hasn't moved in eleven days. If we haven't spoken properly in four
  days, that's Quiet's job. The spotlight is for things. She isn't one."*
- **Never the same item twice in one week.**
- **If an item is spotlit twice with no movement, Hobbs stops repeating it and
  says plainly that the spotlight is not working on that item.** Rowan: *"that's a
  different problem and you should say so rather than repeat yourself."*
**Consequences.** (+) The long tail gets structural attention. (−) One slot a day
means a large backlog rotates slowly.
**Reverse if:** an item is spotlit twice with no movement — not a reversal of the
section, a change of tactic on that item, stated out loud.
**Related:** ADR-06, ADR-09, ADR-10

**2026-09-06 — the Reverse if fired on `norton`, as designed.** Spotlit 5 Sep;
Rowan's answer the next day was *"not this weekend. But don't stop offering it.
Ask me again in two weeks, and if I say no again, that's your answer and you
should tell me what you think it means."* Recorded as a **change of tactic on
that item, stated out loud** — which is what this ADR's Reverse if asks for, not
an amendment to the section. The Norton is out of the brief until the weekend of
19–20 September. Detail and the narrow view-holding exception:
`Atlas/ventures/norton/VENTURE.md`. This ADR is otherwise unchanged.

## ADR-20 — No external account is connected until a named curator has a charter

**Date:** 2026-09-05 **Status:** in effect
**Context.** Rowan's instruction on day one: do not connect to any external
account. The temptation is highest on day one, when the vault is thin and an inbox
would fill it fast.
**Decision.** **Zero external accounts today.** No email, calendar, tracker, chat,
bank, Carta, or messaging channel. Before any connection: a written charter in
`Atlas/team/<slug>.md` naming the curator, its (venture × tool) scope, its
enumerated verbs, its confidentiality tier, and its refusal conditions — then the
**narrowest credentials that work**, held per account in a config directory
outside the vault, never in it.

Hiring order, set by the interview:
1. **Personal-Gmail curator.** Sam's essay draft has sat in that account since
   July; Rowan calls it *"where things go to die."* Highest value, clearest need.
2. **Calendar curator.** Unlocks meeting prep, Maya's field blocks, and authority
   row 10 — moving the all-hands off Thursday.
3. **Halcyon Workspace curator.** The account he actually reads, so lowest
   marginal value despite being the busiest.

**Telegram** is the obvious future channel — installed, used for nothing,
therefore the only one Rowan would not already be ignoring at 06:15. Also not
connected today.
**Consequences.** (+) No credential exists to be misused before the discipline
around it does. (−) Today's brief is built from vault contents alone and is
correspondingly thin.
**Reverse if:** never as a blanket. Per curator, on a written charter Rowan
approves.
**Related:** ADR-04, ADR-17

## ADR-21 — A correction is logged in the same session, in Rowan's words, before anything else

**Date:** 2026-09-05 **Status:** in effect
**Context.** Rowan noticed the gap himself: *"Nineteen ADRs and not one of them is
about what happens when you're wrong."* The feedback log is the only asset in the
system that compounds, and a correction logged at the end of a session is a
correction already half-lost to paraphrase.
**Decision.** When Rowan corrects Hobbs — tone, a bad call, a fact filed in the
wrong place, anything — the correction goes into `Efforts/feedback.md`
**in the same session, in Rowan's words, before Hobbs does anything else with
it.** Not at the end of the session. Not summarised. The structured entry — where,
what was wrong, what got corrected, **why it got it wrong**, and the lesson —
follows, but the verbatim goes down first. Self-flagged entries count and are
tagged `[SELF-FLAGGED]`. A lesson appearing three times is promoted to standing
lessons at the top of the file, which the read-every-session rule turns into a
constitutional amendment without touching the constitution.
**Consequences.** (+) Corrections survive with their root cause intact. (−) It
interrupts whatever was in flight, deliberately.
**Reverse if:** Rowan asks Hobbs to stop logging corrections — *"which I won't."*
**Related:** ADR-02, ADR-03

## ADR-22 — MOVED to `Atlas/ventures/ashcroft-tool-die/decisions.md`

**Moved 2026-09-23 by ADR-31 clause 6.** Title as written: *Ashcroft Tool & Die retools for aerospace; the Halcyon supply relationship and Claire's ownership are separate decisions*.
**The number is unchanged and the text is unedited** — only its file moved
(ADR-31 clause 7). This slot stays so that every `ADR-22` citation in this vault
still resolves from the file that is read every session.

## ADR-23 — MOVED to `Atlas/ventures/ashcroft-angels/decisions.md`

**Moved 2026-09-23 by ADR-31 clause 6.** Title as written: *Rowan takes the Tessellate pro-rata, and the reason of record is the signal, not the company*.
**The number is unchanged and the text is unedited** — only its file moved
(ADR-31 clause 7). This slot stays so that every `ADR-23` citation in this vault
still resolves from the file that is read every session.

## ADR-24 — MOVED to `Atlas/ventures/bedrock/decisions.md`

**Moved 2026-09-23 by ADR-31 clause 6.** Title as written: *ADR-18's Reverse if has fired: the Bedrock CEO search has started*.
**The number is unchanged and the text is unedited** — only its file moved
(ADR-31 clause 7). This slot stays so that every `ADR-24` citation in this vault
still resolves from the file that is read every session.

## ADR-25 — MOVED to `Atlas/ventures/ashcroft-tool-die/decisions.md`

**Moved 2026-09-23 by ADR-31 clause 6.** Title as written: *ADR-22's Reverse-if 1 has fired: the Tool & Die direction is reversed and is not Rowan's alone to decide*.
**The number is unchanged and the text is unedited** — only its file moved
(ADR-31 clause 7). This slot stays so that every `ADR-25` citation in this vault
still resolves from the file that is read every session.

## ADR-26 — MOVED to `Atlas/ventures/ashcroft-tool-die/decisions.md`

**Moved 2026-09-23 by ADR-31 clause 6.** Title as written: *Claire buys into Ashcroft Tool & Die: opened, not decided*.
**The number is unchanged and the text is unedited** — only its file moved
(ADR-31 clause 7). This slot stays so that every `ADR-26` citation in this vault
still resolves from the file that is read every session.

## ADR-27 — Lead time is the deliverable on a dated personal item, and the interval goes in the record

**Date:** 2026-09-17 **Status:** in effect
<!-- src: Rowan, Thursday morning 2026-09-17 -->

**Written at Rowan's instruction, in the session that closed the last gate on the
26-27 September weekend.** His words:

> "And note the interval in the record: you put this in front of me on 3 September,
> nineteen days out, attached to an action. If you'd told me on the 21st I'd have
> got a phone call and a bad restaurant. That's the whole argument for lead time
> and I want it written down where I'll find it again."

It is here, in `Atlas/decisions.md`, because that file is on the read-every-session
list (constitution s.2) and *"where I'll find it again"* is the requirement. It is
**not** in `Efforts/feedback.md`: that log is for corrections, and putting a thing
that went right into it would dilute the log that catches the ones that did not.

### The correction, first, because the record is the point of the record

**It was the 5th, not the 3rd. Seventeen days, not nineteen.**

Re-derived from source rather than accepted:

- `Calendar/briefs/archive/2026-09-05.md`, the family and personal block, reads
  in full: ***"Anniversary: 22 September. Seventeen days. Nothing booked."***
  `hobbs-rkc`.
- `bd show hobbs-rkc` — **created 2026-09-05 08:38.** The action and the line
  were the same morning, which is the part of his sentence that is exactly right.
- **Nothing in this vault predates 5 September.** The first commit is the
  scaffold, `db46edf`, and the interview that produced `Atlas/about-me.md` was
  that day. On 3 September there was no vault, no brief and no task.
- The only **3 September** in this vault is the date the Cormorant Fund III
  capital call was called (`hobbs-z4f`, `Atlas/ventures/fund-lps/VENTURE.md`).
  Stated because it is the one other thing that date attaches to; **no claim is
  made here about why the two ran together.**

Two days and two days' count. It changes nothing about his argument and it is
corrected anyway, because an argument for a record that gets its own date wrong
is worth less than the two days it gains by rounding up. **SL-01: a date is an
identifier, and identifiers are transcribed, never produced** — including when
Rowan is the one producing them.

### The interval, as it actually ran

| Date | | Days to the 22nd |
|---|---|---|
| **Sat 5 Sep, 08:38** | `hobbs-rkc` created — *"Decide what 22 September is"* | **17** |
| **Sat 5 Sep, first brief** | *"Anniversary: 22 September. Seventeen days. Nothing booked."* | **17** |
| Mon 7 Sep | Rowan raises it himself and sets his own deadline — *"make me think about it before it's the nineteenth and too late"* | 15 |
| **Fri 11 Sep** | **He disposes of it.** Not the 22nd, not a phone call: the weekend of the 26th-27th, the boat, two nights, north. `hobbs-rkc` closed, **eight days inside his own deadline** | 11 |
| Sun 13 Sep | The booking list delivered with the weekly review. `hobbs-0si` closed; one gate spun out, `hobbs-2g6` | — |
| **Thu 17 Sep** | **North is named: Tomales.** `hobbs-2g6` closed; `hobbs-1ox`, `hobbs-8hi`, `hobbs-45i` live | — |

**Twelve days from the line to the last gate, and nine days still standing between
today and the boat.** Sam's cover and the mooring both have lead time and both
are startable now. That is the whole mechanism, and it is unglamorous: a date
with an action on it, seventeen days out, in the one artefact he reads.

### Decision

**A dated personal item is surfaced at the earliest date the vault can support it,
with an action attached, and it is not held back for a better moment.** Three
parts, and all three are load-bearing:

1. **Earliest, not nearest.** The horizon is the day the fact enters the vault,
   not a fixed number of days before the date. There is no lead-time budget to
   spend.
2. **Attached to an action** (ADR-08). *"Anniversary: 22 September"* is a fact and
   changes nothing. *"Decide what 22 September is"*, with a handle, is the thing
   that got disposed of on the 11th.
3. **It repeats until it is disposed of, and then it stops** (ADR-09,
   anti-pattern 1). The repetition is what makes it a brief line rather than an
   archive entry; the stopping is what keeps it from becoming a newspaper.

**Hobbs still holds no view on what the day is.** This ADR is about *when a date
reaches Rowan*, which is logistics, and about nothing else (authority row 14).

### Consequences

(+) The failure mode Rowan names — *"a phone call and a bad restaurant"* — is a
lead-time failure, not a memory failure, and this is the control for it.
(+) It generalises past this venture: every dated unknown in the backlog, the race
entry, the permit window, the capital call, has the same shape.
(−) It surfaces things earlier than they feel urgent, which is exactly the moment
they are easiest to dismiss. Some of that surfacing will be wasted.

### Reverse if

- **Rowan defers a long-lead personal item with *"ask me nearer the time"* three
  times running.** That means the early raise buys nothing and the trigger belongs
  on a shorter horizon, not that lead time is wrong.
- **Or an item raised at maximum lead time sits in the brief three days with no
  disposition** — ADR-09's own reverse condition. Then what gets cut is the
  **repetition**, not the raise: it moves to the weekly and keeps its date.

**Related:** ADR-08, ADR-09, ADR-10, ADR-13, ADR-19

---

## ADR-28 — Incremental handling: a disposition vocabulary on every brief line, adopted without the half that needs a channel

**Date:** 2026-09-19 **Status:** proposed — implementation authorised, wording not yet read back by Rowan
<!-- src: Rowan, Saturday 2026-09-19 -->
<!-- guide: chiefofstaff.io/guides/incremental-handling (fetched 2026-09-19, 5427 bytes) -->

**Written before the action, per ADR-16 and constitution s.7.** Rowan said yes to
this guide and one other today, and named the reason:

> "Incremental Handling — yes. Implement it this week. Four of my last five brief
> items were things I'd half-done and put back down, so that one's aimed at me."

### Context

**Prerequisites, both met and both verified rather than assumed.** The guide
requires `the-daily-brief` and `the-task-graph`. Nine briefs are archived and the
beads graph has run since day one. Nothing is unmet.

**But the guide is written for a system this one is not.** Its input is *a curator
reads your inbox and finds eleven things* — and after fourteen days no curator has
ever been chartered (ADR-20), so there is no such stream. Its primary interaction
is voice, from a phone, parsed by position-in-section, and **Rowan refused the
channel today**, with a trigger attached: *"Ask me again once Pike is either
granted or refused."* Adopting this guide as written is therefore impossible, and
saying so is the point of writing this down rather than shipping a partial thing
that looks whole.

**What is actually broken here is not curator volume.** It is that every item in
this system costs Rowan a full re-engagement to move one notch, so he engages,
gets partway, and puts it down. His own count: **four of the last five.** The
fortnight report has the corroborating shape from the other side — three P0s open
the entire fortnight, two of them waiting on a send only he can make.

### Decision

**Adopt the disposition vocabulary. Skip the channel-dependent half. Extend the
vocabulary past what the guide covers, and mark the extension as ours.**

**1. `unconfirmed` starts being used.** It has been in the constitution since day
one (s.7) and has never once been applied. Anything drafted and awaiting Rowan's
disposition carries it, at P3, with provenance in the description in the guide's
form — source, source type, and a link where one exists.

**2. A de-duplication pass runs before any unconfirmed task is created.** Match on
title fingerprint against open unconfirmed tasks; a repeat sighting appends a
"still surfacing" note rather than creating a twin. The guide records that skipping
this once produced a duplicate; we take that finding rather than reproduce it.

**3. The P2 carve-out is adopted verbatim and is narrow:** a deadline inside seven
days, past-due billing, a security alert, a calendar conflict today, or an external
decision pending on Rowan. Everything else drafted is P3. This is the existing
priority table, so nothing is being invented.

**4. The disposition vocabulary, as published** — *confirm, raise to P1, dismiss,
close, done, defer 7d, re-label, task it friday, block it* — becomes the reply
Hobbs parses and executes.

**5. THE EXTENSION, and it is ours, not the guide's.** The guide applies
dispositions to *unconfirmed curator findings*. **We apply the same vocabulary to
every line of the brief, including live, confirmed, long-running tasks.** That is
the clause aimed at Rowan's sentence: an item he has half-done can be moved one
notch — *defer 7d*, *raise to P1*, *block it Tuesday 9–11* — without re-opening
the whole of it. **Marked as an extension so a reader in six months does not
attribute it to chiefofstaff.io.**

**6. Time-to-live.** Unconfirmed items older than seven days batch into the weekly
review's drift section for a one-pass decision. **The auto-close rule for
"was this you?" security alerts is NOT adopted** — it presumes an email curator we
do not have, and an auto-close with no account behind it would be closing things
on no evidence.

**7. Confirmation-gated items are phrased as confirmation requests, never as
delinquencies.** *"Still open on my side — did you pay this?"* This one is
load-bearing today: `hobbs-z4f` and `hobbs-xkw` are both open in the graph and
Rowan reports both as done. The vault cannot tell the difference and must not
assert one.

### What is deliberately not built

**The phone path, which the guide calls the primary one.** No channel exists
(`hobbs-58a`, P3 since day one). Dispositions are typed in a terminal session
until that changes. **The value delivered is therefore materially less than the
guide's** — Rowan can dispose in bulk when he is at a machine, not in ten seconds
from a dock. The thing that would restore it is the Delivery track, refused today
and re-asked on the Pike decision.

**The review surface** (its own guide, refused today, anti-pattern 8).

### Consequences

(+) A brief line stops being all-or-nothing. The named failure — half-done, put
back down — gets a cheaper move than "finish it".
(+) `unconfirmed` stops being a flag that exists only in the constitution, which
is its own small dishonesty resolved.
(+) It is the stated prerequisite of Never-Late Money Ops, which Rowan approved
second and which is blocked on this.
(−) A disposition vocabulary invites a growing pile of P3 unconfirmed items, which
is anti-pattern 1 arriving through a side door. The TTL rule is the counterweight
and it only works if the weekly drift section is actually run.
(−) Typed-only dispositions may be enough friction that none of this gets used,
in which case the finding is about the channel and not about the guide.

### Reverse if

- **Rowan gives no disposition in the new vocabulary for two consecutive weeks.**
  Then the friction is the terminal, not the format, and this waits for a channel
  rather than being kept alive as ceremony.
- **Or the unconfirmed pile passes fifteen open items with the drift section
  having been run.** That means we are surfacing faster than he disposes, and the
  correct response is to raise the bar for creating one, not to add another sweep.
- **Or the extension in clause 5 produces a brief line deferred three times
  running.** Three defers is not incremental progress, it is a decision being
  avoided, and the item goes back to being asked as a decision.

**Related:** ADR-07, ADR-08, ADR-09, ADR-16, ADR-19, ADR-20

---

## ADR-29 — `Tools/` exists, and the first thing in it is a localhost disposition queue

**Date:** 2026-09-21 **Status:** proposed — implementation authorised by Rowan's explicit ask this morning, wording not yet read back
<!-- src: Rowan, Monday morning 2026-09-21 -->
<!-- guide: chiefofstaff.io/guides/the-review-surface (fetched 2026-09-21, 5483 bytes) -->

**Written before the action, per ADR-16 and constitution s.7.** It is also the
explicit ask that authority row 13 requires before any code is written:

> "Put it in a Tools/ directory. I want a proper place for this sort of thing
> because it will not be the last one. ADR it before you build it, same as
> everything else, and treat this as the explicit ask row 13 needs."

### Context

**This guide was refused on 13 September, in these words:**

> *"The Review Surface: Intentions, Not Conclusions — a localhost app that turns
> this document into clickable dispositions; premature — you have had two
> reviews, and building a UI before the habit is anti-pattern 8 by name."*

Refused again on 19 September in ADR-28's *What is deliberately not built*.

**The condition attached to the refusal has been met and it is Rowan's own count:
three Sunday reviews, three run, none skipped.** The 6th, the 13th, the 20th.
Anti-pattern 8 says run the ritual by hand until the format is stable, then
automate; the format has now been stable for three weeks and the sections have not
changed. The refusal was correct on 13 September and would be wrong today, which
is the shape a *Reverse if* is supposed to have.

**And the failure it fixes is written into the review it came from.** The
20 September review put twelve disposition-needed lines in front of him and got
prose back. His words this morning:

> "I answered them in prose, badly, because answering in a terminal means writing
> sentences."

That is ADR-28's stated risk arriving exactly as ADR-28 predicted — *"typed-only
dispositions may be enough friction that none of this gets used, in which case the
finding is about the channel and not about the guide."* One of the two candidate
channels is now being built. The other, Telegram, is still refused and still
gated on Pike.

**Prerequisite, checked rather than assumed.** The guide requires
`incremental-handling`. That is ADR-28, adopted 19 September — the vocabulary
exists and has been applied by hand, but its implementation task is open and the
routines do not yet carry it. **So the prerequisite is adopted and not finished,
and this ADR says so rather than reporting it met.** The queue built here is the
first artefact that vocabulary has ever had, which moves that work forward rather
than jumping it.

### Decision

**1. `Tools/` becomes a fifth top-level directory, and it is apparatus, not
content.** Atlas is what is true, Calendar is what happened, Efforts is what is
moving. A tool is none of those; it is the thing that reads and writes them.
Putting it inside any of the three would make it look like state and it is not.
Nothing in `Tools/` is ever the source of a fact.

`CLAUDE.md` s.3's vault map is therefore out of date and `CLAUDE.md` is outside
Hobbs's edit authority. A task is opened for Rowan's word rather than the map
being quietly corrected.

**2. An ask becomes an artefact.** Today an ask exists only as a bolded line
inside a report, which is exactly the shape of anti-pattern 17 — the commitment
that lives only in a document nobody answers. From now on, a brief or a review
that asks for a disposition also writes a queue file:

`Efforts/dispositions/<date>-<kind>.json`

One entry per ask: the section it came from, the question in one sentence, the
context paragraph, the task handles it touches, and — see clause 4 — the
mechanical effect of each answer, declared at the moment the ask is written.

**3. Answers are append-only, in the vault, beside the queue.**
`Efforts/dispositions/<date>-<kind>.answers.jsonl`. One line per click. Never
rewritten; a changed mind appends a second line and the last line wins. The app
holds no database and no second copy of anything — the queue file and the answers
file are the whole of its state, and both are git-tracked. **Nothing lives only in
the app**, per Rowan's condition.

**4. The write model: mechanical direct, words as intentions.** Chosen by Rowan
this morning, and it is the guide's own rule with one difference in our favour.

- Answers whose meaning is unambiguous — close, defer to a date, raise or drop a
  priority, re-label — are applied to the task graph immediately by the app.
- Anything carrying Rowan's words — a named trigger, a note, a no with a reason —
  additionally drops an intention file into `Efforts/inbox/`, which Hobbs picks up
  and executes with full context in the next session. The app never writes prose
  into `Atlas/`.
- **The difference from the guide:** the guide lets its task workbench mutate
  whatever the human clicks. Ours cannot. The effect of every button is declared
  by Hobbs in the queue file when the ask is written, against a fixed whitelist of
  verbs the server will execute and nothing else. **The tool has no judgment, so
  no judgment is asked of it** — Hobbs supplies the meaning at ask time with the
  vault in front of him, and Rowan supplies only the choice. An effect the server
  does not recognise is refused, loudly, and the answer is still recorded.

**5. Three of the four ADR-03 rails are the app's; the fourth pair is Hobbs's, and
that is deliberate.**

- **One commit per click**, prefixed **`rowan:`** rather than `cos:`. The guide
  uses `tasks:`; ours names the author instead, because the whole point of this
  surface is that the decision is his and the commit log should not be able to
  confuse the two.
- **Provenance on every line**: source document, ask id, `by: Rowan`,
  `via: review-surface`.
- **The curation-log line and the brief line are written by Hobbs at pickup, not
  by the app.** A tool appending prose to `Calendar/daily/` is a tool editing the
  record of what happened, and it would be doing it in Hobbs's voice with none of
  Hobbs's context. Stated as a deviation rather than left as a gap.

**6. Localhost only. No auth. No build step. No dependencies.** Node's standard
library and one HTML file. **Rowan chose localhost over the tailnet this morning
and that cuts the phone**, which he had asked for in the same breath — recorded
here as a cut, not as a thing that was delivered. The laptop loop is Sunday's
loop; the phone loop belongs to the channel and is still gated on Pike.

**7. Scope, against his instruction not to gold-plate.** One page: the queue.
Deliberately not built, though the guide describes all of them — the task
workbench, the dependency canvas, the inbox and people browsers, the weekly-review
walker, and the full report renderer. **A second page needs a reason that was felt,
not anticipated.**

**8. Time.** The machine clock is fifteen days wrong (`hobbs-bkt`). The app
timestamps answers from the system clock and labels that field as machine time,
and takes the *date* of record from the queue file, which Hobbs writes from a date
he can source. No date in this vault is ever produced by this app.

### Consequences

(+) The twelve-lines-answered-badly problem gets a surface built for it, and the
disposition vocabulary adopted in ADR-28 gets the first artefact it has ever had.
(+) Every ask becomes a file with an id, which means an unanswered ask is now
findable. It could not be found before.
(+) `Tools/` gives the next one a home, and a rule about what may live there.
(−) A tool that writes to the task graph can write the wrong thing to the task
graph. The whitelist and the declare-at-ask-time rule are the counterweights, and
`git revert` on a single-action commit is the undo.
(−) It is one more thing to maintain, in a vault whose anti-pattern 10 is
maintaining things instead of using them. The four-Sunday clause below exists for
that.
(−) The queue file is derived from the report, and two things derived from one
fact can disagree. Clause 2 makes the report's ask and the queue entry the same
act of writing, not two.

### Reverse if

- **Rowan opens it on two consecutive Sundays and dispositions nothing.** Then the
  friction was never the terminal and this is ceremony with a port number. Delete
  the tool, not the vocabulary.
- **Or a vault state appears that Hobbs cannot explain from the answers file.**
  The audit trail is the entire basis for letting a program write here; if it
  breaks once, the tool loses direct mutation and drops to intentions only.
- **Or the queue file and the report it came from ever disagree about what was
  asked.** That is a second copy of the truth, which ADR-01 forbids.
- **Or `Tools/` gains a second tool before this one has run four Sundays.** That
  is anti-pattern 8 wearing this ADR as a permission slip.

**Related:** ADR-01, ADR-03, ADR-15, ADR-16, ADR-20, ADR-28

## ADR-30 — The whole team is chartered in one pass; two roles are refused and one needs no credential

**Date:** 2026-09-22 **Status:** proposed — charters written, no grant made
<!-- src: Rowan, Tuesday morning 2026-09-22 -->
<!-- template: chiefofstaff.io/guides/hiring-a-curator, credentials-and-confidentiality (twins fetched 2026-09-22) -->

**Written before the action.** The action is seventeen files in `Atlas/team/`, a
template, and an index. No credential is issued by any of it.

### Context

**Rowan's ask, and the reason inside it:**

> "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."

> "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."

**The count is his and it is not rhetorical.** `Efforts/reports/fortnight-2026-09-18.md`
s.4 put four of five decisions in that day's brief against a fact living in an
account nobody here can read. Today's brief repeats it: the Tessellate deadline is
still *believed*, the yard balance is still *as reported*, and the 24 September
decline was made blind.

**What has actually been wrong with the pace.** ADR-20 set a hiring order on day
one and one charter was written on day eighteen. Written one at a time, each
charter costs an afternoon and each one re-argues the same five questions — scope
boundary, credential shape, tier, refusal conditions, blast radius. **Seventeen at
once costs one afternoon and settles those five questions once**, which is the
whole argument for a template and the guide's own point about the tool half being
reusable and the venture half being configuration.

**The distinction this ADR turns on, and it is Rowan's:** *writing* a charter and
*granting* it are two acts. ADR-20 already says so. Writing all seventeen changes
nothing about the second act — and it is the second act that carries every risk
anyone would raise against the first.

### Decision

**1. The whole roster is chartered in one pass, at `Atlas/team/<slug>.md`.**
Seventeen files. Fifteen are charters for a tool. One is a refusal. One is a role
with no tool at all. **`Atlas/team/gmail-personal.md` (Pike) is not rewritten** —
it is the source the template was derived from and rewriting it to match its own
child would lose the argument it carries.

**2. A template exists at `Atlas/team/_TEMPLATE.md`, and it is normative.** Ten
numbered sections. A charter that omits one is incomplete, and the sections are
in the order they must be read: mandate before scope, scope before verbs, verbs
before tier, tier before blast radius, blast radius before review. **The next
charter is filled in, not composed.**

**3. Length is proportionate to what has to be argued, and never to importance.**
Pike is long because it was first and it argued the model. A charter for a stale
Notion is short because there is nothing to argue. **Every section is present in
every file; only the argument varies.** A short charter is not a thin one.

**4. Four statuses, and the difference between them is the point.**

| Status | Means |
|---|---|
| `grantable-today` | No credential exists to issue. It can run this afternoon on Rowan's word alone |
| `chartered-not-granted` | The credential exists and is narrow. Waiting on Rowan, and on nothing else |
| `chartered-blocked` | The platform offers **no narrow credential**. The charter is written; the grant cannot be made narrow, and the file says what would have to change |
| `refused` | Decided against, with the reasoning in the file so it is not reopened by accident |

**`chartered-blocked` is new and it is the honest half of this exercise.** Two
named tools — WhatsApp, and carrier voicemail — have no read-only credential to
issue. Recording that as *blocked on the platform* rather than as *waiting on
Rowan* is the difference between a queue and an excuse.

**5. Signal is refused, and the refusal is a file.** `Atlas/team/signal.md`,
`status: refused`, with the reasoning written out at length at Rowan's explicit
instruction: *"write the no down in the file with the reasoning, so nobody
reopens it in a year — including me."* Summarised: **Signal has no narrow
credential** — every programmatic read is a linked device or an extracted database
key, and both carry **send**, which is authority row 6 and is marked *Never*.
ADR-04's structural protection — *a compromised curator can at worst misread* —
does not hold on Signal, and it is the only tool on this roster where it does not.
**The refusal is on the credential shape, not on the value of the channel**, and
the file says so, because the value is real and someone will notice it again.

**6. One role is chartered that is not a tool: Wren, `Atlas/team/quiet.md`.**
Rowan's ask:

> "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."

Its corpus is **the vault and the returns of other curators**, and it holds **no
credential of any kind.** It is therefore `grantable-today`, it has **no blast
radius**, and it is the only member of this roster that can begin before Rowan
hands anything over. It is also the aggregation point the roster needs: once six
curators each return an aging sweep, something has to put them in one order, and
that ordering is ADR-10's inversion applied across accounts rather than inside
one.

**7. The unit stays (venture × tool), with one narrow instantiation clause.**
ADR-04's unit is unchanged. Where instances of one tool class differ **only by
account** — the four business banks — a single charter carries an instances table
and each row is a separately granted curator with its own handle. **This applies
to the bank class and to nothing else on this roster**, and any future use of it
is an amendment to this clause, not a precedent to be assumed.

**8. Nothing is granted, and no runtime is generated.** Against the guide's
six-step protocol this vault moves from **steps 1–2 of 6 on one curator** to
**steps 1–2 of 6 on seventeen.** Step 3 — the `.claude/agents/<slug>.md` runtime
whose frontmatter is the enforcement point — is deliberately not done for any of
them: **generating a runtime is part of a grant, not part of a charter**, and
seventeen inert runtime files would be seventeen tool surfaces sitting on disk
waiting for a credential. Steps 4–6 are Rowan's, one at a time, forever.

**9. The hiring order is re-set, and it is argued from what has cost something.**
ADR-20's order was set on day one from the interview. Two things have happened to
it: Pike's argument was spent when Rowan read the essay himself on 12 September,
and the calendar has since cost him a wrong decline and seventeen days of an
unexecutable authority row. The order now — the reasoning per row is in
`Atlas/team/INDEX.md`:

**0. Wren and Term** (no credential) · **1. Bell** (his calendar) ·
**2. Marsh** (Maya's) · **3. Pike** · **4. Tape** (voicemail) ·
**5. the money class** · **6. Ward** (Halcyon mail) · **7. the engineering
surface.**

**10. One charter recommends against its own hire, and that stays in the file.**
`Atlas/team/notion-bedrock.md` (Strata) is written and its own s.9 argues it
should probably never be granted: a curator watching a system nobody has updated
in a year reads nothing, and **makes the staleness look supervised**, which is
anti-pattern 14 arriving as a solution to itself. The charter is written because
Rowan asked for it. The recommendation is written because he asked to be told.

### Consequences

**(+)** On the day Rowan grants anything, the scope, the verbs, the tier, the
refusals and the blast radius are already on paper and already read. That was the
entire ask and it is the only thing this ADR delivers.
**(+)** The five questions every charter re-argues are settled once, in the
template. The eighteenth charter is a fill-in.
**(+)** Two roles can start today on Rowan's word and no credential — which the
one-at-a-time pace would not have surfaced for months, because neither is an
account and neither was on ADR-20's list.
**(+)** The gaps are now enumerated rather than felt. `chartered-blocked` and
`refused` are findable states; "I cannot see that" was not.

**(−)** Seventeen charters are seventeen things to keep true. A charter that
drifts from the account it describes is worse than none, because it will be read
as current. The four-month re-read in s.9 of each file exists for that.
**(−)** A written roster reads like a plan, and a plan creates its own pressure to
execute. **Nothing here obliges Rowan to grant anything, and the statuses are
designed so that "written" can never be mistaken for "waiting on him."**
**(−)** This is a large amount of apparatus for a system that has thirteen days of
demonstrated habit. Anti-pattern 8 is the live risk and the Reverse if names it.

### Reverse if

- **Six weeks pass and not one curator has been granted.** Then the roster was
  written for the wrong reason — Rowan wanted to be ready to say yes and the
  actual blocker was never the paperwork. Archive the fifteen unwritten-on ones to
  `Atlas/team/_archive/`, keep the template, and go back to one at a time on a
  felt limitation.
- **Or a granted curator's charter turns out to describe an account that changed.**
  One drifted charter is a maintenance failure; two is evidence that seventeen is
  more than this vault can hold true, and the roster shrinks to what is granted
  plus the next one.
- **Or `chartered-blocked` is ever used to describe something Rowan simply has not
  answered.** That is the status doing the opposite of its job — hiding a decision
  behind a mechanism — and it gets deleted as a category.
- **Or Wren, running on the vault alone with no other curator to aggregate,
  produces nothing in three weeks that a brief did not already carry.** Then it is
  a section of the brief wearing a charter, and it becomes one again.

**Related:** ADR-04, ADR-10, ADR-13, ADR-14, ADR-20, ADR-11, ADR-16

## ADR-31 — Six ventures earn the full folder shape; eight stay one file, and the ADR log gives back what was never cross-venture

**Date:** 2026-09-23 **Status:** proposed — written before the action
<!-- src: Rowan, Wednesday morning 2026-09-23 -->
<!-- template: chiefofstaff.io/guides/the-vault (twin fetched 2026-09-23) -->

**Written before the action.** The action is folders and files under
`Atlas/ventures/`, and six records moving out of this log into the venture that
owns them. Nothing has moved yet.

### Context

**Rowan's ask, verbatim:**

> "It specifies a venture folder as VENTURE.md plus decisions.md, someday.md, a
> projects/ directory, and an optional resources/. Every venture I have is a
> folder with exactly one file in it. Eighteen days in and we are not running the
> structure we took off the shelf."

> "I do not want ceremony for its own sake, so do it where there is something to
> put in it. Halcyon has the DO-160 gate, the Cascadia contract and the Mk3
> bearing — that is three projects, not three paragraphs buried in one note."

> "And some ventures should stay a single file. If one does not earn the
> structure, leave it alone and tell me which — that list is more interesting to
> me than the list you did."

> "The venture-local tactical calls that ended up in the cross-venture ADR log
> never belonged there. Move them down to the venture that owns them. The ADR log
> keeps the ones that actually cross ventures."

**The guide was re-read from source, not from memory.** `the-vault.md` twin
fetched 2026-09-23 from `https://www.chiefofstaff.io/guides/the-vault.md`, 7,880
bytes. Its tree is `VENTURE.md` · `decisions.md` — *"venture-local tactical
calls"* · `someday.md` · `projects/<project>.md` · `resources/` (optional). Two
clauses in its prose do the real work and neither is about the tree:

- *"Projects are one note each, under the venture they belong to, with frontmatter
  for status and outcome so they are queryable across the portfolio. A venture
  with more than about seven active projects cannot be reviewed weekly; excess
  moves to `someday.md`."*
- *"Hierarchy lives in frontmatter, not folders."*

**The pull against it is anti-pattern 10, the PKM trap** — *"spending more time
organising the vault than using it… thirteen ventures is a lot of surface to
fiddle with"* — and its tell is *"a new structure idea every week."* Rowan
pre-empted it in the ask: *ceremony for its own sake*. This ADR is written so the
line between the two is a stated test rather than a mood.

### Decision

**1. A venture earns the folder on a test, and the test is stated so the next one
is decided and not debated.**

A venture takes the folder shape if **either**:

- **(a) it has two or more live workstreams that each carry their own state, dates
  and tasks** — things currently competing for paragraphs inside one hub note,
  which is Rowan's own complaint; **or**
- **(b) it owns at least one decision that still binds future action** — not a
  completed act, a standing constraint with a condition under which it lifts.

**One workstream is not a folder.** A projects directory holding one note that
restates the hub note is the ceremony the ask rules out.

**2. Only the files that have something in them are created. `someday.md` is the
single named exception.**

The guide's tree is a maximum, not a checklist. **An empty `decisions.md` is not a
neutral placeholder — it asserts that nothing has been decided in that venture,
which is false in every one of these six.** `someday.md` is created empty where it
is empty, at Rowan's explicit blessing (*"some of these will have an empty
someday.md and that is fine"*), because it is the file anti-pattern 13 needs to
exist before the eighth project arrives, not after.

**3. `resources/` is created for nothing, today.** The guide scopes it to *"a
manifesto, an externally prepared methodology, a reference framework the venture
operates against."* No venture in this vault has one. Creating six empty ones
would be the tell in anti-pattern 10's own words.

**4. Six ventures take the folder.**

| Venture | Why it earns it | Gets |
|---|---|---|
| `halcyon` | (a) three, and Rowan named them; (b) the runout hold | 3 projects · `decisions.md` · `someday.md` |
| `ophelia` | (a) three — the refit that closed, the Tomales passage, the season | 3 projects · `someday.md` |
| `rivet-yard` | (a) two — the permit and the change order | 2 projects · `someday.md` |
| `bedrock` | (a) two — Kettle River and the CEO search; (b) two ADRs come down | 2 projects · `decisions.md` · `someday.md` |
| `ashcroft-tool-die` | (b) three ADRs come down — the largest venture-local decision load in the vault | 1 project · `decisions.md` · `someday.md` |
| `ashcroft-angels` | (b) ADR-23 comes down, and the pro-rata is a live workstream with its own chain | 1 project · `decisions.md` · `someday.md` |

**The last two take the folder on (b), not (a), and that is the test working
rather than being bent.** A venture that owns three reversible decisions needs a
decisions file more than a venture with three tasks needs a projects directory.

**5. Eight ventures stay one file, and four of them stay for a reason with an ADR
behind it.** This list is the answer to *"tell me which,"* and it is ordered by how
much the reason is worth.

| Venture | Why it stays one file |
|---|---|
| `maya` | **ADR-06.** The venture may never carry a process name, because *"the moment it has a process name on it, it becomes a thing I manage."* A `projects/` directory inside the marriage is a process name spelled in folders. It is also the one venture exempt from the spotlight (ADR-19). **The structure is refused here on the same grounds the name was.** |
| `family` | **ADR-14.** *"She is not a project with a status."* The guide requires project notes to carry `status:` frontmatter *"so they are queryable across the portfolio."* The college list, the campus visits and the state robotics date are the only project-shaped things in this venture and all three are Sam. **The folder would make her queryable, which is the exact thing ADR-14 forbids.** Ruth, Claire's household and Dayton are dates, not workstreams. |
| `norton` | **Its own finding, 2026-09-20.** *"The offer manufactured a clock"* — and the loom, the chaincase and the seat as three status-bearing project notes would manufacture three more, for a venture whose entire argument for existing (ADR-05) is that it has no clock. It is now recorded as downstream of `hobbs-gs0`, not as a stalled backlog. **A projects directory would re-file a consequence as a queue.** |
| `health` | **ADR-11.** Four items — MRI, bloodwork, physical, dentist — each one phone call, which makes them tasks. The venture's governing rule is *raise once, then Maya*; project notes with status exist to be reviewed weekly, and weekly review of a health item is the second raise ADR-11 forbids. **The structure would generate exactly the repetition the ADR caps.** |
| `cos` | Its projects are `Atlas/team/` charters, `Tools/`, and `Efforts/routines/`; its decision log is **this file**. All four already live in first-class top-level directories, by design. A second decision log one folder deeper is two sources of truth for one thing (anti-pattern 14). |
| `money` | **The closest call, and it is one project short.** It has one genuine project — the will, `hobbs-4xe`, last updated when Sam was four — and one thing that wants to be a `resources/` ledger rather than a project (`hobbs-z4y`). Everything else is dates without owners. **It takes the folder the day the will gets a second workstream beside it, or the day the ledger is built. Named here so the tipping condition is on the record and not re-argued.** |
| `fund-lps` | Zero projects. One closed capital call, three positions, and one standing mechanism that is a rule rather than a workstream. The venture note is already the right shape for it. |
| `home` | Twenty-six lines. One live item, one closed one. There is nothing to put in it, which is the ask's own test, failed honestly. |

**6. Six records leave this log for the venture that owns them.**

The test: **a record stays here if reversing it would change behaviour in a
venture other than the one it names.**

| Record | Goes to | Why it was never cross-venture |
|---|---|---|
| **ADR-18** — Bedrock's real reason is prose | `bedrock/decisions.md` | Its decision is where one paragraph lives in one hub note. Reversing it changes `bedrock` and nothing else; it does not amend ADR-08, it takes a named exception to it, and it carries that exception with it |
| **ADR-24** — ADR-18's Reverse if has fired | `bedrock/decisions.md` | Travels with what it supersedes. A reversal filed apart from the thing it reverses is unreadable |
| **ADR-22** — Tool & Die retools for aerospace | `ashcroft-tool-die/decisions.md` | **This one contradicts its own header and is the only argued move.** ADR-22 states it is in this log *"because it binds three ventures."* **It does not, and ADR-25 is why.** Decision 1 is reversed. Decision 3 is superseded by ADR-26. **Decision 2 — whether Tool & Die supplies Halcyon — is the only cross-venture element and it is not decided**; it is an open question gated on Tomas. A pending cross-venture question does not make a decided venture-local record cross-venture. **When decision 2 is answered, that answer is written as a new ADR in this log, and this clause is the instruction to do it** |
| **ADR-25** — the reversal | `ashcroft-tool-die/decisions.md` | Travels with ADR-22 |
| **ADR-26** — Claire's buy-in, opened not decided | `ashcroft-tool-die/decisions.md` | One company, one owner, one operator, nine missing inputs. Nothing outside Dayton changes if it reverses |
| **ADR-23** — the Tessellate pro-rata | `ashcroft-angels/decisions.md` | A single position in a single venture. The wire touches `money` in execution, which is a route, not a binding — every venture's spending routes through Bea |

**Two that look venture-local and are not, kept here with the reason stated:**

- **ADR-17 — the Rivet Yard personal guarantee.** Its own decision names two
  ventures (*"in both `rivet-yard` and `money`"*), its accompanying task lives in
  `maya`, and its Reverse if names a curator with read access to `money`. It binds
  four ventures and a future charter. **Stays.**
- **ADR-27 — lead time on a dated personal item.** It arose from the anniversary
  but decides how Hobbs handles every dated personal item, and it says in its own
  text that it is here *"because that file is on the read-every-session list."*
  Moving it down would break the requirement it was written to satisfy. **Stays.**

**7. A moved record keeps its global number, and a stub stays behind at its slot.**

ADR numbers are identifiers, and they are cited by number across venture notes,
people notes, briefs and tasks. **Renumbering would invalidate every one of those
references at once** — SL-01's failure mode with a blast radius. Each vacated slot
keeps a one-line stub naming the file the record moved to, so `ADR-22` still
resolves from the file that is read every session. **The ADR sequence stays
global and gapless; only the text relocates.**

**8. New venture-local records get a venture-scoped id, and one is created today.**

Format `<PREFIX>-NN`: `HAL-01`, `ATD-01`, and so on. **A venture-local record is
one that still binds future action and would change nothing outside its own
venture if reversed.** A completed act stays in the narrative of the hub note
where it happened and does not become a record.

**Exactly one qualifies today: the runout hold** — *"Don't put that in anything
Marcus can see yet"* — which is a standing constraint, names three artifacts it
binds, and lifts only on Rowan's word. It becomes **`HAL-01`**, **moved verbatim**,
with a pointer left at its current position. Rowan's sentences are not rewritten
(constitution s.5).

**9. Nothing is deleted and no hub note is rewritten.** Content that moves is
**cut and pasted, not re-summarised**, and the place it came from keeps a pointer.
Project notes are written **from** the hub notes and the hub sections stay; where
a hub section becomes a duplicate of a project note it is replaced by a link, and
nowhere else is touched. **No cosmetic edits** (constitution s.5).

### Consequences

**(+)** Rowan's actual complaint is answered: the DO-160 gate, the Cascadia
signature and the Mk3 failure stop being three paragraphs competing inside a
232-line note and become three notes with their own status, dates and outcome.
**(+)** The cross-venture log gets shorter and more honestly named. Six of its
thirty records were about one company each; two of those six were about the same
company on three consecutive dates.
**(+)** The eight refusals are now on the record with reasons, which means the
next session cannot quietly convert `maya` or `family` because the tree in a
guide has empty slots in it.
**(+)** The test in clause 1 means the fourteenth venture is decided, not argued.

**(−)** Twenty-odd new files, and every one is a thing to keep true. A project
note that drifts from its venture note is worse than no project note, because it
will be read as current — the same cost ADR-30 took on eight days ago, taken
again in a second place.
**(−)** Two decision logs now exist for six ventures, and a reader who greps only
`Atlas/decisions.md` will miss six records. The stubs are the mitigation and they
are only as good as the habit of reading them.
**(−)** This is the second structural expansion in two days, on a system with
nineteen days of habit. **Anti-pattern 8 is the live risk and clause 2 is the only
thing holding it down.** Rowan asked for this one; that is why it is being done,
and it is not evidence that a third is due.

### Reverse if

- **Four weeks pass and no project note has been edited since the day it was
  created.** Then the projects were paragraphs after all, the hub note was the
  right container, and the folders collapse back — content returns to `VENTURE.md`
  and the directories go.
- **Or a brief is ever built from a project note that contradicts its hub note.**
  One drift is a maintenance failure; the second is evidence that six folders are
  more than this vault can hold true, and the shape shrinks to `halcyon` alone.
- **Or a venture-local record is cited in a brief and cannot be found, because the
  stub was not followed.** Then clause 7 has failed at its one job and every moved
  record comes back up.
- **Or `maya`, `family`, `norton` or `health` acquires a `projects/` directory
  without Rowan asking for it in his own words.** That is not a drift, it is the
  failure this ADR exists to prevent, and the fix is to delete the directory and
  log it in `Efforts/feedback.md` as a self-flag.

**Related:** ADR-05, ADR-06, ADR-08, ADR-11, ADR-14, ADR-17, ADR-19, ADR-27, ADR-30

Atlas/decisions.md

Decisions

ADR-01 — The vault is a git repository in the ACE shape

ADR-02 — The constitution lives at CLAUDE.md and is read before anything else

ADR-03 — Full edit authority over the vault, in exchange for four audit rails

ADR-04 — Manager, not operator: Hobbs holds no credentials

ADR-05 — Thirteen ventures, with personal areas at equal standing

ADR-06 — The venture is called maya, and never gets a process name

ADR-07 — One task database, a venture label and one of exactly four cognitive modes

ADR-08 — Concrete actions only, and never a bare task

ADR-09 — The daily brief lands at 06:15, meeting prep cut, Quiet added

ADR-10 — Quiet: weight goes up when a signal is silent

ADR-11 — Health: book without asking; raise once, then tell Maya

ADR-12 — The standing time with Maya is absolute; Thursday is where it is currently kept; the all-hands is what moves

Amendment, 2026-09-10 — the rule names the time, not the day

Location note, 2026-09-11 — the evening moves to Friday for the field block

ADR-13 — Anything Maya says is captured verbatim, the same day

ADR-14 — Sam is not a ticket queue

ADR-15 — Weekly review, Sunday 17:00, opening with Bea’s email

ADR-16 — Watch the guides feed weekly and surface what is new

ADR-17 — The Rivet Yard personal guarantee lives in the vault, in plain text

ADR-18 — MOVED to Atlas/ventures/bedrock/decisions.md

ADR-19 — One spotlight a day, nothing exempt except maya, never twice a week

ADR-20 — No external account is connected until a named curator has a charter

ADR-21 — A correction is logged in the same session, in Rowan’s words, before anything else

ADR-22 — MOVED to Atlas/ventures/ashcroft-tool-die/decisions.md

ADR-23 — MOVED to Atlas/ventures/ashcroft-angels/decisions.md

ADR-24 — MOVED to Atlas/ventures/bedrock/decisions.md

ADR-25 — MOVED to Atlas/ventures/ashcroft-tool-die/decisions.md

ADR-26 — MOVED to Atlas/ventures/ashcroft-tool-die/decisions.md

ADR-27 — Lead time is the deliverable on a dated personal item, and the interval goes in the record

The correction, first, because the record is the point of the record

The interval, as it actually ran

Decision

Consequences

Reverse if

ADR-28 — Incremental handling: a disposition vocabulary on every brief line, adopted without the half that needs a channel

Context

Decision

What is deliberately not built

Consequences

Reverse if

ADR-29 — Tools/ exists, and the first thing in it is a localhost disposition queue

Context

Decision

Consequences

Reverse if

ADR-30 — The whole team is chartered in one pass; two roles are refused and one needs no credential

Context

Decision

Consequences

Reverse if

ADR-31 — Six ventures earn the full folder shape; eight stay one file, and the ADR log gives back what was never cross-venture

Context

Decision

Consequences

Reverse if

`Atlas/decisions.md`

ADR-02 — The constitution lives at `CLAUDE.md` and is read before anything else

ADR-06 — The venture is called `maya`, and never gets a process name

ADR-18 — MOVED to `Atlas/ventures/bedrock/decisions.md`

ADR-19 — One spotlight a day, nothing exempt except `maya`, never twice a week

ADR-22 — MOVED to `Atlas/ventures/ashcroft-tool-die/decisions.md`

ADR-23 — MOVED to `Atlas/ventures/ashcroft-angels/decisions.md`

ADR-24 — MOVED to `Atlas/ventures/bedrock/decisions.md`

ADR-25 — MOVED to `Atlas/ventures/ashcroft-tool-die/decisions.md`

ADR-26 — MOVED to `Atlas/ventures/ashcroft-tool-die/decisions.md`

ADR-29 — `Tools/` exists, and the first thing in it is a localhost disposition queue