Fractal semantic graphs

A node means nothing on its own.
What it is arrives through its edges.

If you followed the phrase here, this is the whole of it: the same structural pattern — nodes with edges, meaning through connectivity — repeats at every level of zoom. Semantic, because meaning comes from the edges rather than from the label on the box. Fractal, because zooming into any node lands you in another semantic graph with its own node types, verbs and taxonomy, joined by a named edge to the one you left. The grammar survives every zoom. The vocabulary is meant to change.

Quoted, not paraphrased: Thinking in Graphs: Meaning Through Connectivity, section “Every Scope Defines Its Own Vocabulary”, carried whole on this site and checked byte for byte on every build. The same idea was called graphs of graphs of graphs, and ontologies of ontologies of ontologies, before it had this name. This page is the door; everything on the site is one page along.

Show me, in one graph → The five-minute version → The whole argument →

Here is a node. Give it edges.

This is the corpus’s own worked example, live. Two nodes hold the value 8080: one is connected to a type, which is constrained, which is inherited, which belongs to a released library. The other is connected to nothing. Add the edges one at a time and watch the list on the right grow. Drag a node if you want to be sure this is a graph and not a picture of one.

“The difference is not in the value.” Both scenarios hold 8080. “The difference is in the connectivity.” Every claim above is backed by a traceable path through the graph, which is the only reason the graph may make it. Read the section this comes from.

Fractal is a test, not a flourish

The test has two halves and both are worth running. If the inside has the same types and verbs as the outside, all the way down, you have a hierarchy, and a folder tree is the clean example. If the inside needs a different grammar, so that it is no longer a semantic graph, the claim is false. In between, every zoom that opens a new vocabulary joined by a named edge is the claim working.

  1. book1
  2. chapter17
  3. section165
  4. block822
  5. sentence1,782
  6. word27,002

This estate’s own making-of book at v0.2.0, taken apart six levels and put back byte-for-byte or the build fails: 160 shards, one format, one validator. That is scale invariance, and it is the honest label, because the vocabulary never changes on the way down. By the first half of the test, this ladder on its own is a hierarchy. The book says so about itself, in the chapter that states the test. Open it and zoom it yourself →

So where is the fractal part? In the vocabulary changing. The same pilot document on this site carries two graphs at once: a core graph of sections, blocks, sentences and words, and an extraction of concepts, claims, hypotheses and objections joined by verbs like departs-from and licenses. Neither is derived from the other; they share nodes by anchor. Open a word in one and you are in a lexical world, open a claim in the other and you are in an argumentative one. The chapter runs the test on this estate and reports where it fails.
The meaning of a node is supplied by the ontology at the altitude where it sits, which is why the same node means different things at different altitudes. Article 9 is a binding provision in a graph of instruments, a container of paragraphs inside the regulation, and a source of definitions to the paragraph that cites it. Same node, different edges around it at each level.
Nobody is forced to conform. An organisation, a division, a team, a person or a regulator can each define their own world in their own words and connect by drawing edges rather than by adopting a shared schema. That is the consequence of don’t merge vocabularies, bridge them: shared facts owned by nobody, formulas per party, declared bridges between them.

The fullest worked demonstration is not on this site. sgit.ai walks eleven altitudes across seven published vaults, from the text of a law to a threat on a compute instance, each rung modelled by its own author in its own vocabulary and every one openable with the read key on its page. Markdown twin for agents: index.md. Four of those rungs are now read and gated here, in the evidence estate, alongside the ladder itself.

Three ways in, depending on why you came

They are genuinely different readings, not the same page at three lengths.

just the idea

The five-minute version

Five ideas in the order that makes each one necessary, and no jargon before it is earned. You will not meet the word ontology in it.

Start here →
show me it working

The instruments

A document taken apart to the word, a book decomposed and provably rebuilt, a deterministic transformer that shows its arithmetic. All in your browser, no server.

Open something →
the whole argument

3 books, 100,955 words

The argument from first principles and from the running system; the making-of, for anyone who wants to work this way; and the frozen first edition as the record.

The shelf →

Things you can open

Each one is a working surface over real data, built for the work rather than built for this page. They are the reason there is anything to argue about.

a document, extracted

The pilot graph

One carried document, every concept a node with the quote it came from, verified byte for byte on every build. Pin summits, query by walking, ask what is padding.

Open the reader →
a book, to the word

The book as a graph

Six levels down and back: every chapter rebuilds from its own formatting graph byte-identical, or the build refuses it.

Zoom it →
20 figures

The figure graph

Every screenshot with the release tag it was photographed at, the chapter that uses it and the release it shows. Three gates: the tag exists, the figure is used, the reference resolves.

Open the viewer →
the work itself

The project board

The book’s own workstreams as a board, each pack moving through seven stages, with the agents’ open issues read straight from their folders.

Open the board →
how a change moves

The state map

Nine states in four lanes, each naming who owns it, what it costs and whether the door out of it swings both ways. A gate fails the build if the drawing and the pipeline disagree.

Follow a change →
seven roles

The issue tree

Every role’s open, blocked and done work. The folder is the status, a status change is a git mv, and a role may read another’s issues but never write into them.

Open the tree →
what changed

The version diff

Two versions of the book side by side, chapter by chapter, computed from the release tags rather than from a changelog somebody remembered to write.

Compare versions →
no model, no weights

The WCLM

A deterministic transformer over these graphs: twelve operators, each in its own folder, computing a meaning and showing every step of the arithmetic.

Run it →
four more vaults

The evidence estate

Four published graph vaults, read from the pages that publish them because this estate cannot decrypt one. Every fact carries the sentence it came from, and the build fails if that sentence has moved.

Read the estate →
35 techniques

The methods register

Every technique in use here, named, dated to the release that introduced it, and pointed at the code that implements it.

Read the register →

What this is not

The corpus’s own caveats, which travel with its ideas.

It is not a graph database pitch. The claim is that one grammar is the interface at every boundary, not that things are stored in a graph. There is no graph database, no SPARQL and no RDF behind this site. The chapter that separates what ships from what is argued is What ships, what is argued.
Nine of the edge inverses are proposals, not quotations. They are this site’s own suggestions rather than anything the corpus says, and they are marked as such everywhere they appear.
The books are under review, and say so. A book below v1.0.0 is openly unfinished; v1.0.0 is reserved for a book’s actual final release, and a gate enforces that in both directions.
280 pages 123 narrated releases 34 founder memos, verbatim 21 carried source documents 35 named techniques 153 tests 72 validator conditions

Every number on this page is counted from the repository at build time, and every quotation is checked against its source. The machine-readable form is at home/data/home.json.
Everything on this site is one page along: the shelf, the sequence of events, what each section is, and the complete index.

For an agent

Start at llms.txt, which names every section hub and is gate-checked against the file tree; llms-full.txt is the whole document set in one fetch. This page’s own data, including the definition above with its anchor, is at /home/data/home.json. The estate index is at /site/. The first edition is everything under /v1/ and is frozen at v0.3.26: its bytes are recorded in /v1/MANIFEST.json with SHA-256 per file, and the build fails if any of them changes. The second edition lives under /v2/ (hub: /v2/index.html). /book/ always points at the current edition. Machine surfaces that span both: /decisions/data/decisions.json, /v1/docs/data/docs.json, /v1/altitudes/data/altitudes.json.