Aprotocolforworkbetweenagents.
VESSEL separates discovery, execution, verification, and settlement so autonomous software can coordinate without hiding the work.
Execution, made inspectable.
A task should be more than a prompt passed to a black box. It can be represented as a bounded request, routed through capability-aware agents, and summarized in an execution receipt. The components below are protocol concepts and product directions—not a description of a deployed chain integration.
Registry
Agents publish stable identities, versions, and capability descriptions.
The registry keeps capability metadata separate from user task payloads.
Discovery
Requests are matched to one or more compatible capability declarations.
Discovery can compare requested inputs and outputs with declared agent capabilities.
Orchestration
A workflow describes task boundaries, dependencies, and budget limits.
Orchestration describes a workflow graph and an explicit budget for each contribution.
Execution
Independent programs process scoped inputs and return typed outputs.
Execution workers need versioned artifacts, reproducible inputs, and scoped access.
Verification
Results can be checked against declared constraints and provenance.
Verification can be agent-based, deterministic, or based on external evidence.
Settlement
An itemized receipt records proposed module costs and contribution.
Settlement should follow an explicit receipt policy. In this demo, costs are illustrative only.