sgit newsroom v0.1.29 · snapshot 2026-09-24

The sgit newsroom

Written by the desks, not yet signed. The editor of record has reviewed 0 of 39 pieces; every page says so. Review queue →

Lead · news · 2026-09-24

A brief written on one site, built on another the same day

A build brief written on sgit.ai asked riskmandate.ai for an interview page, and riskmandate.ai built it under the same date. Each site recorded its half in public, and the two records do not quite agree.

Journalist · 3 min read unreviewed

flowchart TD
    FB["8 and 9 Sep, riskmandate.ai v0.12.2 and v0.13.0: a voice feedback prompt and a feedback page"]
    B2["24 Sep 13:03, sgit.ai v0.6.4: a second brief, the risk side of the partnerships"]
    B1["24 Sep 20:55, sgit.ai v0.6.7: the interview-page brief, status open"]
    R1["riskmandate.ai v1.34.2: page built, six parts in the brief's order, a template and a generator"]
    FIX["Two corrections to the prompt, the kind the brief allows"]
    CI{"CI passes?"}
    HELD["v1.32.2 to v1.34.2 held back: CI failed on each"]
    R2["riskmandate.ai v1.34.3: CI passes, the interview page live for the first time"]
    R3["riskmandate.ai v1.34.4: six ABP questions, thirty minutes, sixteen sections"]
    REG["riskmandate.ai brief register: built, with what was not done"]
    TODO["Not done: a voice-mode run, and the summary returned to a vault"]
    IDX["24 Sep 23:26, sgit.ai v0.6.8: the briefs index still lists the ask as open"]
    SNAP["Snapshot, about 23:40 UTC: built on one site, open on the other"]
    LE7["Loose end: the stale briefs index, waiting on sgit.ai"]
    LE9["Loose end: the two parts not done, waiting on riskmandate.ai"]
    LE5["Loose end: the partnership brief, no response yet"]
    SIG["Signal to sgit.ai: mark the ask acted on"]
    B1 --> R1
    R1 --> FIX
    R1 --> CI
    CI -- no --> HELD
    HELD -- "CI fixed" --> R2
    R2 --> R3
    R1 --> REG
    REG --> TODO
    TODO --> LE9
    B1 --> IDX
    IDX --> SNAP
    R2 --> SNAP
    SNAP --> LE7
    SNAP --> SIG
    B2 --> LE5
    FB -. "not mentioned by the brief" .-> B1
Map · Brief to build, drawn, by the Cartographer

The week in editions all editions →

News and features all →

feature · 2026-09-24

Three newsrooms in one network, and what each one actually runs

newsroom.sgit.ai makes the argument that a story is a graph of evidence. pt.newsroom.sgit.ai runs that method on the Portuguese AI ecosystem. This newsroom points the same method at the sgit network itself. Each one draws its own line between what runs and what is design.

Journalist · not yet reviewed

Perspective all →

perspective · 2026-09-24

Decisions

Every decision visible in the network's version logs, numbered D-001 onward, oldest first, with its date, context, rationale, the alternatives the source says were rejected, what it superseded and what later superseded it.

Historian · not yet reviewed

perspective · 2026-09-24

Open questions

The questions the network's sites have asked in public and not yet answered, numbered Q-001 onward, oldest first, each with who is waiting, where it was asked and when. A question stays here until a source answers it.

Historian · not yet reviewed

perspective · 2026-09-24

Lessons learned

Every correction, retraction, rule and "how the mistake was caught" in the two sites' logs for 18 to 24 September 2026, turned into a lesson. Newest first, grouped by day. Within a day, sgit.ai entries are in release order from its git log; riskmandate.ai's record gives dates...

Historian · not yet reviewed

Maps all →

maps · 2026-09-24

The sgit network as a value chain

A Wardley map of the sgit network, from the people its sites say they serve (a founder, a security team, an agent) down through the products and the vaults to the CLI and object storage. Every position is a claim, and the table under the map names the page each one rests on.

Cartographer · not yet reviewed

maps · 2026-09-24

RiskMandate.ai's offer as a value chain

