Versions
Every release of this site. The badge in the top bar reads current from versions/index.json↗ and links to that version's own details, rather than to a generic changelog, which is what the guidance asks for.
| Version | Date | What changed |
|---|---|---|
| v0.11.0↗ | 2026-09-22 | the Gmail connector measured end to end by the agent that holds it, read from a vault, mapped into the grammar, and set beside the profile read from the vendors' pages |
| v0.10.1↗ | 2026-09-22 | the desktop walkthrough gets its article, with six figures captured from the v0.10.0 tag |
| v0.10.0↗ | 2026-09-22 | the desktop walkthrough: an assistant on your own machine, the map of what matters on it, and the rules that open with the map; plus the article for v0.9.0 |
| v0.9.0↗ | 2026-09-22 | two more cases: the session that built this site, as a ledger with a measured grant, and one person's three surfaces of one product over an account that holds every past conversation |
| v0.8.1↗ | 2026-09-22 | the cost ABP gets its article, with six figures captured from the v0.8.0 tag |
| v0.8.0↗ | 2026-09-22 | the cost ABP: a walkthrough over how much an agent may spend rather than what it may do, with a ledger every turn and an accountant to read it |
| v0.7.1↗ | 2026-09-21 | the first case gets its article, with six figures captured from the v0.7.0 tag |
| v0.7.0↗ | 2026-09-21 | the first case: one person's estate of six deployments, the mandates elicited from an interview line by line, and the grants not yet measured |
| v0.6.1↗ | 2026-09-21 | the mailbox walkthrough gets its article, with six figures captured from the v0.6.0 tag |
| v0.6.0↗ | 2026-09-21 | a walkthrough for somebody who has connected an assistant to their own mailbox: four pages, thirteen prompts, and a fourth page that says what a prompt cannot do |
| v0.5.1↗ | 2026-09-21 | the articles run newest first, carry their version in the title, and link to the release before and after them |
| v0.5.0↗ | 2026-09-20 | the releases get one article each, with the screenshots taken from the tag each one names rather than from today's site |
| v0.4.4↗ | 2026-09-20 | seven shapes contributed by riskmandate.ai are promoted with their provenance, a vendor scope becomes a node, and the intake path is the same for anybody |
| v0.4.3↗ | 2026-09-20 | the product, the tool and the setting become nodes, derived from data already published, and whose material is declared on the grammar |
| v0.4.2↗ | 2026-09-20 | the fact set is data, the fact diff runs over every published page, and every example ends by crossing nine universes |
| v0.4.1↗ | 2026-09-20 | the universes become data with a page each, the walk of one row is built on every build, and the gate checks that every node type is owned |
| v0.4.0↗ | 2026-09-20 | the ABP is mapped onto Fractal Semantic Graphs: one row crosses nine universes and each keeps its own ontology |
| v0.3.0↗ | 2026-09-12 | read, file and project become nodes with their own addresses, and a node type stops being a label and becomes a formula |
| v0.2.0↗ | 2026-09-11 | the delta is derived and never authored, so it is stored with its inputs pinned and the gate recomputes it |
| v0.1.0↗ | 2026-09-11 | the ontology is promoted out of a game and the five examples are derived rather than written |
How the version cannot drift
admin/build/version.txt owns the version. The tag is derived from it by CI, which refuses to tag unless the newest release commit's subject carries the same string and the bump is the next one. The build generates versions/index.json↗ and a file per version from that same string, and the release gate fails if the badge, llms.txt, the twins or the version surface disagree with it.
Each entry records the commit, because a version without one cannot be verified later, and says when it was reconstructed, because history assembled after the fact has to be labelled.
The machine readable index↗ · The repository ↗