OKF (§4.2) defines the body as the standard markdown content following the frontmatter. The body is where prose, schemas, and examples live — content for humans and LLMs to read. Producers SHOULD favor structural markdown (headings, lists, tables, fenced code blocks) over freeform prose, since structure aids both human reading and agent retrieval. There are no required sections.

Conventional headings

When applicable, OKF recommends these headings so consumers can find common content predictably:

• # Schema — for a resource-bound concept, the asset's columns/fields (§4.3).
• # Examples — usage examples, often as fenced code blocks.
• # Computation — the sanctioned computation of an Attested Computation concept (§10).

These are conventions, not requirements. A concept with nothing to schematize simply omits # Schema.

Changed from v0.1. v0.1 listed # Citations as a conventional body heading. In v0.2 per-claim attribution to external sources uses markdown footnotes keyed to sources entries rather than a body citations list (§5.1) — see Provenance. # Computation is a new conventional heading. # Schema and # Examples are unchanged.

Resource-bound vs. abstract concepts

• Bound to a resource (§4.3) — the concept describes a concrete asset, carries a resource URI in frontmatter, and typically has a # Schema section. Example from the spec: a BigQuery Table with a schema table, join notes, and per-claim footnotes.
• Not bound to a resource (§4.4) — the concept is abstract (a playbook, a theme, an idea), has no resource, and structures its body however suits it. Example from the spec: a Playbook with trigger and steps sections. Every concept in this bundle is abstract.

Citations

1. OKF Specification (SPEC.md)