Skip to main content
Exports the project as an Open Knowledge Format bundle (OKF v0.1): a directory of typed markdown files with YAML frontmatter, relationships as ordinary markdown links. The brain’s node model maps almost one-to-one onto OKF’s typed-concept graph, so an OKF-aware agent reads it with no translation layer. This is a third agent-legible surface alongside GET /nodes (JSON) and the MCP server.

Response

files maps each bundle path to its markdown content. Write each one to disk to materialise the directory.
  • One concept file per node, organised by type: goals/<id>.md, needs/<id>.md, approaches/<id>.md, jobs/<id>.md, tasks/<id>.md. The filename is the concept ID.
  • Frontmatter: the one required OKF field type (Goal, Need, Approach, Job, Task), plus title, description, timestamp (the node’s createdAt), and the node’s type-specific fields (status, maturity, kano, size, approachStatus, iteration, measure, kind, urgent) as custom keys.
  • Relationships are markdown links named in prose: parent, blockedBy, and children link to other concept files, for example [label](/needs/need-1.md).
  • A root index.md declares okf_version: "0.1" and lists every concept by type.
Access follows the read endpoints: owners and members, 403 project_access_denied otherwise, 400 for an unknown project.