graphs.sgit.ai › everything on this site

Everything on this site

This page was the front page until v0.6.20, and it is here unchanged in substance, because the archive was never the problem: being the first thing a stranger met was. The front door now answers the question people arrive with. This is the whole estate, listed and indexed.

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. That argument is now made by three books, written from this repository and published from it. The first edition is finished and frozen. The second argues the same claim from first principles and from the running system it describes — a system you can open on this site and use. The third is the making-of, for anyone who wants to work this way themselves.

Every book here is markdown first: the pages render their own source in your browser, so a page cannot drift from the file it claims to show. Each book carries its own version, which moves only when that book’s content moves, while the site’s version moves on every push. The shelf holds all three.

BookVersion and stateWhere
Fractal Semantic Graphs: Meaning Through Connectivity
The argument whole: from first principles, and from the running system.		 v0.2.0 · under review
18 chapters · 38,029 words · 119pp		 Read it · about this book · PDF · book.json
Creating a Book Using Agentic Workflows
The making-of: how this book was written with agents, and how to do it.		 v0.2.0 · under review
17 chapters · 31,435 words · 92pp		 Read it · about this book · PDF · book.json
The Universe Volume for Fractal Semantic Graphs
The reference atlas for the method. Held back from this release.		 v0.1.0 · held
12 chapters · 30,696 words · 91pp		 Read it · PDF · book.json
Meaning Through Connectivity
The first edition. Kept as the record of how this was worked out.		 complete · frozen at v0.3.26
hashed and gated: the build fails if a byte changes		 Read it · one page · print PDF · its front page

A book below v1.0.0 is openly still under review; v1.0.0 is reserved for a book’s actual final release. The rule, and the gate that enforces it in both directions, are on the shelf.

The books are not the only thing here. They were written from a working surface you can open. One pilot document, Thinking in Graphs, is carried whole and extracted twice over: a 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, 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 beside it the WCLM, a deterministic transformer that computes a meaning and shows its arithmetic. The techniques are named and catalogued in the methods register.
Why there is a second edition, 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.
What this site does not claim. It is not a graph database pitch, and the books say so in their own words. The semantic layer described here is designed, not shipped; the chapter that separates the two is What ships, what is argued. Nine of the edge inverses in the verbs register are this site’s proposals rather than quotations from the corpus, and are marked as such where they appear.

The sequence of events

121 narrated releases across three eras, which is what happens when the projection chain is gated and a release costs a commit. Every one of them is narrated: not a commit log, but a paragraph a reader can understand without opening the diff. The history is kept whole by era: current (v0.6, review as change control) · the v0.5 era (the books, 24 releases) · the v0.4 era (the working surface, 41 releases) · the beginnings. Each closed era is also weighed in a retrospective — what compounded, what was got wrong, and how each mistake was found: v0.5, the books · v0.4, the working surface. 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.
v0.4.3726 August 2026the core graph: a document taken apart to the word and put back byte-identical
v0.5.1827 August 2026each book gets its own version, independent of the site's
v0.6.2019 September 2026the front page splits in two: a door for a stranger, and this page for everything

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 teamSeven roles, one folder each, every one naming what it refuses. Their work plan is the issue tree and their pipeline is the state map.the second edition
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. Everything about the second edition lives under /v2/ (hub: /v2/index.html), its plan is at /v2/dev-pack/. /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. The front door’s own data is at /home/data/home.json. Every page moved from /x/ to /v1/x/ at v0.4.0; the redirect stubs that briefly held the old addresses were retired at v0.4.7, so only the edition-prefixed addresses exist.