Notice delivery matrix
This page is rendered at documentation build time from the pinned host capability tables claude-2.1.250.json, codex-0.147.0.json, cursor-2026-08-28.json, portable-1.0.0.json. Those JSON files are the source of truth every target adapter compiles against; change them, not this page.
A notice is an entry in the append-only notice ledger co-mounted with project state (the reserved store id @agent-bundle/runtime/agent-notice-ledger/v1). It targets a recipient and moves only through evidenced states — pending, attempted, acknowledged, expired, unavailable, withdrawn. Delivery is attempted through the channels below, and a generated MCP server wires each cross-request route only where its host advertises it: the recipient-scoped inbox resource agent-bundle://notices/inbox is registered for stateful projects on hosts advertising mcp-inbox (every built-in host), and resources/subscribe plus one notifications/resources/updated per newly eligible pending notice is offered only where the host additionally advertises mcp-resource-updated and the state lifetime is workspace-durable — recorded on the ledger as an availability receipt, never a delivery claim. No host delivery is claimed without a supported channel.