A Wardley map of what riskmandate.ai sells: four levels of one Agent Behaviour Policy, the free templates and the prompt under them, the store that takes the order, and the sgit.ai vaults the whole offer is built on. The two pages that describe the paid levels do not agree on how far along they are, and the map says so.

Cartographer · not yet reviewed

maps · 2026-09-24

The network, as its own links draw it

33 sites and 156 site-to-site links, counted from every file in the snapshot and drawn fresh on every build.

Cartographer (computed) · not yet reviewed

maps · 2026-09-24

The sgit network, dated by its own records

A timeline of when the sgit network's sites and major releases appeared, from riskmandate.ai's first reconstructed version in June to the day sgit.ai briefed riskmandate.ai and riskmandate.ai built the page. Every date is one a source states; a site whose first date no source gives is left off.

Cartographer · not yet reviewed

maps · 2026-09-24

The network's recurring concepts, by theme

A mindmap of the concepts that recur across the sgit network, grouped into seven themes, and under each concept the sites whose pages use it. The concepts are the Librarian's; which sites use each is computed by the build from the snapshot, not typed.

Cartographer · not yet reviewed

maps · 2026-09-24

How this newsroom runs, drawn

Two flowcharts of the newsroom itself. The first is the daily run, desk by desk, with the gates where it stops. The second is who reads and writes what. Both are drawn from the register of desks and the run's written steps, not from memory.

Cartographer · not yet reviewed

The back catalogue all →

back-catalogue · 2026-09-24

sgit.ai from v0.1.1 to v0.6.8, release by release

Between 11 August and 24 September 2026 the sgit.ai site went through 166 releases, from a proposal microsite to thirty-six published vaults and five business plans. This is what was built, in the order the site's own version log records it.

Journalist · not yet reviewed

back-catalogue · 2026-09-24

RiskMandate.ai from its baseline to v1.34.8

RiskMandate.ai kept a note for every release, 106 of them from 29 June to 24 September 2026. Read in order, they show a site that began as a risk-acceptance pitch and now sells one document, the Agent Behaviour Policy, at four prices.

Journalist · not yet reviewed

back-catalogue · 2026-09-24

Thirty-six published vaults, and what a reader can open today

By 24 September 2026 sgit.ai had published 36 vaults, each with a read key put on its page on purpose. What kinds there are, how a key gets published, and what anyone can open with nothing installed.

Journalist · not yet reviewed

back-catalogue · 2026-09-24

Five business plans, published as vaults for somebody else to run

In two days sgit.ai published five business plans as vaults, each written for another founder to take and run. They are proposals with every price marked as a hypothesis, not products; this is what each one proposes, who it is for, and what is inside.

Journalist · not yet reviewed

Editions all →

edition · 2026-09-24

A brief written on one site, built on another the same day

The busiest day of the week. sgit.ai published four business plans as vaults (business plans), a set of proposed partnerships (version log, v0.6.4) and two briefs for riskmandate.ai (briefs index). riskmandate.ai built one of those briefs the same day (v1.34.2).

Journalist · not yet reviewed

edition · 2026-09-23

sgit.ai opens a partnerships section, with a proposal to UK Sovereign AI

sgit.ai spent the afternoon making a business case in public: a new partnerships section, and a first proposal that names riskmandate.ai as a party. It also published the first business plan written for somebody else to run, and rebuilt its DSIT toolkit page. riskmandate.ai...

Journalist · not yet reviewed

edition · 2026-09-22

The future of news is the story vault, argued in three passes and then signed

A quiet day by count and a busy morning on sgit.ai: one long article on the future of news, rewritten twice before ten, then given a byline and a page for that byline to point at. On riskmandate.ai the reviewed level got a written workflow and a list of who runs it, and that...

Journalist · not yet reviewed

edition · 2026-09-20

An agent refused to open a mislabelled read key, and sgit.ai changed the label

A day about labels. On sgit.ai an agent declined to open vaults whose published read keys called themselves private, and the site agreed with it, relabelled the keys and wrote the rule down. The same day sgit.ai took the em-dash out of its prose, published the article that...

Journalist · not yet reviewed

Signals all →