Living knowledge base
Every fact has a source, an owner and a last-verified date. Facts move from draft to published with version history and rollback, and changing one never needs a deploy.
Two layers#
Each project has its own knowledge base, plus a shared company layer that applies to every project. A project can exclude the company layer. When both layers match a pricing question, the project entry wins.
Draft, publish, retire#
Entries move through draft, review, published and retired. Only published entries are retrieved. Every change is a version you can roll back in one click.
Freshness guard#
Entries past their review window are flagged. Pricing entries are hidden from the agent once stale, and a project can choose to hide every stale entry.
Loaders: sitemaps and transcripts#
Besides manual entries, you can crawl a sitemap (same site only, with scheduled re-crawls, and changed pages flagged for review) or import video transcripts as .txt, .srt or .vtt. Imported content arrives as drafts, so a person still publishes it. Seed files in JSON can load a whole knowledge base at once, which is how this website's chat is set up.