# Governs, enforces, attests: what changed in v1.2.0, sgit.ai

> The changes to the article "Governs, enforces, attests" in v1.2.0, paragraph by paragraph.

*Source: <https://newsroom.sgit.ai/articles/versions/governs-enforces-attests/v1.2.0.html> · 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) / [Governs, enforces, attests](../../governs-enforces-attests.md) / [Versions](../governs-enforces-attests.md) / v1.2.0

# Governs, enforces, attests: what changed in v1.2.0

From v1.1.0 (2026-10-19, `4805e6671`) to v1.2.0 (2026-10-27, `db67c5ce1`), paragraph by paragraph.

0 paragraphs added, 0 removed, 4 changed in place, 38 unchanged. About 0 words added and 352 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.

[← v1.1.0](v1.1.0.md) · [all versions](../governs-enforces-attests.md)

2 unchanged paragraphs

!shot at-stack.webp | images/ | Four layers of the same stack. Atstack: the top,mandate, enforcement, the mandate: an Agent Behaviour Policy per role, saying what the role is granted, what it is for, the rules,record and how each rule is kept. Below it, enforcement at three levels: the prompt, hooks in the harness, and a third-party system that blocks, such as Ruflo's policy engine in enforce mode. Below that, the record: Ruflo's decision receipt for every action, and an sgit vault keeping memory and receipts encrypted and versioned. At the bottom, attestation: what was assured, signed, so that someone outside can verify it. The first three exist in ruv.sgit; the fourth is the attestation layer.attestation. | architecture

17 unchanged paragraphs, under In short {#in-short}, A summary, nearly right {#summary}, What an ABP does {#abp}…

!shot at-levels.webp | images/ | Three levels of enforcement for one rule of an Agent Behaviour Policy. Level 1,Policy: the prompt:prompt,the rule is in the agent's instructions; it sees everythinghooks and enforces nothing; the agent can ignore it; the evidence is the agent's own account. Level 2, hooks: small deterministic programs the harness runs before and after each action; they can block, but they sit on the agent's machine and are often editable by its account; the evidence is the hook's log. Level 3, a third-party system: a policy engine, gateway or service that does the blocking, out of the agent's reach; the evidence is that system's decision record. The recommended level for any rule that matters is the third.system. | comparison

7 unchanged paragraphs, under Where the receipt comes from {#receipt}, What is missing: a third party can check it {#missing}

!shot at-without-with.webp | images/ | The same question,question from a customer, an auditor or an insurer:insurer,wasansweredthis agent working under that policy,without and was each rule kept? Withoutwith an attestation layer: the operator sends the policy, the logs and the receipts; the third party cannot tell which version was in force, whether the receipts were edited, or which rules were only in the prompt; they take the operator's word. With an attestation layer: what was assured is signed, the policy version, the level of each rule, the receipts and the record's hash; the third party verifies the signature and reads what was and was not enforced; trust moves from the operator's word to a check.layer. | comparison

3 unchanged paragraphs, under One action, through the whole stack {#flow}

!shot at-flow.webp | images/ | One action through the stack.stack,The agent proposes a tool call. A hook checks it on the machine, as an early warning. The third-party policy engine decides allow or deny, in enforce mode, and writes a decision receipt. The receipt andfrom the agent's memorytoolgo into the sgit vault, encrypted and versioned. The attestation layer signs what was assured: the policy version, each rule's level, the receipts, the record's hash. A customer, auditor or insurer verifies the signature without accesscall to the operator'ssignedsystems.attestation a customer can verify. | concept

9 unchanged paragraphs, under Different layers, one stack {#layers}, What this does not claim {#limits}, Where this comes from {#sources}

[← v1.1.0](v1.1.0.md) · [all versions](../governs-enforces-attests.md)


---

*[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/governs-enforces-attests/v1.2.0.html)*
