Known-good example

A small v0.2 bundle you can inspect and break.

The archive contains human-reviewed, machine-confirmed, deprecated, stale, and attested concepts. The company and policies are fictional. The file structures are valid OKF v0.2 examples.

Download ZIP Validate after editing

Coverage

One bundle, several consumer decisions.

Each file exists to demonstrate a distinct part of v0.2 rather than imitate a complete company knowledge base.

Human-reviewed policy

A human producer and human verifier produce the highest derived trust tier.

Machine-confirmed metric

A deterministic process verifies the metric, so the trust tier remains machine-confirmed.

Deprecated and stale policy

The old definition stays linkable while status and stale_after prevent accidental reuse.

Keyed provenance

Source IDs connect individual Markdown claims to the sources frontmatter list.

Attested computation

The computation declares runtime, parameters, executor receipt, and deterministic attester resources.

Reserved files

The root index declares v0.2 and the log uses newest-first ISO date headings.

Archive contents

Eight readable files.

No database or runtime ships in the ZIP. The executor and attester documents define interfaces for the example computation. They do not execute code.

Reference bundle

okf-v0.2-reference/
|-- index.md
|-- log.md
|-- metrics/recognized-revenue.md
|-- computations/revenue-fiscal-year.md
|-- policies/revenue-recognition.md
|-- policies/revenue-legacy.md
|-- references/run-bigquery.md
`-- references/check-sql.md

Suggested exercise

Remove a source resource, duplicate an ID, or corrupt a verification event.

Upload the edited folder to the validator and compare the advisory findings with the three blocking conformance rules.

Download bundle

Direct answer

Use the bundle to test consumer decisions, not business logic.

The archive is a compact interoperability fixture. It shows how a consumer can distinguish human-reviewed, machine-confirmed, deprecated, stale, and attested concepts while following keyed source citations and ordinary Markdown links.

The company, revenue policy, executor, and attester are fictional. The ZIP does not prove that its calculation is correct and does not provide production security policy. Break the files, run the validator, and compare the findings with the specification.

Structure checked against the OKF v0.2 specification ↗. Example updated 2026-08-24.