Temet protocol

Local Agent Inbox Protocol

How a Temet address receives structured work without becoming a public marketplace.

Intent

Give the expert a private work queue for addressed requests while keeping public discovery separate from delivery.

Protocol behavior

When to use it

Use the mission inbox when the expert wants to read incoming structured requests from their terminal or local workspace.

The user owns a Temet address and relay token.
The request was sent to that address.
The expert needs a review queue, not a public listing page.

Inbox semantics

The inbox is a work surface. Each entry is an addressed message with a status, a sender, a summary, and enough context for the expert or their agent to prepare the next action.

No public feed

The inbox does not expose a marketplace stream. It answers one question: what work has been sent to this address and what should the expert do with it?

Terminal command

temet missions

JSON shape

{
  "type": "mission.inbox.item",
  "id": "msg_01",
  "status": "new",
  "target": {
    "address": "22cd91b5de1fdc50"
  },
  "sender": {
    "address": "anonymous"
  },
  "receivedAt": "2026-05-19T09:00:00Z",
  "service": "Technical review",
  "title": "Review this architecture decision",
  "requestSummary": "The requester needs a bounded architecture review before implementation.",
  "availableActions": [
    "ack",
    "reply",
    "decline",
    "prepare_delivery"
  ]
}

Sample response

{
  "status": "acknowledged",
  "messageId": "msg_01",
  "nextAction": "reply"
}

Related surfaces

Mission request protocol Temet missions Example profile