Anatomy of a concept file

Every non-reserved OKF file is a concept: Markdown with YAML frontmatter that answers four questions - what is this, how does it relate, can I trust it, and when does it expire.

Minimal viable frontmatter

---
title: Deployment rollback policy
description: When and how production rollbacks are performed.
type: policy
tags:
  - deployments
status: stable
---

• type is free-form but required for concepts. It tells agents what kind of statement they are reading (policy, playbook, decision, reference).
• title and description are retrieval surface. Search indexes them; vague descriptions produce vague citations.
• status marks lifecycle: draft, stable, deprecated.

Fields that earn their keep

links connect related concepts so bundles form a graph instead of a pile. sources point at where the claim came from. verified records who confirmed the content and when. Omit them on throwaway notes; include them the moment anyone else will rely on the file.

Keep the body honest

One concept per file. If a document needs "and also", it wants a second file and a link. Short, single-purpose files retrieve cleanly and cite precisely.