OKF Studio v0.8.0

Attested computations become usable rather than merely parsed, and retrieval starts preferring knowledge that has been reviewed and is still current.

A minor, not a patch. This release visibly reorders retrieval results and moves the exported retrieval manifest to schemaVersion 2, alongside five new features. A patch number would have understated all three.

Attested computations

An Attested Computation exists so a reported number can be traced to the query a business actually sanctions, rather than to an agent writing plausible SQL. That check now runs.

• The computation is visible. One stored in a file renders in the reading column under the same # Computation heading an inline one uses, so a reader cannot tell which form the producer chose.
• A run can be checked. The computation panel gains a Check a run… dialog: paste the receipt a run returned and Studio compares it against the bundle's copy. Required evidence fills in as you paste.
• An agent's claim is gated. A turn that ends with an okf-receipt fence is checked before its number is taken at face value, and the verdict renders beside the figure. The agent supplies only its receipt — what it is checked against is read from the bundle, because an agent that could supply both sides could always make them agree.

What Studio does not claim. It checks provenance: that what ran is the sanctioned computation with its parameters bound. It cannot check fidelity — re-reading the authoritative result by job id — because only the executor's runtime can, and it says so rather than implying a run was fully verified. Studio never executes a computation, an executor, or an attester.

Retrieval prefers reviewed, current knowledge

Retrieval reads OKF v0.2's status, stale_after, verified and sources, and marks rather than excludes.

A deprecated concept is ranked below current knowledge and carries a caveat saying so. Searching it by name still returns it first — OKF keeps deprecated concepts for links and history, and a retriever that hid them would break exactly what the status preserves. Human review and declared sources lift a concept over an otherwise identical peer; trust is a bonus and never a penalty, so bundles predating v0.2 are not punished for the spec moving.

Also

• The ACP SDK moves to 2.0. This is a Rust API change, not a wire change — nothing an agent negotiates is affected.
• A worked Attested Computation ships in Studio's own docs bundle, with its example receipt pinned by a test so it cannot rot.
• Fixes: retrieval treated a concept dated only by generated.at as undated; vitest run with no project filter ran nothing at all.

Upgrading

• Retrieval results will reorder for bundles declaring v0.2 lifecycle fields. Nothing is dropped; demoted items carry a caveat explaining why.
• The exported retrieval manifest is now schemaVersion 2. It gained fields; anything reading only v1 fields is unaffected.
• No change to ACP wire behaviour.

Installers for Windows (.msi, .exe) and Linux (.deb, .AppImage) are attached below, each with its update signature.

There is no macOS build: the release matrix has never included one. An earlier draft of these notes claimed otherwise, which was wrong.