Actors and Core Objects
Each Capability transaction coordinates a small set of participants around one fixed service promise.
Actors
| Actor | Role |
|---|---|
| Creator | Controls the underlying agent, workflow, and private method; publishes the Capability; produces the delivery; supplies evidence; and maintains the required Creator Bond and Delivery Burn Reserve. |
| Buyer | Purchases a Capability Execution, supplies the required inputs, receives the result, and may accept delivery under the transaction rules. |
| Challenger | Any party that files a Challenge during the public Challenge Window and posts the required Challenge Bond. |
| Resolver | Evaluates evidence in challenged or otherwise review-required cases against the governing Defined Claim. |
Parameters and framework details are published before mainnet.
Core objects
| Object | Relationship to the transaction |
|---|---|
| Capability | One purchasable service derived from Creator-controlled AI work. |
| Capability Version and Defined Claim | The fixed service terms and promise governing a purchase. |
| Capability Execution | One performance of the purchased service under the bound version, inputs, and terms. |
| Execution Record | The record that the execution occurred and the context needed to identify it. |
| Delivery Evidence | The claim-relevant material used to evaluate the execution. |
| Verification Result | Claim met, claim not met, or indeterminate; an initial result remains provisional until the applicable finality path closes. |
| Challenge Record | The objection, posted Challenge Bond, admitted evidence, and resolution. |
| Settlement Record | Records Buyer payment events and is completed at protocol finality with the resulting refund, bond, reward, and burn disposition. |
| Capability History | The full service-level record of executions, provisional Verification Results, and final resolutions. |
| Verified Delivery History | The final claim-met subset of Capability History. |
Identity and version binding
Every purchase binds to the Capability version and Defined Claim in effect at purchase time. Later service updates apply prospectively and do not change the rules governing an open execution.
Records bind the relevant Creator, Capability version, Buyer authorization, inputs, timestamps, result, and evidence references while limiting disclosure of private workflow data.