No entry, no claim.
Every page here leads with a receipt: a specific entry number, read back from the live graph while the page was written, not reconstructed afterward for the pitch. Where a claim couldn’t be receipted, it isn’t here — that’s a smaller hub than the first draft, and it’s the honest one.
The two halves below sort by what they’re about: the machinery that runs the work (spawning, roles, the dashboard), and what the graph itself does (supersession, drift, lineage). Both halves are the same product, described from two angles.
What runs the work.
Spawning, roles, trust, the dashboard that watches it — the parts a session touches directly.
| Page | What it shows |
|---|---|
| the Kitchen | A node-and-wire canvas for building recipes. The live scout-and-brief graph runs 15 nodes across all 15 v2 kinds (#13048). |
| cookbook & recipes | The catalog a recipe is drawn from, and the honest count of what actually executes today (#13048). |
| fan-out & spawn | One session, many workers, running at 42% of a Pro plan for five shipped features in fifteen minutes (#860). |
| roles & the officer tier | Colonel, Lieutenant, Sergeant, Private — a rank a worker cannot promote itself out of (#13341). |
| trust profiles | The deny floor every worker spawns under, extended from 20 to 49 patterns this week (#13341). |
| workspace binding | Liveness measured from the work on disk, not from whether a worker happened to call a tool recently (#13062). |
| the dashboard | It renders the same graph these pages cite — the receipts and the picture come from one source (#245). |
| ingest | A real repository, walked end to end into the graph, with the bugs that surfaced and got fixed on the record (#6228). |
| federation & sharing | Two operators, two continents, two model families, one graph — proven live, not just designed (#8922, #11287). |
What the substrate itself does.
Supersession, claims, drift, lineage — the properties of the graph these pages and the product are both built on.
| Page | What it shows |
|---|---|
| supersession | Nothing is edited in place. A correction replaces a decision on the record and says so — including the time it replaced only half of one (#12977). |
| directives & claims | A claim is a lease on files, not a promise. Two workers cannot hold the same file at once (#7759). |
| drift & re-derivation | Re-deriving an answer the graph already has is a measured failure mode, not a hunch — mined, counted, and tagged (#6477). |
| threads as branches | Git is the checkpoint layer; Vinculum is the coordination layer. Threads are the branches now (#181). |
Common questions.
Why does every page cite an entry number?
Because the alternative is a feature page that is a claim with an illustration, and every competitor already ships one of those. Vinculum has been recording its own work since the first entry, so a claim about what it does can point at the record of it happening rather than ask to be taken on faith.
What if a claim doesn't have one?
Then it doesn’t go on the page. That rule is why some of the numbers here are smaller or older than a pitch deck would prefer — a page that can only cite what actually happened describes a smaller, truer product than one that doesn’t bother checking.
What does a citation like #12977 mean?
It’s the sequence number of an entry in Vinculum’s own substrate — the same graph these pages describe. Every number on this hub and its spokes was read back from that graph while the page was built, not typed from memory.