What changed between versions
Pick two versions of Creating a Book Using Agentic Workflows and read the delta the way a code review reads a diff: chapter by chapter, block by block, and word by word inside a changed block. 2 version(s) so far, each extracted from the release tag that carried it.
This is the text half, and it is labelled as the half deliberately. Brief 45 asks to read the changes between two versions of the book, and sets the bar higher than this page reaches: “eventually should be a diff created from the graphs… you should be delting the diffs of the graphs, not of the markdown. That would be the really test measurement of our success here.” A graph diff can tell a reworded sentence from a replaced one and report a moved section as a move; this page cannot. It needs a graph stored per book version and only the current version has one. Tracked as an open issue and WS-04 on the board.
Two clocks. The picker offers book versions, not site releases: the site has moved 120 times and the book twice. Each snapshot names the release that carried it. The units are the chapter markdown, not the rendered pages, so a change to a template cannot show up here as a change to the book.
Two clocks. The picker offers book versions, not site releases: the site has moved 120 times and the book twice. Each snapshot names the release that carried it. The units are the chapter markdown, not the rendered pages, so a change to a template cannot show up here as a change to the book.
Loading the version index…
For an agent
changes/data/index.json lists the book versions with the site release and date of each; one file per version holds the chapters as flat text blocks extracted from that version's tag. Extraction from a tag is deterministic, so a version's file never changes once its tag exists and each book release adds exactly one file. The diffing runs client-side in assets/changes.js.