Console

The pipeline

Stage 6 is the only one that cannot be moved by any agent. estado: publicado is the editor of record's line; gate 11 fails the build if it appears without their name and a date.

Departments · who may write where

The agent team · 5 roles, 17 board cards, 8 messages

Three pages, generated by build/newsroom_team.py from dados/agentes.json and the mail folder. The roles are defined in the shape teams.sgit.ai publishes for a ROLE.md, and they coordinate under Email-FS-lite — files in a folder, one commit per cycle, no broker and no API.

Board · 9 issues

Rendered from redacao/issues/*.json. The same issues appear on each agent's board, placed there by a published formula and not by hand. The reader-facing version of this board is A mesa, in Portuguese.

Articles · 6 folders, 5 published

Each article is a folder at artigos/<yyyy>/<mm>/<dd>/<slug>/ holding the prose, the claim record and the provenance. dados/historias.json is derived from those folders and is never hand-edited.

Sections · coverage

Runs

Recent commits

Run it yourself

python3 build/tudo.py               # THE WHOLE BUILD, IN ORDER, THEN THE THREE GATES
python3 build/tudo.py --fetch       # the same, going to the network for the sources first
python3 build/tudo.py --so-portoes  # gates only, no rebuild
python3 build/tudo.py --render      # plus the browser gate (needs playwright installed)

# what build/tudo.py runs, in this order — the order is load-bearing
python3 build/extract.py [--fetch]  # fetch, freeze, hash, register, extract, diff
python3 build/graph.py              # ontology, graph, triples, manifest, source publishers
python3 build/entidades.py          # dados/entidades.json + a page per entity  ← before any page
python3 build/comentarios.py        # agent activity per article, derived from the records
python3 build/artigos.py            # article folders -> pages + derived index
python3 build/build.py              # every reader-facing page
python3 build/paginas_extra.py      # /api/ and /proveniencia/
python3 build/api.py                # api/v1/ — every path is a file on disk
python3 build/newsroom.py         # this console
python3 build/chrome.py             # llms.txt, sitemap.xml, index.md
python3 build/gates.py              # gates  1-15  — must print OK
python3 build/gates_artigos.py      # gates 16-25  — must print OK
node admin/build/validate.js        # the site gate — must print OK
node admin/build/render.mjs         # the browser gate — opt-in, see below

# build/entregas.py is run per delivery, not per build:
python3 build/entregas.py --fetch   # freeze delivery sources, check every excerpt

Use build/tudo.py. The order matters and it is not obvious: entidades.py must run before anything that writes a page, because the pass that turns a name in prose into a link reads the file it produces — run out of order, nothing breaks, the site just quietly has fewer links than it should. The command list in CLAUDE.md is older than half these steps, and CLAUDE.md is the rules file: it is in the deny list on purpose, and editing the rules to match the code is backwards. So the real order lives in an executable file, where it cannot go stale without something failing.

Run --render before shipping anything that touches assets/components/. The other three gates read files and read HTML; none of them executes anything. A component that throws on load passes all three and reaches the reader as an empty box — which looks like a design choice. The browser gate opens each component in a real Chromium and fails on a console error, a failed request, a component that never reaches data-estado="pronto", or a page that overflows at 390px. It is opt-in because it needs a browser and this repository has no node dependencies; when CI has one, it becomes a gate without a line of it changing.

Without --fetch the first two run against the copies already frozen and touch no network. That is how the site is rebuilt from a clone, years later, to exactly the same pages.

Elsewhere in the estate

121 markdown documents in this repository are readable at documents.