OKF starter pack — how to work here

This project was scaffolded to be conformant with Google's Open Knowledge Format (OKF) v0.1 from the first commit — markdown + YAML frontmatter, a standard-markdown link graph, and two reserved files. Conformance here is pre-populated, not enforced: OpenKnowledge's native frontmatter schema stays open-shaped, nothing is linted, and you are free to author however you like. This skill explains the conventions so the kit stays OKF-portable as it grows.

This skill is pack guidance. The platform open-knowledge skill (read/write/preview/linking/grounding rules) still governs every markdown operation — this layers the OKF conventions on top.

The one rule (keep the kit conformant)

OKF requires exactly one thing of every non-reserved document: a non-empty type in its frontmatter. That is the whole conformance contract for your content.

• The value is yours to choose — concept, reference, note, person, event, anything that fits. There is no blessed taxonomy.
• Document is a fine generic fallback when nothing more specific fits (it is just a non-empty value, not a special keyword).
• The folder templates already set a sensible type per section — create docs with write({ document: { path, template: "<name>" } }) and you inherit it.

Folders

• concepts/ — durable ideas and definitions, one file per concept (type: concept).
• references/ — external sources and citations you rely on (type: reference).
• notes/ — working notes and observations (type: note).