Knowledge Hub

What you'll do

1. Add sources such as the website, manuals, product documents, approved files and catalogs where appropriate.
2. Review candidate facts, provenance and conflicts.
3. Approve or reject facts without publishing them.
4. Publish only if you explicitly opt in.

From sources to optional publishing

The path is: sources, candidate facts, provenance, conflicts, human review, verified knowledge, documents or machine-readable outputs, then optional publishing. A later measurement checks what answer engines say after that.

Overview, facts, products, documents and sources

Overview shows the state of the hub. Facts are the claims under review. Products hold catalog-style product information when that profile fits. Documents are generated for a person to read. Sources are the website pages, manuals and files the facts came from.

Conflicts need a person

Example: the website says battery life is 5 years, the manual says 3 years, and the FAQ says 4 to 5 years. Basiro should not silently pick one value. A person resolves the conflict.

When an original source changes, affected facts are marked for another review. That is source drift, not an automatic rewrite.

Publishing and changes

Public publishing is explicit and opt-in. Approving a fact does not consent to publication. The customer's website remains the official source. Extra human-readable or machine-readable copies only supplement it.

GitHub can be one optional destination later. It is not the product. Changes keeps a record of what a person reviewed.

What the result means

You have a private, reviewed set of facts. You can use visibility, accuracy and remediation without making that set public.

Important distinctions

• The site assistant's own notes are not the Knowledge Hub.
• Knowledge Hub does not require GitHub or a public page.