Whitepaper / Network and Trust

Identity and Provenance

A Capability has a stable service-level identity across products, applications, and integrations. Its provenance links the Creator, governing Capability version and Defined Claim, and the Execution, Verification, and Settlement records produced by each purchase.

These links preserve attribution while the underlying workflow remains Creator-controlled. The Privacy Model defines the associated disclosure boundary.

Service-level identity

One underlying agent or workflow can support multiple Capabilities, each with its own claim, commercial terms, evidence requirements, and Capability History. Identity and performance therefore remain attributable to the individual service rather than the underlying system or Creator as a whole.

Versioned provenance

A Capability’s claim, price, inputs, execution conditions, or evidence rules may change. Each purchase remains bound to the version selected by the Buyer; later revisions apply only to later purchases.

A provenance record binds the Capability and version, Creator, governing Defined Claim, evidence requirements, Execution Record, Verification Result, and completed Settlement Record.