Agent runbooks
The intended model is a versioned description of an operation that can be reviewed and audited. The legacy repository contains draft, validation, preparation, and submission concepts, but no supported end-to-end economic pipeline is available. Parsing a JSON file or producing an unsigned payload does not prove protocol-side policy enforcement, fresh-state simulation, intent binding, approval integrity, or receipt reconciliation.
The hosted Stele preview supports public reads and private provider-listing drafts, the live hosted OAuth MCP supports search plus a different deployed nonbinding booking-approval draft tool and uses authenticated runtime discovery for its inventory, and the local exact-three MCP prerelease provides read/status tools. Existing provider-listing drafts cannot be listed, read, updated, deleted, or published through MCP and have no execution path. Production currently has 0 published services, so no successful booking-approval draft runbook exists. Stele has no supported booking, provider-contact, payment, escrow, dispute, review, agent-wallet, spending-policy, signing, or submission runbook.
Release rule
Section titled “Release rule”A future runbook becomes actionable only when its exact schema, SDK encoder, protocol behavior, dedicated-key lifecycle, wallet review surface, replay protection, simulation, and receipt path are released together and independently tested. Until then, examples are pseudocode and must remain non-economic.