The demo vault

This site can describe a vault forever and never show you one — the confidentiality rule makes sure of it. So here is a whole one that belongs to nobody: 146 files, 254 commits, 18 days in the life of a founder who does not exist.

Nothing in it was written by hand. Every file was produced by Claude Code sessions running the bootstrap prompt — the same one you would paste. The first session interviewed the principal for nine rounds and scaffolded the vault one commit at a time; each session after it was a single day of his fortnight. He is invented, and so is everyone in it.

Explore the vault

Every file, as it was left on day 18 — the constitution, thirteen ventures, twenty-one people, the task graph, nine daily briefs.

How it was built

All 254 commits, in order, grouped by the day they belong to. An empty folder becoming a vault, one confirmed decision at a time.

Scenarios

Three runs, each following one mechanism end to end: a voice note that became five decisions, a decision reversed by its own stated condition, and the weekly review.

Start anywhere

CLAUDE.md — Seventeen authority rows, approved line by line.
Atlas/decisions.md — Twenty-seven records, each with a Reverse-if. One of them fired.
Efforts/feedback.md — Seven corrections. Six of them self-flagged.
Calendar/briefs/archive/2026-09-05.md — Day one, built from vault contents alone.

What is honest about this

The vault is not a mock-up and it has not been tidied. The assistant makes mistakes in it: six of the seven feedback-log entries are it catching itself, including one where it invented a task handle the day after logging the lesson forbidding invented task handles. A decision it wrote on day five is reversed on day eleven. One venture has almost nothing in it for the whole fortnight, and the weekly review says so rather than inventing activity.

A few files mention localhost:8788. That is real too — the vault was built against a locally served copy of this site, because for its first fourteen days this site was not yet deployed. The thread that runs out of that is the best evidence here that nothing was staged: the watcher refused to report “nothing new” from a fetch it could not make, and did so for three weeks running; a cause was then inferred from a comment in the script rather than probed, went into a task title, and stood there as fact for thirteen days before the assistant caught it and wrote itself up for it. On day fifteen — the first session after this site went live — it repointed the watcher at the public feed, closed the task, and found something the local copy had been hiding.

Take it

The whole vault is in the repository at demo/vault/. Clone it, open it in Obsidian, or point your own Claude at it and ask what it would do on day 19.