Transient
Back to Home
ATP 1.1Open source (Apache 2.0)

Agent Transaction Protocol (ATP)

ATP is the public interoperability layer for governed agent actions. It is not a product SKU. It defines a stable contract for intents, policy decisions, approvals, receipts, and conformance.

The normative specification, conformance checklist, and reproducible conformance kit live in the public repository below. Intelligence and Recall in this docs section are implementation surfaces on this stack; ATP itself is vendor-neutral.

Official repository
Source of truth for the specification, JSON schemas, reference packages, and conformance artifacts.
transient-atp on GitHubATP specification (canonical)Conformance checklistConformance kitPublic claim boundaries
Canonical ATP glossary

Intent

An Intent is a machine-readable declaration of what an agent is attempting to do before execution. It captures actor identity, requested action, target scope, and declared risk context.

Decision

A Decision is the governance outcome produced by ATP policy evaluation for a specific Intent. It is one of allow, deny, or escalate, and includes the rule basis used for that outcome.

Receipt

A Receipt is the immutable evidence record emitted after ATP processes an Intent and Decision. It binds timestamps, event snapshot hashes, correlation identifiers, and outcome metadata for audit and replay verification.

Governed agent action

A governed agent action is an agent-initiated operation that is intercepted by ATP, evaluated against policy, and recorded with a verifiable Receipt before downstream execution proceeds.

Prose-first ATP references
Use these pages for dense definitions and citation-friendly implementation language.
ATP foundationsImplementation notesATP in production

Versioning and status

Version tags and the full specification history live in the repository. ATP 1.1 is published and the normative text is maintained in the canonical spec directory on GitHub. This site does not mirror ATP releases; the repository stays the single source of truth.

Conformance

ATP-L1 lists machine-verifiable requirements (stable IDs such as ATP-L1-*). The conformance checklist in the repository is the authoritative register. The reproducible conformance kit lets you validate implementations against the published contract. The summary cards below highlight baseline receipt proof expectations versus later roadmap items.

Baseline (ATP-L1)
Normative receipt proof expectations for ATP 1.1
  • occurred_at, received_at, sealed_at
  • event_snapshot + event_snapshot_hash
  • correlation_id: fail closed if missing or placeholder
Post 1.1 backlog
Explicitly not blocking for ATP 1.1
  • Advanced signing key lifecycle and rotation
  • Append-only receipt chain traversal
  • Expanded replay verification APIs
Back to docs home