Protocol

Temet protocol

Mission Request Protocol

How an agent sends a structured work request to one known Temet address.

Intent

Replace vague contact messages with a bounded request that an expert can accept, price, decline, or turn into a signed delivery.

Protocol behavior

When to use it

Use a mission request when a requester already knows which Temet address should receive the work. The protocol is addressed, not broadcast.

  • The work has a concrete expected outcome.
  • The expert must decide whether the scope is acceptable.
  • The request needs context, constraints, and open questions before any commercial response.

What the receiving agent gets

The receiving agent gets a service/request object. It can summarize the need, prepare clarification questions, identify relevant capabilities, and leave the final decision to the human expert.

Human boundary

A mission request is not an automatic order. It is a work object prepared for human review. The expert can respond with a proposal, request clarification, decline, or produce a signed deliverable later.

Terminal command

temet ask 22cd91b5de1fdc50 "Review this architecture decision" \
  --service "Technical review" \
  --outcome "Decision brief with risks and next steps" \
  --constraints "No database migration, answer within 48h"

JSON shape

{
  "jsonrpc": "2.0",
  "method": "service/request",
  "params": {
    "target": {
      "address": "22cd91b5de1fdc50"
    },
    "sender": {
      "address": "anonymous"
    },
    "service": "Technical review",
    "title": "Review this architecture decision",
    "requestSummary": "The requester needs a decision brief on a proposed architecture change.",
    "expectedOutcome": "Decision brief with risks and next steps",
    "constraints": [
      "No database migration",
      "Answer within 48h"
    ],
    "openQuestions": [
      "Which failure modes matter most?",
      "What should be verified before implementation?"
    ],
    "preparedByAgent": {
      "name": "Requester agent",
      "contextSummary": "The request was structured from a conversation before being sent."
    }
  },
  "id": "mission_request_001"
}

Sample response

{
  "status": "received",
  "nextAction": "expert_review",
  "message": "The mission request is now available in the expert mission inbox."
}

Related surfaces

Temet · Mission Request Protocol