OKF Studio v0.7.0

OKF Studio 0.7.0 supports OKF v0.2, the spec revision Google published on top of v0.1.

v0.1 answered "what does an agent need to know?" v0.2 adds "should the agent believe it, and is it still true?" Provenance, trust, and freshness stop being prose and become fields a consumer can compute over. Studio now reads all of it.

Your existing bundles keep working. v0.2 has two breaking changes and both keep a fallback, so a v0.1 bundle opens exactly as before — and validation stays quiet about fields it never declared rather than nagging you to migrate.

Whether to believe a concept

• The Concept Reader now shows a trust tier above the producer metadata: unverified, machine-confirmed, or human-reviewed. It is derived from who actually confirmed the concept, so a bundle cannot simply assert that it is trustworthy.
• Who wrote it and who confirmed it are separate. A concept generated by an agent and confirmed by nobody reads as unverified, however complete its provenance. That distinction is the point of v0.2, and collapsing it would hide the only signal separating reviewed knowledge from generated knowledge.
• Sources carry credibility signals — who produced a source, how often it was used over what window, and when the source itself last changed. A usage count is always shown with its period, because 5,000 uses over a week and over five years mean opposite things.

Whether it is still true

• A concept past its stale_after date says so, and a deprecated one says that instead — they are different claims, so they read differently.
• Knowledge Health gains findings for a concept past its staleness date, and for a current concept that links to deprecated knowledge, which is how a reader arrives at retired material without being told.
• Freshness now reads v0.2's generated.at as well as v0.1's timestamp, so a migrated bundle is no longer reported as undated for having adopted the newer field.

Attested computations

v0.2 adds a concept type for a sanctioned computation, so a consumer can check that a reported number came from the blessed query rather than from an agent writing plausible SQL. Studio reads and validates these contracts, and reports one that cannot gate anything — no runtime, no receipt fields, no attester.

Running an attestation is not wired up yet. Studio can compare a run's executed query against the stored computation without executing anything, and that check is built and tested, but nothing yet lets you invoke it. Tracked in #28.

For agents

The OKF methods Studio serves to agents are updated to v0.2, including two new ones: attest for defining a computation an agent may run but not write, and migrate for moving a bundle from v0.1.

Fixes

• A sidecar's digest check reported tampering on an untouched file on Windows, because the checkout rewrote the file's line endings and changed the bytes the digest covers.
• Component status stopped rendering in design-system bundles.
• Buttons that look like links rendered unstyled in the sidebar and type filters in some views.
• A source link in the reader opened inside the app window instead of your browser.

Notes

Screenshots on the download page still show 0.5.0's appearance and will be refreshed separately.