The articles
One article per release, explaining what changed and why, with the screenshots taken from the tag each one names and diagrams of the mechanisms a screenshot cannot show.
Source: https://abp.sgit.ai/articles/index.html↗ · site v0.11.0 · this file is generated from the same content
as the page, so the two cannot drift. Every page on this site has a .md twin; internal links
below point at them.
One article per release
The version surface says what changed, in the release's own words, and it is deliberately terse. These articles say why, one per release, and they show the site as it stood at that release rather than as it stands now.
Eight releases, four measures
[A chart here in the page: four small line panels, one per measure, across the eight releases. Pages: v0.1.0 52, v0.2.0 55, v0.3.0 93, v0.4.0 95, v0.4.1 111, v0.4.2 112, v0.4.3 113, v0.4.4 114. Nodes in the graph: none before v0.3.0, then 170 at v0.3.0 through v0.4.2, 216 at v0.4.3 and 369 at v0.4.4. Edges in the graph: none before v0.3.0, then 488 through v0.4.2, 658 at v0.4.3 and 993 at v0.4.4. Checks in the release gate: 10, 10, 11, 11, 12, 13, 13, 13. Each panel keeps its own scale]
The articles, newest release first
One article per release, and the article is the release. Each one is titled with the version it is about, says what that release changed and what it did not settle, and links to the release before it and the release after it, so the sequence can be read in either direction.
v0.10.0: The desktop walkthrough: on your own machine, host means your machine, and the mandate is a map of what matters before it is a list of rules↗: The third walkthrough in the same four steps, because the workflow is meant to always be the same. On a machine the published shape's character is that reading files, changing them and running commands each sit at a switch the account can flip. The concept the section is built on is the deployer's: what is being given to the agent is context on what is important and what is not. 22 September 2026 · the current release
v0.9.0: Two more cases: this site's own session as a ledger, and three surfaces of one product over a record that contains secrets↗: The cost walkthrough said no case had run its prompts. The first case here is that case, on the one shape whose grant was measured, with a ledger counted from the repository and the workflow log. The second is a deployer with one assistant on three surfaces and one rule: reading the past is on demand. 22 September 2026 · 1 release back
v0.8.0: The cost ABP: every ABP so far bounded what, and this one bounds how much↗: Cost is not a capability. It is a property of every call, the grammar has one primitive for money and none for a count, and quantity lives in the one universe this site has no node in. So the release says that first, then puts the substance where it can live: twelve prompts, a ledger every turn, and an accountant to read it. 22 September 2026 · 2 releases back
v0.7.0: The first case: one person's estate, the mandates elicited line by line, and the grants left empty on purpose↗: Every shape on this site is a vendor's product in a configuration. A case is one person, the assistants they actually run and the connectors they actually switched on, with a mandate for each in their own words. The first one has two assistants, six deployments and one account four of them share, and it starts with the mandate side full and the grant side empty, which is the opposite of a shape. 21 September 2026 · 3 releases back
v0.6.0: Thirteen prompts a reader runs against their own mailbox, and the fourth page that says what a prompt cannot do↗: Every page before this one was written for somebody who already believes the argument. This release adds the door: a walkthrough that does not hand a reader a table, because the agent in front of them can produce a better one for their own deployment. And the page that keeps it honest, which is the one that says the document they just wrote is not a control. 21 September 2026 · 4 releases back
v0.5.0: The releases get one article each, and the screenshots come from the tag rather than from today's site↗: A release record says what changed and is deliberately terse. Nothing said why. This release adds the section you are reading, and the rule that makes it worth reading: a figure about the eleventh of September shows the site as it stood on the eleventh of September, version badge and all. 20 September 2026 · 5 releases back
v0.4.4: Seven deployment shapes somebody else measured, promoted with their provenance intact↗: A consumer of this data built seven shapes this site did not have, one of them from a dated probe of a live instance. Under the three layers those are facts owned by nobody, so they belong at the address every consumer reads. The bytes are held unchanged and the evidence tier stays the contributor's. 20 September 2026 · 6 releases back
v0.4.3: The home page has argued about one setting since v0.1.0, and now the build walks it↗: A product, a tool and a setting became node types with formulas, derived from data the site already held. The setting that distinguishes confirmations on from confirmations off was found by diffing two grants, and whose material a capability reaches was declared without being guessed. 20 September 2026 · 7 releases back
v0.4.2: The fact diff was named as a blocker on four consecutive days, and it reads the published page↗: Every projection renders the same fact set with an empty diff. That rule had no mechanism behind it for a month. The mechanism parses the label, the leaflet, the prohibitions and the figure back out of the page that shipped, because a diff that trusts the generator checks nothing. 20 September 2026 · 8 releases back
v0.4.1: The map became files, pages and a gate check, and the walk is rebuilt on every build↗: A map in prose is a claim. Thirteen universes as data with a page each, a walk computed from the published rows, and a fourteenth check that refuses to publish a world nobody owns. The walk immediately found an error in the brief that drew it. 20 September 2026 · 9 releases back
v0.4.0: An ABP is a junction object, which is what Fractal Semantic Graphs is for↗: Applying the zoom test to this site's own graph returns an uncomfortable answer: it decomposes one vocabulary very well and crosses into another in exactly two places. The map names the nine worlds one capability row actually crosses, and who owns each. 20 September 2026 · 10 releases back
v0.3.0: read.file.project was a string with a gloss beside it, which is schema-first thinking in graph syntax↗: Thirty three words that existed only as substrings got a node, a file and a page each. A node type stopped being a label and became a formula the build walks. And the reach pages started keeping nine disagreeing definitions of one word instead of averaging them. 12 September 2026 · 11 releases back
v0.2.0: A rule this site published in the morning was wrong by the afternoon, and the correction is on the page↗: The foundation document says twice that the delta is computed and never stored. Half of that was right. The corrected rule is harder, the passages were not rewritten, and the check that enforced the old rule was inverted to enforce the new one. 11 September 2026 · 12 releases back
v0.1.0: The ontology already existed, so the first release promoted it instead of writing one↗: Twenty three capability primitives, nine deployment shapes and four barriers were already published as the data pack a game reads. The first release gave them an address and derived five worked ABPs from them, and the thing that took the time was the honesty line rather than the research. 11 September 2026 · 13 releases back
Reading forwards starts at v0.1.0↗, the first release, and follows the newer link at the foot of each article. Reading backwards starts at v0.10.0↗ and follows the older link.
How the screenshots were taken
Every screenshot in these articles came from the tag it names, not from today's site. For each of the eight release tags, a detached worktree produced a checkout of that exact commit, a static server served it on a local port, and a headless browser captured the named section of the named page. Every caption states the version and the capture date on its face.
Why that is worth the trouble. A screenshot of today's page illustrating a claim about the eleventh of September is a small lie, and it is the kind nobody ever catches, because the page looks right and the claim sounds right. The tags are in the repository and the method is four commands, so the figures are reproducible rather than trusted.
What these articles do not do
- They carry no score. Not a rating and not a level, here or anywhere else on this site. That rule is the reason the site exists in the shape it does.
- They make no claim about a named product. Where an article names one, it names it as a deployment shape with a source, a date and a measured ratio, and attaches no adjective to it.
- They do not restate the model. Where an article describes a rule, it links to the page that owns it. If the two ever disagree, the model page is right and this is an article that needs correcting.
The version surface↗ · The model↗ · The data↗