Temet protocol
Proof of Production Protocol
How a supervised delivery records human review, corrections, and a verifiable content hash.
Intent
Give clients evidence that a human expert reviewed the work before delivery.
Protocol behavior
When to use it
Use proof of production when the final delivery must show that expert review happened before the output was sent.
- The client needs a defensible final deliverable.
- The expert made corrections or accepted responsibility for the result.
- The delivery should be verifiable later through a content hash or receipt.
What is recorded
The protocol records the mission, the final deliverable hash, the review status, the expert identity, and the supervision evidence that can be shown to a client.
What it does not prove
It does not claim the machine was always correct. It proves the delivery passed through a human supervision boundary before it was finalized.
Terminal command
temet mission <mission_id> close --deliverable ./delivery.mdJSON shape
{
"type": "mission.delivery.certificate",
"missionId": "mis_01",
"expertAddress": "22cd91b5de1fdc50",
"deliverable": {
"sha256": "5f6d4f5d4d1c2e5a6f2d9c3b8f3c1e0f9a7b6c5d4e3f2a1b0c9d8e7f6a5b4c3d",
"mediaType": "text/markdown"
},
"supervision": {
"status": "reviewed",
"expertEdits": 12,
"auditDurationSeconds": 840,
"finalDecision": "approved"
}
}Sample response
{
"status": "delivered",
"receipt": {
"id": "rcpt_01",
"hash": "receipt_hash",
"prevHash": "previous_receipt_hash"
}
}Related surfaces