# The book-writing pack — three books from this estate **Status:** COMMISSIONED — one pack, three entry points, three fresh sessions **Date:** 26 August 2026 ## The commission, verbatim > Great work , now for something a little bit different, can you write a brief to write > three books/pdf created from this repo and the work we have done so far (I have a long > flight tomorrow and will use it to read these) > > - on a new Claude code session > - taking into account the 1st book, the 21 referenced docs , the fractal examples in > this repo + the others added to https://sgit.ai/demos/vaults/index.html , the multiple > *.sgit.ai sites we have been creating (in other Claude sessions) > https://sgit.ai/network/index.html and very importantly the work and workflows from > the 2nd book , namely the universe work (which really shows a lot of the practices and > ideas in action) > - using the title: “Fractal Semantic Graphs: Meaning Through Connectivity” > - (apart from the title which is locked) have full editorial freedom on the books > content and structure > > Create these books/webpage/pdf > > 1) the universe for the “Fractal Semantic Graphs: Meaning Through Connectivity” > 2) the “Fractal Semantic Graphs: Meaning Through Connectivity” book > 3) a new book focused on “Creating a book using Fractal Semantic Graphs” (which > basically tells the story so far of how we have been doing on book 2 , namely all the > experimentations, discoveries, MVPs / Pocs (with screenshots of the evolution), the > use of Claude and our agentic workflow …. Basically an expansion of that great > analysis that you did on the v0.4.x versions . This book is aimed at other authors > that want to use similar agentic workflows to write their own books > > Basically what I need you to do is to create a book writing pack (same style as the dev > packs) so that I can create 3 different Claude code sessions (one per book) and say: > read this initial prompt (which should contain instructions for everything that needs > to be read). Make this one pack with 3 entry points, since most should be very similar > between the briefs to each agent ## How to use this pack Open three fresh Claude Code sessions on this repository, one per book. Each book has a HOME FOLDER under `v2/books/` whose README is the complete initial prompt, so starting a session is one line: **"hi, you are going to focus on writing this book: `v2/books//README.md`"**. | Book | Home folder | Charter in this pack | Deliverable | |---|---|---|---| | A — the Universe volume | `v2/books/fsg-universe/` | `03__entry-a-the-universe.md` | the atlas: the concept graph of Fractal Semantic Graphs, as a readable book | | B — the book itself | `v2/books/fsg/` | `04__entry-b-the-book.md` | *Fractal Semantic Graphs: Meaning Through Connectivity* | | C — the making-of | `v2/books/making-a-book/` | `05__entry-c-the-making-of.md` | *Creating a Book Using Fractal Semantic Graphs* | The founder has answered the pack's two held questions: book B does NOT wait for book A, and the finished books DO ship on the site — each writing session releases its own book to `dev` through the full release ritual once it is complete. Every entry prompt tells its session to read, in order: this README, `01__the-corpus.md` (what to read and where it lives), `02__shared-conventions.md` (the rules all three books share), and then its own entry file. The three sessions share the first three files completely; only the entry file differs. That is the pack's design: the corpus and the rules are said once, the editorial charters diverge. ## The three governing rules 1. **The title is locked; everything else is editorial freedom.** Books A and B carry *Fractal Semantic Graphs: Meaning Through Connectivity* (A as the companion volume to that title, B as the book itself). Book C is *Creating a Book Using Fractal Semantic Graphs*. Structure, voice, chapter count, figures — the writing agent's call, made confidently and recorded in the book's own front matter. 2. **Every claim is anchored or it is not made.** This estate's own discipline applies to its books: a position attributed to the corpus carries its source (a chapter, a brief, a page, a release note); a number is computed or quoted, never remembered; a screenshot is taken from the real page, never described from imagination. The corpus's own honesty lines survive verbatim — above all "not a graph database pitch". 3. **The reader is on a plane.** No live demo can be the argument. Each book must land as ONE self-contained PDF that reads start to finish offline, with the web version as its companion, not its crutch. Substantial but finishable: aim for a 60–120 page PDF, and say in the front matter what the reader will know at the end that they did not know at the start. ## What already exists that these books stand on The estate is live at graphs.sgit.ai (v0.5.9 at the time of this pack): the frozen first edition, the second edition's working surface (the universe reader, the core graph, the identity ledger, the file explorers), the WCLM with its twelve operators in folders, the 38 briefs, the registers (methods, senses, analogies, meaning packs), the v0.4 retrospective, and a release history whose every row narrates what happened. Book A compresses the ideas into a graph you can hold; book B argues them; book C tells how they were built. Same corpus, three projections — which is itself the thesis.