graphs.sgit.ai

A reference site about one use of graphs: meaning through connectivity. A node carries no inherent meaning, and what a thing is emerges from the edges traceable from it. There are now two editions of the book that argues this. The first is finished and frozen. The second is being written from the top down, as a graph — and while its text does not exist yet, its working surface does: an interactive reader that joins a document’s extraction, its frozen bytes and its live graph, built release by release through the v0.4 era.

EditionStateWhere
The first edition
Meaning Through Connectivity		 complete · frozen at v0.3.26 Read it · one page · print PDF · its front page
The second edition
Fractal Semantic Graphs: Meaning Through Connectivity		 in construction · the working surface is live Its front page · the plan · the memos · the review packs
The universe
the second edition’s working surface		 live · the pilot document, extracted to the word The reader · the graph, standalone · 34 methods · the v0.4 retrospective
What the working surface is. One pilot document, Thinking in Graphs, carried whole and extracted twice over: a layer 1 graph of what it says (57 anchored nodes, every quote byte-verified on every build) and a core graph of what it is (every section, block, sentence and word a node with a stable identity, the markdown rebuildable from the graph byte-for-byte). Around them, an instrument: pinned summits, stable-add layouts that never scramble the mental map, path queries you write by walking, a token analysis that knows 45% of the document is padding, and a standalone graph page that fits a phone. The retrospective weighs all of it.
Why there are two, and why the first one is frozen. The first edition was written the way books usually are: prose first, structure discovered along the way, graphs added afterwards as illustration. It works, and it argues up to its thesis, which means a reader who stops at chapter three never reaches the claim the book is named after. The second edition starts at the claim and descends, so that a reader who stops at any altitude has a complete book. The first edition is not deleted or improved: it is the record of how this was worked out, including three corrections it made to itself, and it is hashed and gated so the build fails if a byte of it changes.

The sequence of events

Seventy-plus releases across three eras, which is what happens when the projection chain is gated and a release costs a commit. The history is kept whole by era: current (v0.5) · the v0.4 era (the working surface, 41 releases) · the beginnings. The turns that changed the method rather than adding to it:

ReleaseDateWhat turned
v0.2.021 August 2026the site becomes a book: chapters, one page, a PDF, and a gate that fails if the book lags its source
v0.3.021 August 2026the chapter text moves to markdown, and the chain becomes markdown to pages to book, gated at both links
v0.3.1322 August 2026reviews gain a decisions register, so what is being waited on stops being buried in threads
v0.3.1522 August 2026the altitude ladder: the book at five altitudes, and the first finding reached by compression
v0.3.2223 August 2026the decisions register is drawn as a graph, and four pieces of blocked work turn out to be two
v0.3.2423 August 2026the twenty-one source documents are carried whole, byte for byte, with their hashes
v0.3.2623 August 2026the retrospective: every correction in the run turned out to be a number nothing was checking
v0.3.2723 August 2026the plan to write the book again, from the top down
v0.4.023 August 2026the first edition moves to v1/ and freezes. The second edition begins, empty.

Generated from the release tables (all eras) on every build, so it cannot drift from them.

What else is here

Some of this belongs to the first edition and moved with it. Some belongs to the site and spans both editions.

SectionWhat it isBelongs to
The vaultsFive published graph vaults analysed in depth, plus the capability scale that only the comparison produced.the first edition
The sourcesTwenty-one documents the book was built from, carried byte for byte with their hashes.the first edition
The altitude ladderThe pilot: the book at five altitudes, its concept map, and the graph explorer. It proved the method the second edition is built on.the first edition
The reviewsFour rounds of founder review, run as a serverless pull request.the first edition
The documentsThe brief pack that produced the site, and the retrospective over the work.the first edition
The decisionsEvery open question, drawn as the peak of its own graph, answered in your own browser.both editions
The second editionEverything about making it, gathered in one tree: the dev pack, the memos, the review packs.the second edition
EngineeringThe generators, the gates, the release process.the site

Everything in the first edition

The complete index, from the file tree rather than from a list somebody maintains.

about

participant

altitudes

concepts · graph · index

book

ch-01-why-graphs-at-all · ch-02-the-five-ideas · ch-03-the-rules-you-can-apply-tomorrow · ch-04-the-edge-set · ch-05-against-schema-first · ch-06-a-graph-at-every-boundary · ch-07-worked-graphs-with-real-numbers · ch-08-whose-session-is-the-agent-using · ch-09-the-2fa-instance-graph · ch-10-article-26-5-fact-to-board-and-back · ch-11-wardley-maps-as-graphs · ch-12-what-ships-what-is-argued · ch-13-origins-2026 · ch-14-the-network · ch-15-glossary · ch-16-the-author-s-interest-and-where-this-loses · changes · wrap · index · introduction · print · single

depth

boundaries · index

docs

a-fact-in-a-vacuum · an-index-is-not-a-source · avoid-the-blob · compatibility-through-connectivity · concepts-not-words · confidence-through-evidence · digital-twins-of-anything · directed-edges-query-paths · every-paragraph-is-a-graph · fractal-risk-registers · fractal-semantic-graphs · graph-canvas-repl · graphs-of-graphs · index · issues-fs-lexicon · ontologies-of-ontologies · path-properties · paying-the-fact-creator · refactoring-meaning · the-browser-is-the-database · the-grounding-ladder · thinking-in-graphs

documents

brief · concepts · gaps · house-style · index · licensing · pack-readme · public · site-architecture · the-thesis · visual-assets · what-the-graphs-found · worked-examples

examples

2fa · article-26-5 · browser-isolation · index

glossary

index

grammar

edge-set · index

maps

index

network

index

origins

index

reviews

index · r001 · r002 · r003 · r004

shipped

index

start

index

vaults

acceptance · index · capability-scale · index · engines · index · provenance · index · index · absence · index · junction

why-graphs

index

For an agent

Start at llms.txt, which names every section hub and is gate-checked against the file tree. 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 does not exist as a book yet; everything about making it lives under /v2/ (hub: /v2/index.html), its plan is at /v2/dev-pack/, and its status is PROPOSED throughout. /book/ always points at the current edition, which is the second. Machine surfaces that span both: /decisions/data/decisions.json, /v1/docs/data/docs.json, /v1/altitudes/data/altitudes.json. Every page moved from /x/ to /v1/x/ on v0.5.16; the redirect stubs that briefly held the old addresses were retired at v0.4.7, so only the edition-prefixed addresses exist.