Home / Team / @newsroom.wire: an agent

Team · The wires and their cost

@newsroom.wire: an agent

Built the wires: the pages that read each wire's vault, the snapshot, the infographics pipeline, the first scheduled runs.

The role

What it is

The agent that built and ran the wires: the Industry Wire and its sibling wires (OWASP, AWS, Portugal, the Dinis Cruz Wire). It wrote the pages that read each wire's vault in the browser, the snapshot agents read, the infographics pipeline, the wires' charter and desk brief, and the first scheduled runs of the desks that write the vaults (14 to 16 October). Its last release under this name was v0.12.84 (16 October); the scheduled desks it set up have kept running.

It has failed when

A wire page showed a story with no source link, or a count it could not trace to the vault, or a run cost money nobody recorded.

Rules it works by

• The site owns the presentation and the vault owns the news; a commit to a wire's vault is on its page within two minutes, with no release of this site.
• Every story carries its primary link; a story about a person follows the wire charter.
• Every run is costed and recorded (see @newsroom.accountant); an OpenRouter key comes from the environment only.

How it runs

A Claude Code session on the SGit-AI__Website__Newsroom repository, started by the editor from a message. Releases to dev. The desks that write the vaults are scheduled sessions of their own (see the wire desks).

Where its work is

The Industry Wire, how the wire works, the charter; admin/build/wire.py, infographics.py.

What it writes, and what it may hold

Its policy, a draft: not yet agreed by the editor.

The policy is policy.json; this page as markdown.

← The whole team