**A fourth research delivery, and the first that validated against the schema without a single
error.** `chatgpt-2026-09-18-politicas-delta` — one source, one item, two claims, both found word for
word in the bytes this newsroom froze. The editor of record approved the item; the article is
commissioned and not written; nothing from the delivery is on a reader page.

**One source, readable at the first attempt.** `src-pol-13`, an official digitalGOV page dated 17
September 2026, HTTP 200, 306 214 bytes and **10 345 visible characters**, with its SHA-256 in the
register. No 403, no script-rendered wall, no 404. That is the first time in this section: the four
policy stories already published are all built on the opposite experience, and three of them are
partly *about* it.

**Both claims confirmed, and the excerpt gate was checked against by hand rather than trusted.**
*"O Cloud and AI Development Act é uma proposta da Comissão Europeia"* and *"Prevê igualmente um
quadro comum de contratação pública"* are both in the frozen bytes verbatim. A first hand-check
reported the opening excerpt as absent; that was this session's own bug — ` ` was unescaped
*after* whitespace was collapsed, so the entities survived as literal text and the match failed. Done
in the right order, both confirm. The gate was right, and the note is here because a verifier that
cannot be wrong is not verifying anything.

**Nowhere did the delivery's own account and the check disagree** — which had not happened before.
The 14 September delivery claimed in its notes that it had *"confirmado o instrumento jurídico da
ANIA"* while the check said the page returns no text. This one says the European Commission's primary
page returned **HTTP 429** and that it therefore did not use it as a source. That is the right call
and it is recorded rather than worked around: if that page is ever frozen it is a new source and a
new excerpt, not a retroactive confirmation of this one.

**Zero schema errors and no ontology change.** The one proposed entity is
`politica:cloud-and-ai-development-act`, type `Política` — already in the ontology, with an
identifier matching the published pattern. No vocabulary proposal, so no version to take for it. The
six schema errors still printed by the delivery step belong to the 14 September delivery and are
unchanged.

**Three things ride in the record without being claims, and that is worth naming.** The acronym
`CADA`, the procedure `2026/0138(COD)` and the 3 June 2026 presentation date travel as `attributes`
and `dates`, not as `claims` — so the excerpt gate never looked at them. All three were checked by
hand against the same frozen copy and all three ARE in the bytes. They are sound, but they satisfy
rule 2 by accident rather than by construction, and `redacao/issues/014` says that if any of them
reaches the prose it becomes a claim with its own excerpt first.

**One inference is named and excluded.** The delivery's `why_it_matters` says the proposed framework
articulates *"com a execução do Plano Nacional de Nuvem Soberana"*. "Nuvem Soberana" appears on that
page only as a tag; the articulation is ours, not the source's. It is the kind of sentence that passes
unnoticed because it is plausible, so it is written down in the issue and in the commission to
Reporting as something that does not reach the page.

**The thing this article has to get right is that CADA is a proposal and not an act.** Every policy
story on this site so far is an announcement whose instrument could not be read. This one is a text
that declares itself a proposal, in the ordinary legislative procedure, with Parliament and Council
still to come. Promoting it to an instrument in force would be exactly the error the section exists
not to make.

**The valuable negative.** A second independent search again failed to find the readable Série I PDF
of RCM 2/2026 and any published act designating Portugal's market surveillance or notifying authority
under the AI Regulation. Two assistants, two dates, same wall. That is evidence for
`redacao/issues/006` and `redacao/issues/002` and it is not a story.

**Gate 41 caught this release's own mistake.** The commission to Reporting quoted a literal source
mark, and the back office may not carry one — it reports on the newsroom, not on the world. The
message names the identifier and leaves the mark to the issue. A rule with a gate is the only kind
that holds.

**What is deliberately NOT done here.** `redacao/revisoes/chatgpt-2026-09-18-politicas-delta.json`
does not exist. The approval was given by the editor in conversation; the file is the editor's line,
it says so in its own text — *"é escrito por uma pessoa … Uma execução automática nunca escreve
aqui"* — and `Edit(redacao/revisoes/*)` is deny-listed. Writing it through another tool would be the
same act renamed. So `build/entregas.py` keeps the delivery at `por_rever` and gate 13 keeps
`item-pol-12` quarantined, which is the correct and safe state. The JSON is written out ready to
paste, and the delivery, the frozen source, the verification record, the issue and the commission are
all on the register and dated in the meantime.

921 pages, four languages, 44 gates green, browser gate unchanged.