missionsPhase 13

Mission Completion

When the agent believes the mission is done, it POSTs a completion interaction to the PS's interaction_endpoint with a Markdown summary. The PS presents the summary to the user. The user either ACCEPTS — the PS terminates the mission and returns 200 OK — or responds with follow-up questions via clarification, keeping the mission active. See §1285 (Mission Completion) and §1098 (Interaction Endpoint).

§ Mission Completion / § Interaction Endpoint

POST https://ps.example/interaction202

Agent signs the request with its agent token via Signature-Key: sig=jwt.

type="completion" and summary is a Markdown string (§1113).

mission binds the completion to the mission by approver + s256 (§1114).

AAuth-Capabilities is NOT sent on PS endpoints (§1731).

PS returns 202 + Location because user acceptance requires human interaction (§1179).

1 / 3

speed

Step 1: POST /interaction {type=completion, summary, mission}

Request / response

Completion Timeline

→

Mission being completed

Description (Markdown)

# Analyze Q2 Customer Feedback

Read customer feedback records and produce a summary report with sentiment analysis and key themes.

Structured Fields

approverhttps://ps.example

agentaauth:local@agent.example

approved_at2026-04-14T17:14:54Z

s256R9kNpXeErMQ1Jvk_vxYUp3YEdggmvUhksWtjXtcmnh0

Approved Tools

FeedbackReader

Read customer feedback records

ReportWriter

Write the summary report to the shared drive

PS Capabilities

interactionclarification

POSThttps://ps.example/interaction

Content-Type?

application/json

Signature-KeyAAuth?

sig=jwt;jwt="eyJhbGciOiJFZERTQSIsImtpZCI6ImFnZW50LWtleS0xIiwidHlwIjoiYWEtYWdlbnQ…

Signature-InputAAuth?

sig=("@method" "@authority" "@path" "signature-key");created=1700000000;alg="ed2…

SignatureAAuth?

sig=:MDAxMDAxMDAxMDAxMDAxMDAxMDAxMDAxMDAxMDAxMDAxMDAxMDAxMDAxMDAxMDAxMDAxMDAxMDA…

Body

{
  "type": "completion",
  "summary": "# Q2 Feedback Analysis Complete\n\nRead 1,247 feedback records across April–June and produced `q2-feedback-summary.pdf` on the shared drive.\n\n**Headline numbers:** avg rating 4.2 ⭐ · 68% positive · 22% neutral · 10% negative.\n\n**Top three themes:** (1) onboarding flow friction, (2) billing page clarity, (3) requests for dark mode.",
  "mission": {
    "approver": "https://ps.example",
    "s256": "R9kNpXeErMQ1Jvk_vxYUp3YEdggmvUhksWtjXtcmnh0"
  }
}

HTTP Signaturescheme=jwt

Covered Components

@method

@authority

@path

signature-key

Signature Base

"@method": POST

"@authority": ps.example

"@path": /interaction

"signature-key": sig=jwt;jwt="eyJhbGciOiJFZERTQSIsImtpZCI6ImFnZW50LWtleS0xIiwidHlwIjoiYWEtYWdlbnQrand0In0…"

"@signature-params": sig=("@method" "@authority" "@path" "signature-key");created=1700000000;alg="ed25519"

Signature-Key Header

sig=jwt;jwt="eyJhbGciOiJFZERTQSIsImtpZCI6ImFnZW50LWtleS0xIiwidHlwIjoiYWEtYWdlbnQrand0In0…"

Signature-Input Header

sig=("@method" "@authority" "@path" "signature-key");created=1700000000;alg="ed25519"

Agent Tokenaa-agent+jwt

Header

{"alg":"EdDSA",
"kid":"agent-key-1",
"typ"?Token type identifier. aa-agent+jwt = Agent Token, aa-resource+jwt = Resource Token, aa-auth+jwt = Auth Token:"aa-agent+jwt"
}

Payload

{"iss"?Issuer — who created and signed this token:"https://agent.example",
"sub"?Subject — who or what the token is about:"aauth:local@agent.example",
"dwk"?Discovery Well-Known — the metadata document path for key discovery (e.g. aauth-agent.json):"aauth-agent.json",
"jti"?JWT ID — unique identifier for this token (prevents replay):"a6ae301d-1dc7-4b75-8f8b-5612197664a7",
"cnf"?Confirmation — proof-of-possession claim binding this token to a key:{"jwk"?JSON Web Key — the public key bound to this token:
},
"iat"?Issued At — Unix timestamp when the token was created:1776222894,
"exp"?Expiration — Unix timestamp after which the token is invalid:1776226494,
"ps"?Person Server URL — the PS that represents this agent's user:"https://ps.example"
}

sig: 8byvGd-PR3uOLeS_HYOpbW7OD_8whUuD…