The second edition
Fractal Semantic Graphs: Meaning Through Connectivity · for humans and agents. Being written from the top down, as a graph: the universe of concepts, claims and evidence first, the plot lines through it next, the spine derived from where they converge, and only then the prose. It does not exist as a book yet. What exists is the plan, the memos that shaped it, the review packs for the people and agents who will check the work, and the rule this tree enforces.
/v2/: the plan, the founder's memos, the review packs, and, as they arrive, the project management, the universe and the book's own graph. When the edition needs material from the first, it takes its own copy in here with a provenance block naming where it came from. Anything outside /v1/ and /v2/ is the site's own chrome and spans editions; nothing an edition depends on lives out there. One day this tree freezes the way /v1/ did, and a /v3/ begins.What is in this tree today
| What | Where | State |
|---|---|---|
| The dev pack — the plan: ten files, seven phases, the ADRs, the open questions | /v2/dev-pack/ | PROPOSED throughout |
| The memos — the founder's voice, verbatim, with every instruction mapped | /v2/memos/ · raw at /v2/briefs/ | source material, not edited |
| The review packs — documents a reviewer can answer with no link followed | /v2/packs/ | first pack shipped at v0.4.3 |
| The universe, layer 1 — per-document local graphs, every node anchored to the frozen bytes | /v2/universe/ | pilot extracted at v0.4.5: 1 of 21 sources |
| The lexicon — the vocabulary as scopes that may extend, specialise or override one another | /v2/lexicon/ | 27 book terms, 1 override on record |
| The methods register — every graph technique this project has used in earnest, as book source material | /v2/methods/ | 20 techniques registered |
| The artefact catalogue — point-in-time pages and PDFs preserved byte for byte, hash-gated | /v2/artefacts/ | the first pack, as built at v0.4.3 |
What happens next
The universe is being built bottom up, one carried source document at a time: each of the twenty-one documents at /v1/docs/ gets its own local graph — its concepts with the document's own definitions, its claims with their evidence state, every node anchored to the section and characters that carry it. The sources are byte-frozen behind a hash gate, so an anchor into one is stable forever and the build can verify every quoted extraction against the frozen bytes. A bridge layer then records, as authored decisions, where documents name the same idea differently and where they disagree. The book's universe connects to those nodes; it does not absorb them. The pilot, on the cornerstone document, shipped at v0.4.5; the founder reviews the method on it before it is applied twenty more times.
Where the first edition is
Complete, frozen at v0.3.26, and readable at /v1/book/ with its own front page explaining how it happened. Its bytes are recorded in /v1/MANIFEST.json and the build fails if any of them changes. It was never published beyond this site; it is kept intact as the record, the source material, and the worked example of the method the second edition industrialises.
For an agent
This tree is the second edition's own; nothing in it is book text yet. The plan is under /v2/dev-pack/ (raw markdown under /v2/dev-packs/), the founder's memos are raw under /v2/briefs/, and the review packs' machine index is /v2/packs/packs.json, the universe is /v2/universe/data/universe.json, the lexicon is /v2/lexicon/data/lexicon.json, the methods register is /v2/methods/data/methods.json and the artefact catalogue is /v2/artefacts/data/catalog.json. If you are reviewing, take a pack and read nothing else. Do not cite this tree as the book: the book is the first edition at /v1/book/ until the second exists, and /book/ always points at the current one.