A concept document (or concept) is a single unit of knowledge in a knowledge bundle: a UTF-8 markdown file with a YAML frontmatter block followed by a markdown body. Every .md file in a bundle is a concept document except the reserved index.md and log.md.

Every file you are reading in this bundle's concepts/, spec/, operations/, implementations/, and references/ directories is a concept document.

Concept ID

A concept's identifier is its file path within the bundle with the .md extension removed. For example, this file's concept ID is concepts/concept_document. Concept IDs are how concepts are referenced and how cross-links resolve.

Anatomy

• Frontmatter — machine-readable metadata. Only type is required; title, description, resource, and tags are recommended, and OKF v0.2 adds optional provenance/trust/lifecycle families (sources, generated, verified, status, stale_after).
• Body — human- and agent-readable markdown prose, with conventional headings such as # Schema, # Examples, and # Computation when applicable. See Body. Per-claim provenance uses footnotes keyed to sources entries in v0.2 (superseding v0.1's # Citations body list).

A concept may be bound to a resource (e.g. a database table, with a resource URI) or abstract (e.g. a playbook or, as here, an idea) with no resource. Every concept in this bundle is abstract.

Citations

1. OKF Specification (SPEC.md)