Knowledge Bases

Correct once, use everywhere

Livealy — 06 / 07

Knowledge Bases

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

The Livealy Knowledge Base admin: 39 approved facts at version 7, zero waiting for review, an item open with its accepted versions, and the note that corrections never erase their source.

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.

A central cyan Knowledge Base sends approved information into five distinct website pages.

Repeated questions form clusters, trigger one owner message, and return through approval into knowledge.

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.

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.

One approved edit sends a cyan update pulse to four different page layouts.

Bring the source material

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

Request an invitation