.gitattributes
# Use bd merge for beads JSONL files
.beads/issues.jsonl merge=beads
The vault 146 files
of
Not a screenshot and not a mock-up: 146 real files, produced by Claude Code sessions running the bootstrap prompt. Every page here shows one file at its real path.
The next two minutes are about the shape — where anything you would want to store goes.
Plain Markdown, tracked in git, openable in Obsidian or any editor. No database, no vendor memory feature, nothing stored anywhere else.
That buys two things: portability — switch models in three years and the new one reads the same files — and auditability, because every change to the assistant's beliefs is a commit you can diff and revert.
CLAUDE.md is the constitution: who the
assistant is, what it may do alone, what it must never do. The assistant reads it first, every
session.
HOME.md is the dashboard for the human — the one file you open. Everything
below is reached from one of those two.
Everything that stays true over time.
-
ventures/<slug>/VENTURE.md— one hub note per company, side project or life area. 14 here, and family, health, home and money are ventures with equal standing. -
people/<Name>.md— one note per person, 21 of them. Someone in two ventures is still one note, wiki-linked from both. team/<slug>.md— one charter per sub-agent. 18 written here.-
decisions.md,about-me.md,anti-patterns.md— the log, the identity, the known failure modes.
Status and hierarchy live in frontmatter, never in folder names: folders are permanent, status is not.
Time-indexed, and never rewritten. 18 daily notes — which double as the assistant's curation log — and an archive of every brief ever delivered, 11 of them.
History stays history. Nothing in here is edited after the day it belongs to.
inbox/— every raw capture lands here before triage. Voice notes, forwards, fragments.routines/— the daily brief and weekly review, written down as procedures.cadence.md— when the rituals fire.feedback.md— every correction, read at the start of every session.reports/— deliverables, once they are finished things rather than working notes.
Atlas is what is true, Calendar what happened, Efforts what is moving. A tool is none of the three — it is the apparatus that reads and writes them, and it is never the source of a fact.
There is one: a review surface, a localhost page that turns a brief's open questions into buttons. It earned the folder because a ritual done by hand had become the bottleneck; asked for before that, it was refused.
.beads/ is the task graph — issues as JSONL,
git-tracked, so work diffs like everything else in the vault.
.claude/commands/ holds the slash commands.
/daily-brief lives there because
a ritual is a procedure, not a prompt retyped each
morning.
AGENTS.md is the constitution again, under the name other agents look for.
A curator's note is this site talking — commentary about the file, and never part of the vault. Most files do not have one. The vault itself is published untouched, which is the whole point of showing it to you.
Every rendered page keeps its Markdown source folded underneath. Open it and you are reading what the assistant actually wrote, rather than what we made of it.
Three folders, two entry points, and a task graph. Where to go next:
- The Vault: Atlas, Calendar, Efforts — the guide that specifies all of this.
- How it was built — the same vault as an empty folder, one commit at a time.
- Scenarios — three narrated runs that follow one mechanism end to end.
Or just start clicking. Nothing here is private, because nobody in it exists.