# Process behaviour policies: what changed in v1.1.0, sgit.ai > The changes to the article "Process behaviour policies" 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) / [Process behaviour policies](../../process-behaviour-policies.md) / [Versions](../process-behaviour-policies.md) / v1.1.0 # Process behaviour policies: what changed in v1.1.0 From v1.0.0 (2026-10-24, `125add183`) to v1.1.0 (2026-10-27, `db67c5ce1`), paragraph by paragraph. 0 paragraphs added, 0 removed, 4 changed in place, 63 unchanged. About 0 words added and 201 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names. [all versions](../process-behaviour-policies.md) 2 unchanged paragraphs !shot px-walls.webp | images/ | Seven walls around one process, set from its policy and enforced by Linux inside this cloud container: an ephemeral user with no capabilities; an empty, read-only root holding only the listed files; its own namespaces; Landlock for paths, exec and TCP ports; a seccomp allowlist of the system calls the traced run made; a network broker that only opens tunnels to the policy's hosts; and cgroup limits.container. | concept 34 unchanged paragraphs, under In short {#in-short}, Why a process {#why}, The question, made concrete {#question}… !shot px-probe.webp | images/ | What the probe tried, and what stopped it: as root in the container today, it could read /etc/shadow and the agent's home, write to /usr/lib and /tmp, see 92 processes, start a shell, mount a filesystem, make a user namespace, reach the internet and the agent's proxy, and open a netlink socket;root, under the Hello World policy, all of it was refused;and with seccomptwoand Landlockwalls switched off, the other walls still refused all but the netlink socket.off. | comparison 11 unchanged paragraphs, under sgit, under its own policy {#sgit}, What it costs {#cost} !shot px-cost.webp | images/ | The size of a policy,policy and what it costs:costs, for four programs from Hello World in C,C1 file, 12 system calls, no hosts, 5 ms bare, 103 ms of policy overhead; Hello World in Python, 37 files, 34 system calls, 30 ms bare, 92 ms overhead; Python fetching one page, 169 files, 44 system calls, one host, 565 ms bare, 149 ms overhead;to sgit init, commit and status, 1,025 files, 58 system calls, one host, 3,495 ms bare, 187 ms overhead.status. | comparison 3 unchanged paragraphs, under A policy of policies {#policy-of-policies} !shot px-layers.webp | images/ | A policy of policies: the operating systemsystem,(whatenvironment,Linuxruntime,can do here), the environment (this container's proxy, CA bundleapplication and paths), the runtime (Python and its standard library), the application (sgit, its dependencies and its server), and this execution (one command, one folder, one host, one user for one run),execution, each narrowing the one above. | concept 13 unchanged paragraphs, under The size of the policy measures the software {#measure}, What this does not claim {#limits}, Where this comes from {#sources} [all versions](../process-behaviour-policies.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/process-behaviour-policies/v1.1.0.html)*