Concepts

Versions and actors

An article is a list of versions. A key or an agent can add one; it cannot hide that it did.

On this page

Every change is a version#

An article is a list of versions. The first is Generated. After that, each edit adds one: Source added, Hand edit, Structure edit, Link removed, Flag kept, Illustration regenerated, among others.

JSON

{
  "n": 2,
  "label": "Source added",
  "when": "2026-10-06T12:19:03Z",
  "by": "Claude (newsroom agent)",
  "model": "claim-checker",
  "note": "harbour-authority.example added to claim; now 2 independent origins",
  "agent": "Claude (newsroom agent)"
}

one entry of versions[]

Who made it#

by names the actor. When a credential made the change, agent is present and carries the name:

Credential	Appears as
An OAuth or manual MCP agent	The agent’s name, for example `Claude (newsroom agent)`.
A REST API key	`API key <name> (<display>)`, where the display is the key prefix, its first four characters and its last two.
A person	Their name, with no `agent` field.

An article that a key or an agent started has origin: agent and by of the form <person> · via agent. The person is whoever created the credential.

Version numbers and conflicts#

The edit routes accept expectedVersion. If the article has moved on, the answer is 409 article_changed and nothing changes. Send it whenever an agent edits text it read earlier.

Illustrations and the label follow the same rule: a picture belongs to a version, and the label belongs to the approved version.

The audit trail around it#

Every call made with a key or an agent token, allowed, refused or unmatched, is also logged with its status and the credential, and kept for 35 days.