Knowledge changes, but that should never erase who changed it, who approved it, or what came before. Curated Data versions each document independently, then makes an approved revision live immediately, without publishing an unrelated workspace bundle.

A company policy, metric definition, or source-system guide has its own lifecycle. Treating the entire knowledge base as one release couples unrelated work together: correcting one page would require rebuilding and publishing everything else. Per-document revisions keep the audit trail strong without adding that release bottleneck.

Approval publishes exactly one document

A change begins as a draft, moves into review, and becomes current when a reviewer approves it. That approval is the publication event. Authorized REST and MCP clients see the new revision on their next request; other documents remain exactly as they were.

Every revision keeps its identity

Revisions are numbered per document and record their author, change summary, review decision, reviewer, and timestamps. The document's stable path, for example policies/refunds.md, stays the same while its current approved revision advances. Prior revisions remain part of the history instead of being overwritten.

This gives reviewers a useful diff and gives operators a precise answer when someone asks what changed. It also keeps edits isolated: a pending update to the refund policy cannot hold back an approved correction to an analytics metric.

Agents only read current approved revisions

Retrieval never reads an author's open draft or a revision still waiting in the queue. Concept reads, search, and MCP tools all resolve through the same current-revision pointer and token classification checks. An agent therefore gets the latest reviewed content for each document, not the latest text someone happened to save.

What this model guarantees

• Approval makes one reviewed document live immediately.
• Unrelated documents are never republished as a side effect.
• Draft and in-review revisions remain unavailable to agents.
• Every document retains its numbered revision and approval history.
• A stable path gives integrations one identity across revisions.

Governance without release ceremony

Good governance should make the trustworthy action obvious, not make teams repeat it. Review is the meaningful gate: a named person examines a specific change and signs off. Publishing that same document at approval preserves the gate while removing a redundant whole-bundle workflow.