FAQ

Where do notebooks, wikis, deals or invoices go?

In an extension. The core holds only what every organization has. A data platform writes its notebooks and wikis under extensions/data/, a CRM its deals under extensions/hub/, an ERP its invoices under its own folder, each with namespaced types.

Can I write an extension for my own system?

Yes, without asking anyone. Pick a namespace, write an EXTENSION.md, follow the same rules as the core (type always present, empty fields left out, relations as paths, no secrets) and list it in the manifest.

What happens to an extension my importer does not know?

It stays as it is. A reader that does not know an extension neither drops it nor rewrites it, so a bundle that passes through several systems keeps everything it came with.

Do I have to include the history?

No. COMMITS.md and HISTORY.md are optional. Without them a bundle is a snapshot, and an importer takes it as a creation by whoever imports it. See History.

Why paths and not ids?

Ids belong to the system that issued them; they mean nothing in the next one. A folder means the same thing in every system, and a person can follow it.

Are secrets ever in a bundle?

Never. Keys, tokens, passwords and sessions stay out, in the core and in every extension. A Connection can say which header carries a credential, never the credential.

Is a POF Skill an Agent Skill?

It has the same shape: a folder with a SKILL.md whose name and description tell an agent when to use it. See POF vs. MCP vs. Agent Skills.

Is this an official standard?

No. POF is a format with a working implementation behind it, offered so that more than one system can use the same shape.