Source code is a fractal semantic graph, and a review should read every layer of it

Stories, flows, components, classes, methods and calls, the syntax tree: each layer is a graph with its own vocabulary. Naming a node and its verb is now cheap, so a change can be diffed at every altitude: a refactor moves the bottom and leaves the top still; a fix is a story holding again; the blast radius is the climb from the methods touched to the stories that can reach them. The only honest answer to AI-generated code that breaks something three packages away.

Decided by. Nobody yet: a candidate for Dinis to read, comment on and decide (keep, rewrite, merge, cut, article first, later, not doing it).

Note. The worked example is the sgit tool read as layered graphs, published as a vault with the read key on the page; the stories are hand-written and the example runs nothing. The numbers on the review burden (GitClear, DORA, Stack Overflow, Veracode) are in the article.

Where it comes from

Code review as a fractal semantic graph Source code is already the thing; Review every layer, diff every layer (newsroom)
Code review as a fractal semantic graph Method streams, again: the O2 Platform technique from 2012, one script over a syntax tree (newsroom)
Everything is connected What to bring: next to the 2018 AST chapter (article)

What it answers in the 2018 book

AST (Abstract Syntax Tree) answered written, Technologies
Threat Modeling answered outline, Security
graphs answered outline, Concepts

Where it goes

Chapter Everything is connected: graphs, part Before you start (drafting); topic Graphs, memory and your future self.

Other ideas proposed for the same chapter: A graph is a network of nodes and edges, not a diagram, The whodunit is the easiest way in: the detective's board is a graph, A map is a graph with positions; a Wardley map is a graph with context, Graphs nest, and so does the world: groups of groups are the abstraction layers we think in, You can start anywhere: it matters that you start, and get movement, The 2018 book was already there: Dot Language and AST were graphs without saying so.

Node idea:code-is-already-a-graph in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.