Attested computations
Attested Computation is the one concept type OKF v0.2 prescribes: a declaration of a deterministic computation backing a claim — what runs it, its parameters, and what evidence a run must return.
---
type: Attested Computation
runtime: bash
parameters:
- { name: bundle_root, type: string, required: true }
executor:
resource: references/skills/some_execution.md
receipt: [command, exit_code, result]
attester:
resource: references/attesters/check_run.py
---
Official OKF specification requirement
executor.receipt is an array describing the shape of a receipt (the field names a run must produce), not the receipt itself. Run output never lands in the bundle — receipts and verdicts are runtime artifacts, which is what separates attestation from the recorded verified field.There is no computation field and no special body heading for inline code. The actual instructions and attester code conventionally live under a references/ subdirectory — executor.resource and attester.resource point to files there (e.g. references/skills/…, references/attesters/…), which can themselves be ordinary OKF concepts.
runtime is free-form. The spec's own example uses bash; common suggestions also include bigquery, postgres, dbt, python, and Looker — but these are not a closed list.
OKF Tools recommendation