**An article becomes a dated folder.** `artigos/<yyyy>/<mm>/<dd>/<slug>/` with four files: the
prose, the verification record for each claim, the provenance — which run by which agent
produced it, in what order — and the JSON saying what the article is. A folder and not a file
because an article is not only the text: it is the text plus the bytes it stands on plus whoever
re-read them plus whoever wrote it, and in a single file three of those four end up elsewhere
and stop agreeing.

The date in the path is the date of the **material**, not of publication. Six folders opened:
three with prose and verification done, three gathering material for the stories §11 of the
brief commissioned. None published — that line is the editor of record's. `dados/historias.json`
becomes DERIVED from the folders, as the organisations are derived from the speaker cards.

**Each of the eight sections gains a folder and an editorial record.**
`seccoes/<id>/seccao.json` says what the section covers, what it can and what it CANNOT claim
today, which sources it has frozen and which did not resolve, and which questions are open. The
two sections with not one frozen source are forced by gate 20 to answer «Nada.» to the question
of what they can claim.

**A back office, in English.** `/backoffice/`: the operations console with the pipeline's state,
who may write where, the board, the articles, each section's coverage, the runs and the commits
— and a reader for this repository's 32 markdown documents, reading them from their own bytes
rather than a copy. It is in English by the editor's decision, and the condition of that
exception is checked: gate 19 fails the build if a back-office page cites a frozen source as
evidence. The console reports the newsroom, never the world.

**Five new gates, in a separate file.** `build/gates_artigos.py` exists apart because
`build/gates.py` is in the deny list of `.claude/settings.json`: an agent that can edit the gate
that stops it has no gate at all, and the wrong way to add checks would be to lift that
protection. All five were injection-tested, like the others.

**Two rendering defects fixed, and both are worth naming:** the markdown renderer made every
LINE a paragraph, which broke prose mid-sentence and left a `**bold**` crossing the break
without closing; and article prose had no vertical rhythm at all because `.std` has zero margin
— right on the front page, where the spacing comes from the column's `gap`, and wrong in an
article, which has no column.