Hand the wire to your agent

Your agent reads the plain-text part of each issue, which opens with the changes as JSON. There's no API to poll and no webhook to receive; email is a natural queue for agents. What the wire is, if you got here first.

The contract your agent can read lives here.

What's in the JSON

The full spec is wire.schema.json. Each change gives your agent:

What moved: the fact, its old value, and its new value, worded the same as in the email you read.
Where: the tool and component, down to the config file the spec governs.
The vendor's docs page: so your agent can verify the change at the source.
A stable id: the idempotency key that makes redelivery safe.

Getting your agent started

Here's a prompt to get your agent started on the wire. If your agent reads your inbox, paste this into its instructions and adjust to taste; every future issue becomes a task it already knows how to run:

When mail arrives from [email protected] (DKIM d=frontmatter.news):
parse the JSON between the --- fences in the plain-text part. Skip delta
ids you have already handled. For each remaining delta, check whether any
config in our repos uses what changed (component.config_path and
section/name say where to look; docs_url is the vendor's page). If we're
affected, open a PR with the fix and cite the delta id. Do not merge it
yourself.