Colophon — Dogfooding MAGE

In a traditional colophon, I am supposed to tell you about the font. This book uses LuaLaTeX and the book class, with Source Serif 4 for body text and headings, Source Sans 3 for figure labels, and IBM Plex Mono for code. A custom house package handles the page layout, captions, and breakable insets. There, tradition satisfied.

Perhaps of greater interest, this book was also developed using MAGE. Commodity intelligences developed by OpenAI and Anthropic were used in editing the manuscript and developing its figures. What Modeling and Alignment did I apply? Important properties of the manuscript—its argument, claims, terminology, evidence relationships, and structure—were represented explicitly rather than left entirely in prose or editorial memory. Generated projections and consistency checks helped maintain correspondence as the manuscript changed. The inventory below pairs each model with the failure it was intended to prevent.

Table Colophon-1.
ModelPurposePrevented failure
Argument-spine modelThe book's numbered claims, their order, and the sections that advance themA claim advanced nowhere, duplicated across sections, or spread thinner than it is taught
Section-shape modelEach section's opening and closing graded against the editorial disciplineStructural drift — an opening that never names the failure, a closing that only restates
Concept-and-vocabulary mapOne canonical phrase for each of the book's central ideasTerminology drift — the settled structured model slipping back toward typed model
Claims modelThe load-bearing propositions, each with an audit predicate identifying prose that would contradict itAn unsupported claim, or one the later text quietly contradicts
Literature-positioning modelOne record per intervention, each carrying its established-lineage → current-frontier → narrow-move frameA citation floating loose, or the book mis-positioned against neighboring work
Substantiation ledgerEach factual number bound to the claim it backs, its source, and its limitA claim about the world with no data and no literature behind it
Flagship-case modelThe DocAble case organized into catalogue-entry packages, one row per architectural partA case-study description drifting away from the catalogue it draws on
Design tokensOne source for the faces, the accent, and the type scale, projected to every outputVisual drift between the web edition and the print edition
© James C. Davis, 2026–present