Temet protocol
Human-Supervised Delivery Protocol
How Temet separates agent preparation from expert validation before a client-facing delivery.
Intent
Make the expert review step explicit so agent output can become accountable professional work.
Protocol behavior
When to use it
Use this protocol when an agent has prepared work, but the final answer must carry the expert's judgment.
- The output affects a business, technical, legal, or operational decision.
- The client needs a reviewed deliverable, not raw generated text.
- The expert must decide what is correct, incomplete, or unsafe to send.
Production versus validation
Temet treats production and validation as separate phases. The agent can draft, compare, structure, and summarize. The expert validates, corrects, signs, or refuses the delivery.
Delivery status
The protocol keeps the state explicit: requested, prepared, reviewed, delivered, declined, or closed. This makes the work auditable without pretending the machine is the accountable party.
Terminal command
temet mission <mission_id> reply --status ready-for-reviewJSON shape
{
"type": "mission.thread.reply",
"missionId": "mis_01",
"status": "ready-for-review",
"preparedByAgent": {
"summary": "The agent prepared a decision brief and unresolved risks.",
"artifacts": [
"architecture-review.md"
]
},
"humanReviewRequired": true,
"reviewChecklist": [
"Check factual assumptions",
"Validate recommendation",
"Remove unsupported claims",
"Approve delivery wording"
]
}Sample response
{
"status": "review_required",
"missionId": "mis_01",
"message": "Prepared work is waiting for expert validation."
}Related surfaces