Home / Articles / Hooks are kernel code / Versions / v1.1.0
Hooks are kernel code: what changed in v1.1.0
From v1.0.0 (2026-10-14, dad31e35f) to v1.1.0 (2026-10-14, 1f0b50266), paragraph by paragraph.
1 paragraph added, 0 removed, 1 changed in place, 57 unchanged. About 25 words added and 0 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
17 unchanged paragraphs, under In short {#in-short}, Kernel code {#kernel}, The best case study we have {#case-study}
They are also the best case study I can think of for the way we want to do code review. The work on code review as a fractal semantic graph, which started onat sgit.ai,secrets.sgit.ai in its review graphs, draws a change from the method it touched up to the stories that can reach it. On a large codebase that graph is big. A hook can be five lines. The whole graph, from the intent it serves to every line it runs and everything it calls, fits on one page, so we can do all of it, completely, and show it working.
37 unchanged paragraphs, under Hooks of hooks {#fractal}, A maturity model {#maturity}, Where hooks run {#where}…
• Corrected on 14 October. The first version said the review work started on sgit.ai; it started at secrets.sgit.ai, now linked.
3 unchanged paragraphs, under Where this comes from {#sources}