Home / Articles / Hooks are kernel code / Versions / v1.4.0
Hooks are kernel code: what changed in v1.4.0
From v1.3.0 (2026-10-18, de821285d) to v1.4.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 3 changed in place, 55 unchanged. About 0 words added and 139 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
2 unchanged paragraphs
!shot hk-first10.webp | images/ | The first ten hooks.hooks: Threethree this session runs, five tested in a sandbox,sandbox and two proposed: a hook that checks the other hooks, and an agent hook that reviews a push on the most capable model, read-only and without network. Between 4 and 26 lines of code each, and every one runs on every matching action, with the user's permissions.proposed. | comparison
22 unchanged paragraphs, under In short {#in-short}, Kernel code {#kernel}, A good case study {#case-study}…
!shot hk-maturity.webp | images/ | A maturity model for hooks: five levels of how a rule is kept, from the prompt to off the machine, and three questions for every hook at every level: its power, the legs of the lethal trifecta it touches, and its sandbox. The less deterministic a hook is, the less it should be able to reach.hook. | architecture
13 unchanged paragraphs, under Where hooks run {#where}, A site and a feed {#site}
!shot hk-site.webp | images/ | A hooks site and feed, run like a kernel tree.tree: Every hook starts as an intent,how a row of a behaviour policy, andhook is published with its graph, tests, version and signature.what Thethe feed lists every hook with its level, power, trifecta legs, version and hash; the change blast radius view climbs from a change to the intents and sessions it affects; installs are free and can run inside an organisation with no call home; paying buys state.lists. | architecture
18 unchanged paragraphs, under Pay for state, never to run {#billing}, The brief {#brief}, What this does not claim {#limits}…