Journalist: @Journalist

Register id journalist.desk · kind desk · cadence every day that had changes

Mission

Write the pieces about what has been created: what happened, what shipped, what it does, in plain words and with every fact linked. Fact based: the Journalist reports, the Historian interprets. Capture the present, and reverse-engineer the back catalogue from the material that already exists.

The central claim, written as a failure condition

A role that says what it does can only be admired; a role that says when it is failing can be contradicted.

This role is failing when: A reader cannot tell, in a minute, what happened and where it is; or a sentence states something no cited source says; or a proposal reads as a product.

Gravity

What happened, told plainly, every claim linked.

Reads

data/changes/YYYY-MM-DD.json (the Librarian's)
the sources themselves, in sources/

Writes (its mandate: the validator holds a run record to these)

editions/
stories/

Plus what every run shares: runs/, site/, version.txt, data/loose-ends.json, issues/. Every run writes its run record, may add or close a loose end (brief/02: every desk adds to the list), files or moves issues (issues-fs-lite: the folder is the status), and rebuilds and releases the site.

Produces

editions/YYYY-MM-DD.md (the day's edition)
stories/YYYY-MM-DD__slug.md (a piece: news, feature, explainer or back catalogue), with standfirst and section in its front matter

How a run goes

Read the day's changes file, then every source you will cite.
Write the edition: a standfirst, a lead story, two to five shorter stories, and everything else by site. reviewed_by stays empty.
Write a piece in stories/ for anything that deserves the room: a feature on what was built, an explainer, a second story beneath a decision. Front matter gains standfirst (one or two sentences) and section (news, feature, explainer or back-catalogue).
Back catalogue: when a day is quiet, reverse-engineer a piece from what already exists (a site's version log, a vault, a series of briefs), dated to when it happened, sourced like any other.
Quote exactly; group related changes across sites into one story; keep shipped and proposed in the source's own words.

Works with

@Librarian: whose changes file is the day's input
@Editor: who reviews before an edition is called published

The mandate, what this role refuses and whose work it is not: MANDATE.md.

Journalist: mandate

Register id journalist.desk. A run record for this role names "agent": "journalist.desk".

Not responsible for

Without this, every role quietly becomes the same role; each entry says whose the work is.

Finding what changed Belongs to: @Librarian

What it means over time: moments, connection lines, lessons Belongs to: @Historian

Maps and graphs Belongs to: @Cartographer

What leads the front page Belongs to: @Editor

Marking a piece reviewed Belongs to: the editor of record

Refuses

A claim without a source
A quotation that is not character for character
Upgrading a proposal to a product
Writing about a person rather than a site or a role

Wrong when

A reader cannot tell, in a minute, what happened and where it is; or a sentence states something no cited source says; or a proposal reads as a product.

May write

editions/
stories/
runs/
site/
version.txt
data/loose-ends.json
issues/

Anything else in a run record's folders_changed fails tools/validate.py.

Runs (5)

2026-09-25T12:43:06Z · desk · Issues 032 and 029: a news piece about this newsroom's own changes on 25 September 2026 (releases v0.1.5 to v0.1.10, the desks' runs, the 45 issues from the editor of record's notes, the first full run), with the two experiments on this piece only: briefing cards in the front matter and a semantic twin written before the prose.
- stories/2026-09-25__the-newsroom-reads-itself.json written first: 24 nodes (10 Fact, 5 Evidence, 3 Observation, 2 Question, 1 Statement, 1 Idea, 1 Hypothesis, 1 Comment; every Fact and Evidence with a source) and 24 edges (9 supports, 6 cites, 5 follows, 2 leads_to, 2 asks_about).
- stories/2026-09-25__the-newsroom-reads-itself.md (news, about 1,080 words) written from the graph: the six release commits 08c1295, 18b68b4, 026dd52, afd0846, c5e97dc, b927dad read in full (bodies and stats); every quotation checked against the commit bodies and run records.
- Counts computed from the files: 11 tags v0.1.0 to v0.1.10 on origin, all dated 2026-09-25 (none in this clone); 30 run records dated 2026-09-25 (build 9, editor.desk 6, librarian 4, journalist 4, historian 2, architect.guest 2, editor.human 2, cartographer 1); issues 45 = 20 open, 23 done, 2 blocked after this run's two moves (030 and 033 were moved by commit a2e6cc8 at 12:40 while this run was working), 8 epics, 33 tasks, 4 briefs; 35 bullet-line notes (12 site, 20 content, 3 riskmandate); 16 issues moved to done across v0.1.8 to v0.1.10 (7, 5, 4).
- cards: four briefing cards (What happened, Where, Waiting on, Next) in the front matter; rendered and checked in the built page.
- issues/open -> issues/done: 032-newsroom-reports-on-itself.md (the piece is written; the Librarian's half, releases in the changes file, is not) and 029-semantic-twin-experiment.md (round one of two done on this piece; round two on the next new piece, then the editor of record decides). issues/open now 20, issues/done 23.
- Built, validated and check_diagrams run into a private NEWSROOM_SITE_OUT folder; the page's diagram renders (0 failures on 9 pages).
2026-09-25T09:09:51Z · desk · Back catalogue, part B: four pieces a new reader needs (a reader's guide to the 32 sites, a feature on abp.sgit.ai, a feature on the three newsrooms, an explainer on how agentic teams are organised), and standfirst and section lines for the three existing stories.
- stories/2026-09-24__a-readers-guide-to-the-sgit-network.md (explainer, about 1,070 words): all 32 sites in seven groups, one or two sentences each from its own llms.txt (front page for the two provider sites without one), file counts from sources/sites/manifest.json.
- stories/2026-09-24__the-agent-behaviour-policy-site.md (feature, about 1,130 words): what an ABP is, 20 releases from v0.1.0 to v0.11.0, 315 files (182 md, 131 json, 2 txt), 14 articles, and riskmandate.ai's use of it (16 vault pages, the reviewed level, Lab 03 requests), shipped and drawn kept apart.
- stories/2026-09-24__three-newsrooms.md (feature, about 1,080 words): newsroom.sgit.ai's three running instances against its design, pt.newsroom.sgit.ai's real and not-real lists, this newsroom from brief/01; records that pt.newsroom.sgit.ai's llms.txt says no story is published while its story index says 5 of 6 are.
- stories/2026-09-25__how-agentic-teams-are-organised.md (explainer, about 1,020 words): teams.sgit.ai's two fields, claim forms 6/7/6, Explorer/Villager/Town Planner, and this newsroom's nine agents compared field by field. Dated 2026-09-25, not 2026-09-24, because the newsroom's register it describes was created on 25 September (commit dee6057).
- Added standfirst and section: news to the three existing stories (2026-09-21, 2026-09-23, 2026-09-24); nothing else in them changed.
- Every quotation in the four new pieces checked by script against the snapshot, brief/, agents/ and the dee6057 commit message: 0 missing.
2026-09-25T09:09:21Z · desk · Back catalogue, part A: reverse-engineer four pieces from material the network already has: sgit.ai from v0.1.1 to v0.6.8, RiskMandate.ai from its baseline to v1.34.8, the five business plans published as vaults, and the 36 published vaults as a whole.
- stories/2026-09-24__sgit-ai-from-v0-1-1-to-v0-6-8.md (1198 words): 166 version-log entries read; counts by series (27, 100, 10, 10, 10, 9), by month (81 August, 85 September) and by day computed from sources/history/sgit.ai-version-log.json.
- stories/2026-09-24__riskmandate-from-baseline-to-v1-34-8.md (1133 words): versions.md (106 releases, 35 reconstructed, 71 from git) and 20 release notes read, plus index.md and pricing.md; prices quoted as the pages state them (£10, £50, £500, £1,500), and the record's own £5/£10 disagreement reported.
- stories/2026-09-24__five-business-plans-published-as-vaults.md (1240 words): README, PUBLIC.md, plan/00-START-HERE.md and spec headings of all five vaults, the five sgit.ai vault pages and startups/business-plans read; file counts (32, 31, 32, 27, 60) computed from sources/vaults/.
- stories/2026-09-24__thirty-six-published-vaults.md (1085 words): published-vaults.json (36 entries, 8 categories, 2,957 files, about 308 MB, 21 August and 15 September), data/vaults.json (36 read keys, all sgit_public_read_), demos/vaults/index, publishing and catalogue pages read.
- No key is printed in any story; each piece points at the vault page that publishes it.
2026-09-25T08:02:03Z · desk · Correct links in the editions and a story that pointed at sgit.ai repo content paths, not live pages.
- editions/2026-09-20.md, 2026-09-21.md and stories/2026-09-21__the-performance-page-that-corrected-itself.md: links to update notes now point at the anchors on sgit.ai/updates/, which are in the snapshot.
2026-09-25T00:20:23Z · desk · Journalist for 20 to 24 September: one edition per day, and a story where one deserved the room.
- editions/2026-09-20.md to 2026-09-24.md, all reviewed_by empty.
- stories/2026-09-21__the-performance-page-that-corrected-itself.md, 2026-09-23__a-proposal-to-uk-sovereign-ai.md, 2026-09-24__brief-to-build-in-a-day.md.
- Verified the 24 September lead against the sources: the interview page was briefed and built the same day; sgit.ai's briefs index still lists it as open.