Knowledge Hub

The path you follow

Work through the hub in this order. You can stop after approval and never publish.

1. Add a source.
2. Wait for candidate facts to be extracted.
3. Review each candidate and its provenance.
4. Resolve conflicts. Do not let the product pick a value in silence.
5. Approve or reject.
6. Generate a document or a machine-readable copy if you need one.
7. Publish only if you explicitly opt in.
8. When a source changes, review the affected facts again.

Overview

Knowledge→Overview

Overview shows whether sources are still being read, how many facts wait for a person, and whether publishing is off. Start here after you add a source so you know the hub is still private.

Sources

Knowledge→Sources

1. Open Knowledge → Sources.
2. Add website content, a manual, a product document, an approved file, or a catalog when that profile fits.
3. Wait until extraction finishes. A candidate is not yet a verified fact.

Provenance

The source passage a candidate came from. Open it before you approve.

Facts

Knowledge→Facts

Facts lists claims under review. Open a row, read the provenance, then approve or reject. Reject a candidate that is not the company position. Approval stores the fact for Basiro workflows. It does not put the fact on a public page.

Products

Knowledge→Products

Products holds catalog-style product information when that profile fits. It does not replace Answer Accuracy, and it is not the visitor-facing site assistant. Approve a product fact the same way you approve any other fact.

Documents

Knowledge→Documents

Documents are generated for a person to read, and some copies are machine-readable. Generate one after the facts you need are approved. A document is a copy. The customer's website remains the official source.

Conflicts

Knowledge→Conflicts

Open Knowledge → Conflicts when two sources disagree. Basiro must not silently pick one value. A person resolves the conflict, and that choice becomes the fact you can approve.

Publishing

Knowledge→Publishing

Publishing is off unless someone with permission turns it on. Open Knowledge → Publishing only when you intend to make a copy public. The customer's website remains the canonical authority. GitHub can be one optional destination later. It is not the product.

Changes

Knowledge→Changes

Changes keeps a record of what a person reviewed. When an original source changes, affected facts are marked for another review. That is source drift, not an automatic rewrite and not an automatic publication.

What you have when you stop

You have a private, reviewed set of facts. Visibility, accuracy and remediation can use that set without making it public. Next, compare a live answer on AI answers → Truth, or open To do if a claim is wrong.

What this does not prove

• An approved fact is not a public page.
• A generated document is not proof that an answer engine cited you.
• Source drift does not rewrite or publish facts by itself.
• The site assistant's notes are not the Knowledge Hub.