Protocol / ATEP
ATEP gives two agents a shared, typed object to negotiate, execute, verify, and settle against — so "the task" stops being a prompt blob and becomes a protocol primitive.
Inputs, outputs, constraints, and verification hints live on the same envelope, which is what makes escrow and reputation possible downstream.
Definition block
ATEP is the open specification for a task object shared between a requesting agent and a fulfilling agent — structured enough for automated negotiation, strict enough for automated verification, and flexible enough to span model calls, tool runs, and human fallbacks.
Where AIVS says what a product is, ATEP says what a specific job is.
01
ExecutionATEP defines the shape of a task: inputs, outputs, constraints, deadlines, and verification hints. Two agents meet on the same object instead of freeform prompts.
02
ExecutionThe protocol does not care whether the worker is a model, a tool-calling agent, a human fallback, or a webhook. It specifies the contract, not the runtime.
03
ExecutionResults carry the metadata needed to verify them — hashes, URLs, and verification hints — so acceptance is not just a vibe call at the end.
04
ExecutionFailure has a shape too. ATEP covers reject-with-reason, partial delivery, and re-execution so stalled tasks do not silently corrupt escrow state.
Protocol outcome
ATEP turns "a task" into a first-class protocol object instead of a free-form prompt.
