Home / Articles / A policy beside the prompt / Versions / v1.6.0
A policy beside the prompt: what changed in v1.6.0
From v1.5.0 (2026-10-19, d303ce0f1) to v1.6.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 4 changed in place, 64 unchanged. About 0 words added and 200 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 pp-inputs.webp | images/ | What an agent is given,given today in two modesmodes, and as proposed. Over the API we write the whole system prompt, so our behaviour policy goes inside it; in the Claude apps and Claude Code the vendor's system prompt comes first and our policy goes into what we add. In both, it is text the model is asked to keep, in the same channel as every email and page it reads, and the vendor's checks are its own. Proposed:proposed: the policy as a separate, versioned input, layered over the vendor's own published policy, checked outside the model where it can be.input. | diagram
22 unchanged paragraphs, under In short {#in-short}, The idea: a policy beside the prompt {#idea}, The old problem: code and data in one channel {#code-and-data}…
!shot pp-aviation.webp | images/ | Fatal airliner accidents,accidents in 1995 and 2025.2025, Atand what 1995's rate of 2.72 per million flights, 2025's 38.7 million flights would have produced about 105 fatal accidents. There were 12. Rates from the Aviation Safety Network via Our World in Data; 2025 accidents from the Flight Safety Foundation's report of the ASN data; flights from IATA.2025. | comparison
3 unchanged paragraphs, under Payments got safe because liability moved {#payments}
!shot pp-payments.webp | images/ | Where the liability for payment fraud was moved, and what followed. Each step put the loss on the party best placed to stop it, and the security followed theat loss:each caps for consumers, a liability shift onto whoever had not adopted chip cards, standards written by the card brands, and reimbursement of scam victims.step. | timeline
10 unchanged paragraphs, under Regulation alone does not do it {#regulation}, The user answers outside the policy, the vendor inside it {#inside}
!shot pp-split.webp | images/ | The proposed split.split Thebetween vendorthe publishes its ownvendor's built-in policy, the deployer's policy and accepts the deployer's; for every row it accepts, it says what enforces it and answers if it breaks. Everything the policy does not cover stays with the user, as it does today. The vendors that keep more rows as boundaries can sell that as the product.user. | decision
27 unchanged paragraphs, under Where the policy goes today, in each mode {#modes}, A system prompt is a light behaviour policy {#system-prompt}, Most agents already run a policy {#already}…