Home / Articles
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
The articles
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.
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.
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.
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.
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.
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.
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.
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.
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.
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