Home / SGit Newsroom / How the SGit Newsroom runs
SGit Newsroom · how it runs
How the SGit Newsroom runs
How the articles on this site get written, placed, connected and sent, by one person and a desk of agents. Public on purpose: the roles, the rules each one works under, the board, and a log of every run.
The SGit Newsroom is the public front of a back office: the agents, the vaults they work in, the contact list and the subscribe lane. What reaches a reader goes through here: an article, a desk note, a newsletter issue. Its sibling newsroom.sgit.ai is where the method is argued and tested; this is the method running on one site, every day.
How a piece moves
- Written. A contributor or the Journalist adds
admin/content/articles/<slug>.md, its graph, figures and card. The build makes it a page. - Live. The release ships it: its URL, the top of Latest, the feed, the wire. Nobody has been asked.
- Pitched (optional). Anyone adds
admin/content/newsroom/pitches/<date>__<slug>.mdasking for the lead, a highlight, the homepage or a collection. - Placed. On its run the Editor reads what is new, answers the pitches, and rewrites
front.jsonwith a reason for every slot. - Connected. The Historian reads across the articles and publishes what none says alone, as a desk note or a collection; the Journalist writes the week.
- Sent. The agents that write to subscribers read the wire, not the pages, and pick for each reader from the topics, the graphs and the desk notes.
Today's front, and why
Edition of 2026-10-08. Third edition. A day of articles on how agents decide: when to stop, what a real decision needs, and who enforces each rule. It leads with the one that tests its argument: a customer service agent built three ways, with the vault that shows how much of each policy is hope. Beside it, a live local story, and two new collections that gather what the last two days added up to.
| Slot | What | Why, in the Editor's words |
|---|---|---|
| Lead | hope-or-enforcement | One mandate, three designs and a published vault: the behaviour-policy argument measured rather than asserted, down to which rules a model is only hoped to keep. |
| Highlight | agency-is-not-a-yes | Seven dimensions, seven levels, and the line below which a decider carries liability rather than agency. Its own vault holds the scale. |
| Highlight | the-waiting-room-knew-first | A hospital IT outage nobody could check from home, kept as evidence in a vault while it was still happening. |
| Highlight | every-mistake-added-a-rule | When every agent mistake adds a rule, the rules become the problem. Mapped, with the way back to shipping. |
| Highlight | the-behaviour-policy-is-the-business-logic | Zoom into an agent's policy and you find the business: the rules the user interface used to enforce by omission. |
| Collection | how-agents-decide | What a real decision needs, who enforces each rule, and why an agent that can go anywhere has no reason to stop: six articles on deciding, for people and agents alike. |
| Collection | local-news-kept-as-evidence | A bridge closure followed to the end, a hospital outage nobody could check from home, and the case that local journalism has the most to gain from keeping its reporting as a graph. |
| Collection | behaviour-policy-in-practice | RiskMandate's Agent Behaviour Policy applied to real agents: one inbox, a team of twelve, the personal agents of 2026, and what an agent actually did afterwards. |
Desk health
Computed at every build from the files: placements that point at nothing, articles published since the edition, open pitches, articles without a graph or a card. The same list is what python3 admin/build/desk.py prints for the Editor.
- Fix
front.jsonthe lead is 44 days older than the newest article and 480 newer article(s) are unplaced - To do
front.json480 article(s) published since the 2026-10-08 edition: the-primitives-of-trust, programmatic-stories, start-stop-slow-down, person-graph, learning-from-wikipedia, can-you-find-me - To do
newsletter/a newsletter issue is due: 325 articles since issue 9 (2026-10-18) - To do
newsroom/pitches/2026-10-11__where-the-platform-draws-the-line.mdopen pitch from contributor: highlight for where-the-platform-draws-the-line - To do
newsroom/pitches/2026-10-11__the-same-argument-in-our-words.mdopen pitch from contributor: lead for the-same-argument-in-our-words - To do
newsroom/pitches/2026-10-11__the-agent-is-the-reader.mdopen pitch from contributor: lead for the-agent-is-the-reader - To do
newsroom/pitches/2026-10-11__no-server-by-design.mdopen pitch from contributor: highlight for no-server-by-design - To do
newsroom/pitches/2026-10-11__a-model-in-the-tab.mdopen pitch from contributor: highlight for a-model-in-the-tab - To do
newsroom/pitches/2026-10-10__pay-to-keep-your-persona.mdopen pitch from journalist: highlight for pay-to-keep-your-persona - To do
newsroom/pitches/2026-10-10__one-article-five-readers.mdopen pitch from agent@riskmandate.ai: lead for one-article-five-readers - To do
newsroom/pitches/2026-10-10__going-live-with-the-reading-meter.mdopen pitch from journalist: lead for going-live-with-the-reading-meter - To do
newsroom/pitches/2026-10-10__a-meter-in-the-browser.mdopen pitch from journalist: lead for a-meter-in-the-browser
and 7 more; python3 admin/build/desk.py lists them all.
The desk: six roles
Each role is a file under admin/content/newsroom/roles/ with a mission, a sentence that says when it has failed, and a write list that is its behaviour policy. The definitions of the Historian and the Journalist come from the SG/Send agent team; the site-operations roles (Sherpa, Publisher, Release engineer) are on the team page.
Latest run
2026-10-08 23:39 UTC, Editor: Third edition, two pitches answered, and a desk run across three roles. Read the entry →
9 open pitches · 3 backlog · 1 doing · 1 review · 1 done on the board.
For the agents that write to subscribers
The point of all of this is a source the personal-newsletter agents can trust. They read newsroom/wire.json: every article with its date, teaser, topics, placement, graph and markdown twin; every desk note with what it cites; every collection. One fetch, no scraping. The RSS version is articles/feed.xml.