7. Exporting your knowledge (OKF)#

Any bundle of concepts — the built-in curated bundle (everything promoted via Curation), the built-in authored bundle (everything written via §10's trusted write-back), or a custom bundle name you've uploaded — can be exported as a portable OKF (Open Knowledge Format) tree: one Markdown file per concept plus a root index.md, packaged as a download.

Exports are OKF v0.2: each concept's frontmatter carries the v0.2 trust-signal vocabulary so trust travels with the knowledge — okf_version: 0.2, status (the lifecycle stage), generated (what produced it), verified (the human {by, at} promotion records, §4a), sources (lineage), stale_after (the re-verification date, §4b), and superseded_by (dedup lineage, §4c) when set.

• Settings → Export workspace: the Download export button grabs your entire workspace as an OKF .tar.gz — open format, no lock-in. The archive contains what you can see (group visibility applies).
• GET /v1/bundles/{name}/export downloads one bundle as a .tar.gz; add ?format=zip for a .zip. Same via API: GET /v1/export for the whole workspace (bundle-prefixed paths).
• GET /v1/bundles lists bundle names visible to the API key or member token, so external builders such as Forge Runs can offer a picker before targeting an export/import flow.
• The export honors your visibility: a restricted member's export never contains concepts outside their groups; an unrestricted workspace API key exports the whole bundle.
• Round-trip: an exported tree re-imports cleanly via PUT /v1/bundles/{name} — and import preserves unknown fields rather than dropping them, so a bundle that passed through another OKF-speaking tool survives the trip. Export is a safe way to snapshot, back up, or hand a bundle to another OKF-compatible tool.