# Behaviour policies from the checks: what changed in v1.1.0, sgit.ai > The changes to the article "Behaviour policies from the checks" in v1.1.0, paragraph by paragraph. *Source: · sgit.ai v0.7.87 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.* --- [Home](../../../index.md) / [Articles](../../index.md) / [Behaviour policies from the checks](../../behaviour-policies-from-the-checks.md) / [Versions](../behaviour-policies-from-the-checks.md) / v1.1.0 # Behaviour policies from the checks: what changed in v1.1.0 From v1.0.0 (2026-10-21, `69e244a3c`) to v1.1.0 (2026-10-27, `db67c5ce1`), paragraph by paragraph. 0 paragraphs added, 0 removed, 4 changed in place, 65 unchanged. About 0 words added and 131 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names. [all versions](../behaviour-policies-from-the-checks.md) 2 unchanged paragraphs !shot bv-graph.webp | images/ | 57 checks, 8 behaviours: the site inat the centre, the eight behaviours around it, sized by their checks, and each check as a dot coloured by what keeps it today: one boundary, 34 settings and 22 expectations.it. | concept 12 unchanged paragraphs, under In short {#in-short}, Why take the checks apart {#why}, The method: up the graph and back down {#method} !shot bv-chains.webp | images/ | Two checks taken apart the same way.way:The em-dash: nothe em-dash in prose; many readers find it off-putting; the house voice; run by sgit.ai's validator in my buildrule and the leak scan; kept only because I run them. The key tripwire:tripwire,nothing looks like a vault key; a published key opens a vault for ever; never publish a secret; CI blocksfrom the deploy;rulekepttobywhatakeepsfileeachmy own push can change.one. | concept 11 unchanged paragraphs, under The eight behaviours {#behaviours}, Where each behaviour is kept {#where} !shot bv-where.webp | images/ | The checks for each behaviour by where they run: CI that blocks the deploy,blocks, CI that only reports, the local build, the session, and the container or hooks. The house voice and the agents' mandate have no check in CI; the reader's data is checked in CI, but a failure does not stop the deploy. | comparison 28 unchanged paragraphs, under Only one boundary {#boundary}, Every check, by behaviour {#all}, What to change {#target} !shot bv-target.webp | images/ | Where each behaviour should be kept: each behaviour's checks moved into this site's validator and CI where they can run on the repository, the tests required once decoupled from live services,CI, the mandate kept in grants and hooks; and the checks protected, so a change to them needs a person's review.hooks. | concept 12 unchanged paragraphs, under What this does not claim {#limits}, Where this comes from {#sources} [all versions](../behaviour-policies-from-the-checks.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/behaviour-policies-from-the-checks/v1.1.0.html)*