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

v0.4.0, 20 September 2026. v0.4.0's own release record.

A test this site had been quoting backwards

The network's graph site defines a property it calls fractal, and this site's graph module quoted its first edition: if zooming into a node needs a new format or a special case, the system is hierarchical rather than fractal. That wording scores decomposition as a pass, and it was corrected at the source in August and propagated in September.

The corrected test is in two halves. What survives every zoom is the grammar: every edge a verb with an inverse, meaning in connectivity, supersede never delete, provenance kept. The ontology is meant to change. A system whose types and verbs are identical all the way down is a hierarchy.

The zoom test, in two halveswhat survives every zoom is the grammar; the ontology is meant to changedocumentcontainssectioncontainsblockcontainssentencecontainswordOne vocabularya hierarchyvery good addressing, and not the claima capabilityits own types: verb, object, reachgranted_bya deployment shapethe vendor's words: tools, scopes, settingsbounded_bya barrierenforcers, layers, partieslicensed_undera licence conditionauthority, interval, a named ownerA new ontology at every step, joined by a named edgethe claim working
The first edition of the claim said one grammar and one schema everywhere, which scores the left hand side as a pass. The corrected test asks the harder question, and the left hand side is a folder tree with very good addressing.

Applying it to this site, and not liking the answer

Run that test against the graph this site held at v0.3.0, zoom by zoom, and the result is uncomfortable.

ZoomWhat you land inVerdict
A capability into its verb, object and reachthree nodes in the same lexiconDecomposition in one vocabulary
A deployment shape into its grantgranted capability nodes, same vocabularyDecomposition
A mandate into what it authorisescapability nodesDecomposition
A reach class into what each shape says it meansnine rows, each owned by the shape that said itFractal. The first one on the site
This vocabulary into the game'sone declared bridge, partial on purposeFractal, and honest that the bridge is total today
A barrier into what enforces itthree enforcer nodes and no vocabularyOne edge deep, then it stops
A granted row into how it is knownan evidence tier and nothing behind itOne edge deep, then it stops
That is not a defect in v0.3.0. It passes the grammar half everywhere, which is the half a validator, a query engine and a provenance rule care about. It is fractal in exactly two places, and in three more it takes one step into another world and finds it empty. What a map has to add is not more nodes in the grammar: it is the worlds the existing edges already point at.

An ABP is a junction object

Here is the finding the map is built on. The four objects of an ABP are owned by four different parties who speak four different vocabularies. The grant is the vendor's published words. The evidence for it belongs to whoever observed. The barrier belongs to whoever set the control, who is often neither. The mandate is the deployer's own sentence about a job. And the licence that sits above all of it belongs to a different site entirely.

That is precisely the case Fractal Semantic Graphs exists for, so the right model is not one bigger ontology. It is nine small ones joined by named edges, with the grammar shared and nothing else.

One capability row, nine universeseach with its own owner and its own node types, sharing only the grammaru0The source bytesowned by nobodyhashed_fromu1The grammarowned by this sitegranted_byu2The deployment shapeowned by the vendor's wordsgrantsu3The grant and its evidenceowned by whoever observedbounded_byu4The enforcementowned by whoever set itauthorised_byu5The deployerowned by the deployerderived_intou6The derivationowned by the computationprojected_asu7The projectionsowned by the rendererlicensed_underu8The licence and the riskowned by riskmandate.aiWhat is sharedevery edge a verb with an inversemeaning in connectivitysupersede, never deleteprovenance on every claimWhat is notthe node typesthe verbsthe taxonomywho decides any of itNothing is merged, andnothing asks permission.Levels run up and down.Universes run across.
The walk on the site is built from the published data on every build, so the sentence it reads as cannot drift from the rows it is made of. Only one of the nine worlds belongs to this site.

Three words, and one ruling that keeps the map from collapsing

This site and the network's definition page use the word altitude for different things, and the map could not be drawn until that was settled.

WordThe ruling
AltitudeKeeps its 20 August sense here: a rendering of the same facts for a different reader. It lives inside the projections universe and is never a different world.
UniverseAdopted from the definition page's own sentence, that on one of those links you can jump into another universe. A world with its own owner, node types and verbs.
LevelPosition on the ladder only: down towards the byte, up towards the estate of agents.
Levels run up and down. Universes run across. The four objects are not a stack: the mandate is not above the grant and the delta is not below the barrier. They sit side by side and each opens into a different world. A map that stacks them is a hierarchy with the wrong shape, which is the mistake the whole exercise is trying to avoid.

The release that publishes a map and builds nothing

v0.4.0 is a brief and two corrections. It adds no data, no formula and no page beyond the brief itself and a pointer to it from the graph page.

The graph page listing where each published rule landed, with the map added as a new row
The map is reachable from the model rather than only from the docs index. The four rows above it are what v0.3.0 built; the fifth is a brief that says what the releases after it would build, one universe at a time.abp.sgit.ai at v0.4.0, captured 20 September 2026 from a checkout of the v0.4.0 tag. Unretouched.

Naming the gaps is the point of publishing a map before building it. Four of the thirteen universes are named with an owner and nothing behind them: the twin, the obligations, the runtime and the estate of agents. Named gaps get filled and unnamed ones do not.

The map · The graph rules · v0.4.0's own release record