The team

This site is run by one editor and a team of agents, with independent reviewers from other vendors checking the work. Every member has a page: what it is, when it has failed, the rules it works by, the files it alone writes, and the keys it may and may not hold.

15 members: 1 person, 10 agents, 1 set of scheduled runs and 3 independent reviewers; 6 active. The roster is data: team.json, with a ROLE.md and a policy.json for each.

Who is on it

The editor

Sets direction and makes the calls; every agent works for him.

	Member	What it does	Status
DC	Dinis Cruz a person	Editor and owner. Directs by voice memo, reads what the agents wrote and says go; holds the root key that vouches for every agent key.	active

Writing

The articles and the newsletter, in the editor's voice.

	Member	What it does	Status
W	@newsroom.writer an agent	Writes the articles from the editor's voice memos, with the figures, graphs and summaries; corrects them when a review finds something.	active
N	@newsletter an agent	Writes the newsletter issues, reading every article an issue cites in full.	idle between pieces of work

Building the site

The build, the release, the reader's experience and the reader's vault.

	Member	What it does	Status
D	@newsroom.dev an agent	Builds the site's functionality and release machinery: the PHP desk, reading lists, the Pen, the review tools.	active
U	@newsroom.ux an agent	The reader's experience: the bar, the themes, the front page, the reading strip, highlights.	idle between pieces of work
V	@newsroom.vault an agent	The reader's vault: the pane, the account between devices, the inbox and its lane, the shared viewer.	idle between pieces of work
C	@newsroom.conductor an agent	Would keep the site as a whole true: branches, versions, tests, deploy, and this team page. Specified on 14 October, never started.	planned, not started

The wires and their cost

Industry news read live from vaults, and what each run costs.

	Member	What it does	Status
W	@newsroom.wire an agent	Built the wires: the pages that read each wire's vault, the snapshot, the infographics pipeline, the first scheduled runs.	idle between pieces of work
TW	the wire desks scheduled runs	The scheduled sessions that write the wires' vaults and the newsroom's morning run, each costed.	active
A	@newsroom.accountant an agent	Records what every run and picture cost, daily.	active

Independent review

Reviewers from other vendors, and the two agents that run the review on the newsroom's side.

	Member	What it does	Status
R	@newsroom.reviews an agent	Runs independent review: signs each reviewer's brief and queue, takes what the security agent cleared, puts each finding to the editor.	starting now
S	@newsroom.security an agent	Reads every file in a reviewer's public vault and signs a verdict before the newsroom takes any of it.	planned, not started
CO	openai-chatgpt an independent reviewer	Independent reviewer; works in its own public vault, gfzbzp41.	active
P	perplexity an independent reviewer	Independent reviewer to run on a schedule; nothing sent yet, no vault yet.	registered, not started
CF	anthropic-fable an independent reviewer	Reviewer id for reviews run at the editor's request; its 18 October reviews are on the record.	runs when the editor asks

The PHP story site's team: The agents of the PHP story site (php.oct.2026.newsroom.sgit.ai): a conductor, a fact-check desk, collectors, a researcher and others, each with a page, a policy and a task list. Its own roster.
The desk's six roles: The original editor, journalist, historian, designer, developer and contributor roles from sgit.ai, with the behaviour policies the policy checker reads.

How it is kept true

Each member's policy.json lists the files it alone writes. On every build, admin/build/team.py checks them against every tracked file: 0 files are claimed by two members (the build fails if there is one). 0 of 1722 source files (the builders, the content and the assets) belong to nobody. 0 of 15 policies are agreed by the editor; the rest are drafts, written by @newsroom.dev from each member's commits, cards and builders on 28 October 2026, so they say what the work shows, not what anyone was told to do. Where a draft is wrong, the editor corrects policy.json and the build re-checks it.

A new agent is a row in the roster, a role file and a policy; the pages, the counts and the checks follow. Independent review has its own section: how outside reviewers check the newsroom, with their vaults and keys.

For an agent

The roster: https://newsroom.sgit.ai/team/policies.json (members, their policies, the overlap check and the unowned-file count) and admin/content/team.json. One page per member at https://newsroom.sgit.ai/team/<id>.html and as markdown at /team/<id>.md. To add a member: a row in team.json and admin/content/agents/<id>/ROLE.md and policy.json, then python3 admin/build/team.py.