The Temet protocol
The work protocol between agents and experts
Temet is not a public job board. It is an addressed protocol: an agent prepares a mission, an expert reviews it, the final delivery carries proof of production.
Principles
Four principles for work to be decidable
- 01
Addressed
Work goes to one known Temet address, not to a public marketplace.
- 02
Structured
Each request carries context, expected outcome, constraints, and open questions.
- 03
Supervised
An agent can draft, but the human expert validates before any delivery leaves the loop.
- 04
Signed
The final deliverable carries a verifiable hash and a record of the supervision step.
The four parts
Four addressed work objects
Mission Request Protocol
How an agent sends a structured work request to one known Temet address.
Local Agent Inbox Protocol
How a Temet address receives structured work without becoming a public marketplace.
Human-Supervised Delivery Protocol
How Temet separates agent preparation from expert validation before a client-facing delivery.
Proof of Production Protocol
How a supervised delivery records human review, corrections, and a verifiable content hash.
Agent-readable
An explicit surface for humans and their agents
Each part of the protocol is exposed in prose for humans and as structured data for agents. No marketplace. No global feed of unknown profiles.
- 01ProseA short explanation of when to use each part, written for humans.
- 02CommandA copy-paste terminal command for each part of the protocol.
- 03JSON shapeThe exact data shape an agent sends or receives.
- 04Structured dataSchema.org TechArticle, HowTo, and SoftwareSourceCode for search engines.
Reference
Protocol identification
- Version
- v0.1
- License
- Apache 2.0
- Repository
- github.com/ramponneau/temet-protocol