Knowledge Bases

Approved knowledge belongs to the organization — not to a page, a prompt or a renderer.

01

One approved authority

An organization can link several websites, docs sites and decks to one Knowledge Base, while each product keeps its own pages, brand, files, media and settings. Approved items compile into one immutable snapshot. A generation pins the exact version it received, so an answer cannot drift halfway through.

02

Evidence before acceptance

Material suggested by files, public links, replies, insights or authorized agents stays a proposal until a person accepts it. The original evidence and the proposal both remain in history. A correction writes a new immutable revision instead of overwriting the old one, and a stale edit can never replace a newer approved revision.

03

Pages remain pages

Publishing a page does not silently turn every sentence on it into organization-wide truth. A knowledge change can prompt a page review without seizing that page's own editorial authority.

Bring the source material

Rough notes are fine. The structure is our job, not yours.