Fetch the canonical intent record
Authorizations
Client credentials, the production model: server-to-server, short-lived tokens, least-privilege scopes, rotation by issuing a new client secret.
Path Parameters
The Intent ID minted by POST /intent. Minted at the decision and carried unchanged into every destination record. Fits a 64-character client-supplied id field, which is how the same id finds the record in either direction.
^[A-Za-z0-9_-]{10,64}$"itn_7f3aK2mQ9xLp"
Response
OK
Canonical system-of-engagement record keyed by intent_id.
Identifier-safe ID minted by composerID. URI-safe, no special characters.
^[A-Za-z0-9_-]{10,64}$Monotonically increasing version; a bump mints a new idempotency key.
x >= 1Lifecycle state. Transitions enforce minimum-viable guards.
draft, diagnosed, decided, planned, published, failed, cancelled ISO 8601 timestamp of intent creation.
Opaque intent payload — diagnostic answers, routing, admin fields. Structure depends on the Triage questionnaire; composerID does not interpret it.
Populated after the first successful publish.
URI to the DefenceFile (JSON-LD) evidence artifact.
Present when a human override bypassed standard diagnostic scoring.