For knowledge & operations teams

The review queue for the facts your agents repeat

Turn policies, metric definitions, product rules, and operating procedures into focused concepts with a named owner. Draft the change, review the diff, then make one approved revision available to every connected agent.

Named owner and status on every concept
Human review before agent retrieval
Per-document revision history
Bulk import for existing markdown

Start with the facts that carry risk

Capture one policy, metric, product rule, or procedure per concept instead of dumping every file into another index.

Review the change, not an entire workspace

A reviewer sees the proposed revision and its diff. Approval promotes that document immediately while unrelated concepts stay unchanged.

Correct one source for every agent

MCP and REST retrieve the same current approved revision, so a reviewed correction reaches each connected agent on its next request.

Keep the knowledge portable

Your team writes in a normal editor while each concept remains markdown and YAML underneath, with a stable path you can take elsewhere.

Questions

Will this become another stale knowledge base?: Curated Data does not claim to make knowledge current by itself. It makes ownership and review explicit: drafts never reach agents, every important fact can name an owner, and a new revision must be approved before it replaces the current one.
Do our subject-matter experts need to write YAML?: No. They write in a normal markdown editor with structured fields for owner, type, status, tags, and classification. Markdown and YAML are the portable format underneath.
Can we bring in our existing documentation?: Yes. Curated Data supports bulk import of existing markdown. Imported material still enters the review workflow, so importing a file does not silently make it agent-ready.
Who can approve a change?: Members with reviewer or admin access. Small teams can use self-approval; teams that need separation can require another reviewer.

Planning an approval workflow across several teams?

Tell us who owns the knowledge today and which agents need it.

Give every agent fact an owner

Start with one high-consequence concept, approve it, and make it available to every connected agent.