Interactive v0.2 lab
Build an Attested Computation contract with a runtime, inputs, executor, expected receipt, and attester. This lab writes the contract. It does not execute or attest the calculation.
Concept preview
Contract, not result
Executor and attester are different. The executor runs the sanctioned computation and returns the declared receipt. The attester checks that the request and receipt satisfy your policy.
Add verified only after a real review. Use the trust metadata builder for that event.
Direct answer
An Attested Computation concept names the sanctioned runtime, accepted parameters, executor resource, expected receipt, and attester policy. A consumer can inspect that contract before asking another system to calculate a result.
Declare where the computation runs and the inputs the executor accepts.
List the evidence the executor must return after running the calculation.
Point to the separate policy or process that checks the request and receipt.
Contract fields follow the OKF v0.2 specification ↗. Guidance updated 2026-08-24.
Senior Engineer, Product Builder, and Founder
Systems, product software, and practical execution for teams that need clear decisions, durable implementation, and agent-ready knowledge structures.