Home / Articles / Are hooks the sweet spot? Moving an agent's rules from hope into hooks, rule by rule, until enforcement moves off the machine / Versions / v1.1.0
Are hooks the sweet spot? Moving an agent's rules from hope into hooks, rule by rule, until enforcement moves off the machine: what changed in v1.1.0
From v1.0.0 (2026-10-14, 2d0143c83) to v1.1.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 2 changed in place, 49 unchanged. About 0 words added and 71 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 hs-rules.webp | images/ | The eleven rules of this site's writing session, rule by rule. Today one rule is kept by a hook, one in part by a disabled push URL,rule, and thehow rest by the agent's good behaviour. Moved intowell hooks andcould testedkeep on fixed inputs in a throwaway repository: four fully, two mostly, three partly, two not at all.each. | comparison
24 unchanged paragraphs, under In short {#in-short}, The question {#question}, This session's own policy {#own}…
!shot hs-layers.webp | images/ | Where a rule can be kept.kept, Fromfrom the prompt,prompt which sees everything and enforces nothing, through agent hooks and the tools' own hooks,down to the sandbox, a gateway off the machine, and the service itself.itself, Eachwith each layer down is harder for the agent to change and sees less of what the agent meant to do.change. | architecture
23 unchanged paragraphs, under Chained, not ordered {#chained}, Who else is doing this {#who}, A hook pack generated from a policy {#pack}…