blog
Notes on verifiable records.
Signed records, verification, policy discovery, payment-related workflows, provisioning records, and open infrastructure for automated interactions.
series
Evidence handoff.
Five parts, in reading order: what has to survive when someone else reviews an automated action.
- 01An AI agent audit trail has to survive the handoffAnother team has to review an agent action without access to your dashboard. What to preserve, what a signature shows, and how to hand off a case they can check.Audit / 6 min
- 02An MCP tool call can succeed while the job is unfinishedRecord the result at the level where it happened. Keep approvals, invocations, tool results, and retries distinct for the person who reconciles them.MCP / 6 min
- 03When a customer asks why your AI gateway allowed a requestA policy decision, an enforcement action, and a downstream result need distinct evidence when a customer questions what your AI gateway allowed.Gateways / 6 min
- 04The agent paid. What did it receive?A payment record answers a payment question. Production, delivery, receipt, and acceptance each need evidence from the system that observed them.Commerce / 6 min
- 05Your next customer may be an agent. Can it tell whether you finished?Businesses handling delegated requests need to make acceptance and completion distinguishable. A status model, completion records, and where to start.Agents / 6 min
more writing
Standards, protocol and explainers.
- Verifiable provisioning records for agent-driven infrastructureWhen agents and CLIs provision services, credentials, environments, and deploy targets, signed records help teams verify what changed without owning the runtime.Protocol / 11 min
- AIPREF: a common language for AI usage preferencesHow the IETF AIPREF working group is standardizing machine-readable AI usage preferences, and where portable signed records fit alongside it.Standards / 6 min
- robots.txt (RFC 9309): crawl access control for the webRFC 9309 formalized the Robots Exclusion Protocol. Its matching and error rules, the limits of crawl control, and where verifiable access records fit.Standards / 5 min
- What is HTTP 402? Payment Required, explainedHTTP 402 Payment Required, its history, its recent revival for agents and APIs, and how it relates to (but is separate from) signed interaction records.Explainer / 2 min
- Portable evidence across agent-to-agent handoffsWhen agents hand work to other agents, the record of what was authorized and what happened has to travel with the work: policy discovery, HTTP 402 payment, and signed records.Agents / 2 min
archive
Earlier writing.
Kept for the record. These pieces use legacy terminology and commands and are not maintained against the current release.
subscribe
Subscribe on SubstackGet new articles by email.
Protocol updates, technical notes, and articles from the Originary team.