The EP company vault went from an un-governed 8,000-file sprawl to a scalable, multi-writer federation that Prism, Echo, and Carl co-own, and it now generates and tests its own new knowledge.
The vault was never empty. It was un-governed: no operating contract, no single home per fact, competing wikis, a dead 31-agent fleet, and no way to search or maintain it. The rebuild gave it a written constitution and a clean shape, consolidated the sprawl, and added a generative loop that proposes new conclusions and refuses to trust them until reality has graded them.
Nothing was lost. Every move is reversible in git, the client deliverables stay in the repo for every co-owner, and one tag rolls the whole thing back. Prism built and merged it; this page is the read-in for the people who share it next.
What changed
The same content, filed by owner and lifecycle instead of by accident. The headline moves:
| Measure | Before | After | |
|---|---|---|---|
| Operating contract | none | → | root CLAUDE.md |
| Live agent homes | 31 dirs | → | 2 |
| company/ subfolders | 39 | → | 31 |
| Canonical wikis | 2–3 | → | 1 (238 pages) |
| Remote branches | 19 | → | 7 |
| Generative loop | none | → | live + gated |
How it functions
The old vault tangled four different things into flat peers. The rebuild separates them by who owns them and how they change. Every fact now lives in exactly one place, which is both the filing rule and the reason two writers almost never touch the same file.
Immutable sources plus the one canonical wiki. Our current best understanding, revised freely, never silently overwritten.
Identity, memory, checkpoints, and per-agent specialty wikis. Prism and Echo, and the pointer to Prism's sovereign vault.
What has been decided, not synthesized: mission, clients, SOPs, ratified decisions. Agents propose; humans ratify.
The board room, shared skills and keys, and the report-only maintenance zone that automation writes to and never past.
wiki/ is our current best understanding (agents rewrite it, invalidate-don't-delete). company/ is what we have decided (human-owned truth, changed only by a reviewed proposal). That split is what makes three writers work.
The new part
The generative loop reads the knowledge graph for conclusions it already implies but nobody wrote down: a page links B, B links C, but nothing links A to C. That missing edge is a candidate. On the live 238-page graph it surfaced 3,392 of them.
A candidate is only a question. It becomes a card with a claim, a falsification condition, and a test plan, and then it faces the gate that is the whole point of the design: only a SOUND verifier, reality itself, can promote a claim into curated knowledge. A council of AI critics is a WEAK cross-check and may never promote a claim on its own. An untested conjecture never enters a curated page.
Claim: as general-purpose AI commoditizes, defensible value concentrates at two poles, platform ownership (Apple, on-device) and vertical domination (Shield AI, defense), as two instances of one force.
How it scales
Adding a person, an agent, or a client is a template plus one ownership line, not a reorganization. Each writer's high-frequency work (their own domain, their checkpoints, their status) is direct-push with no waiting. The shared truth (the wiki, the company record) is proposal-and-review, so nothing shared changes unseen. Ownership is routed softly by folder and recorded per page, so a three-author vault never deadlocks on a merge, and search is already wired so the vault stays findable as it fills.
Get your data in
The vault is ready to receive. Two ways in: promote a section of your own vault as a reviewed bundle, and file status at end of day and end of week. Here is the concrete path for each of you.
domains/_template into domains/echo/ for your specialty synthesis. It is yours, direct-push, no review needed.wiki/ by pull request. The shared copy carries provenance back to yours.status/; it auto-merges. The weekly rollup gathers them into the company timeline.domains/echo/ and agents/echo/ is yours to write freely; the shared core is where you propose.company/. The decided record, clients, mission, SOPs, ratified decisions, is human-owned. You and Branden hold final say on what merges there.company/clients/ by pull request. Deliverables (PDFs, designs) stay tracked so every co-owner gets them.company/; an agent may draft, but a human sign-off is what makes it the record.Honest edges
The structure is done and merged. A few pieces wait on one call each, not on more building.