Creating a Book Using Fractal Semantic Graphs
The true story of how the second edition of Fractal Semantic Graphs: Meaning Through Connectivity is being built: one person talking into a phone, a set of AI agents, and eighty-eight tagged releases in six days. Written for authors who want to work this way, not for graph specialists. Every scene in it is checkable at the git tag its caption names.
What it is
An expansion of the v0.4 retrospective into a full book, carried through the v0.5 era, and aimed at a different reader: not a graph specialist, but somebody with a book in them and an AI agent at hand. It is the third of three books commissioned from this estate, and the only one about the making rather than the material.
The promise: here is a working loop for writing a book with agents, demonstrated end to end on a real one, failures included. Every claim is checkable in the repository it describes, which is the loop's whole point.
The book
| # | Chapter | What it gives you | Raw |
|---|---|---|---|
| 00 | Creating a Book Using Fractal Semantic Graphs | What the book is, who it is for, what you will know at the end, how to check any claim in it, and the AI-authorship disclosure. | .md |
| 01 | 1 · The loop | Voice memo, verbatim brief, build, release, live review, usually inside an hour. The four numbers that tell you whether the loop is running. | .md |
| 02 | 2 · The first book, and the pivot that saved the second | A book written in three days, and then the memo that cancelled the plan for the second one: build the universe first, find the plot afterwards. | .md |
| 03 | 3 · Briefs as the contract | Why the raw transcript goes above the tidy summary rather than instead of it, and the three-part shape every brief in this corpus has. | .md |
| 04 | 4 · Gates buy speed | Why automated checks make an agentic project faster. The seven checks to start with, the unit suite from 13 tests to 84, and the release note as a gate. | .md |
| 05 | 5 · From a page to an instrument | Five screenshots from five points in history, and the design law underneath them: every node move costs the viewer their mental picture. | .md |
| 06 | 6 · Two agents, one repository | Two Claude sessions, one repository, three merge commits. The four-note exchange, the bug neither could see alone, and the four rules that held. | .md |
| 07 | 7 · The failures, lovingly | Nine failures with the cost attached: the iPad round, the wire that jumped a layer, the negation that was not there, and the hour lost to a zombie browser. | .md |
| 08 | 8 · Reviewing out loud | Ten screenshots and three and a half minutes of talking produced six findings. And the inversion that followed: pages that broadcast their own state. | .md |
| 09 | 9 · The experiments | A crazy experiment from voice memo to tested, folder-structured subsystem in eight releases across one afternoon, with its exit named before it started. | .md |
| 10 | 10 · The founder's craft | Five habits from a person who steered eleven build rounds in six days without writing a line of code, and the five things he did not do. | .md |
| 11 | 11 · The playbook | The chapter that stands alone. What to set up on day zero, what to say in your first memo, what to expect to go wrong, and the honest costs. | .md |
| 12 | 12 · What it costs, and where it loses | What the six days did not produce, the costs nobody mentions, and four situations where this method is the wrong one. | .md |
| 13 | Appendix A · One brief, annotated | One complete brief, verbatim, annotated segment by segment, with the release it produced thirty-three minutes later. | .md |
| 14 | Appendix B · The chronology | All eighty-eight releases in order, by day, with timestamps and the opening of each release note. | .md |
| 15 | Appendix C · The harness | The scripts: time travel by git tag, the screenshot harness and its port rule, and every command that produced a number in this book. | .md |
| 16 | Colophon | How the book was made, what was cut, what remains open, and the honesty positions carried from the corpus. | .md |
How to check any of it
The repository carries a git tag for every one of the eighty-eight releases. Every figure in this book was taken by checking out the tag its caption names into a temporary worktree, serving it, and photographing the page as it actually was. None is a reconstruction, and any of them can be re-taken with the two scripts in Appendix C. Every number was computed from the repository rather than recalled, and the commands are in the same appendix. Every founder quotation is verbatim and was already published at the memos hub before this book was started.
The twenty figures
Each one re-taken from the tag in its caption. In the order they appear in the book.
