Guidance
What to read before you change anything here — human or agent.
This is the operations console, not the publication. It is in English on purpose: its audience is whoever is operating the newsroom, not the reader of the paper. The publication itself is natively Portuguese and nothing here is linked from the masthead. Every number on these pages counts files in this repository — the back office reports on the newsroom and never on the world, and a gate fails the build if a page here ever cites a frozen source as evidence for a claim about Portugal.
Everything except what a visitor reads is in English. One test decides it: would a visitor to pt.newsroom.sgit.ai read this string on the site? Yes means European Portuguese under AO90; no means English. That covers code, comments, commit messages, this console, the release history, API paths and browser-side state. It does not cover the prose, the entity names, or the ontology's readings — those are what the reader reads.
A rule without a gate is decoration. Every principle below names the thing that stops the build when it is broken, and the one principle that has no gate says so in those words. If you add a rule, add the gate in the same change — and break it on purpose first, because a gate that has never failed is a comment.
Start here
The one-minute version, the reading order, and what not to build. Most tasks end at the third item on that list.
The language rule
One test decides every naming question: would a visitor read this string on the site? The most commonly broken rule here, including by the agent that wrote most of this pipeline.
The nine principles
Each one names the gate that enforces it. The one principle with no gate says so in those words.
Before you change anything
The checklist: know who you are, read in order, find out who else is working here, check the tree is green before you touch it, build with build/tudo.py, record what you did.
More than one session at a time
Three sessions work on this repository at once. What has actually collided between them, which gates now catch each one, and the order that avoids most of it. Includes the merge that succeeded and still deleted a release's work.
Who you are
More than one agent works here and they are not interchangeable. Claim an identity, name it in your run record, and the gates hold you to its write scope. If no identity fits the work, that is a message to the editor, not a licence to invent one.
| Agent | Role | Writes in | Declares | Mandate |
|---|---|---|---|---|
| Pesquisa @Pesquisa | departamento | fontes/congeladas/<data>/, dados/registo.json, dados/*.json extraídos das fontes… | pesquisa.pt | ROLE · MANDATE |
| Redação @Redacao | departamento | artigos/<data>__<slug>/, conteudo/*.md, redacao/correio/redacao.pt/… | redacao.pt | ROLE · MANDATE |
| Verificação @Verificacao | departamento | dados/verificacoes/*.json, artigos/<data>__<slug>/verificacao.json, redacao/correio/verificacao.pt/… | verificacao.pt | ROLE · MANDATE |
| Bastidores @Bastidores | departamento | backoffice/, build/ (exceto os portões), assets/… | bastidores.pt | ROLE · MANDATE |
| Dinis Cruz @Dinis | humano | estado: publicado, redacao/decisoes/, redacao/correio/dinis.humano/… | dinis.humano | ROLE · MANDATE |
The rest of the estate
This repository is an instance of an argument made elsewhere, not a restatement of it: where these answer a question, we link rather than copy. sgit.ai/docs/guidance · coding.sgit.ai — the house style, derived by counting rather than from documentation · nfrs.sgit.ai — version control, reliability, resilience, security, backups, consistency, explainability, documentation · newsroom.sgit.ai — the parent publication.
build/newsroom.py from the files in this
repository; nothing here is hand-written. The machine-readable index of the publication is at
llms.txt. Source: github.com/SGit-AI/SGit-AI__Website__Newsroom__PT · file:
newsroom/guidance.html · version v0.23.6.