Truth + Governance (what OmniLore shows you)

OmniLore’s differentiator is not a prettier chat box. It is where answers come from and what tools may do.

Badges you should see (or agents should state)

| Badge | Meaning |
|-------|---------|
| Answer came from Disk SoT | Product/ops facts via product_answer / knowledge_answer / sot_get — not model memory alone. |
| Vector search was discovery only | Qdrant/similarity may help find docs; disk SoT revalidation is authority. Empty search ≠ “no docs.” |
| Tool used / tool denied | Agents must report which MCP tools ran and which gates denied them. |
| Mutation required permission | Writes need tier + confirm/gates. No silent changes to forge, tribal, or knowledge. |
| Private personal corpus | Your Drive/Gmail brain is not shared tribal and not product encyclopedia. |

How to ask product questions

1. Use OmniLore mode (Shared Operator / agents with fabric tools) — not raw Quick/Auto alone.
2. Ask “What is OmniLore?” / HOOTL / CoTrinity — agent should call product_answer first.
3. Expect Sources with disk paths when claims are made.

What OmniLore will not do

• Invent fabric definition when SoT is down
• Treat frontier web drafts as tribal truth
• Mix your private corpus into product SoT
• Run unrestricted shell or dual-envelope image authority

Operator tool

MCP: truth_governance_card — returns the badge pack for footers and UI.

LibreChat (Shared Operator)

Product answers should end with a visible markdown block:

Sources · Disk SoT

• List tools used with keys/paths from results
• Authority: disk_sot · vector_role: discovery_only

| State | Header |
|-------|--------|
| OK | Sources · Disk SoT |
| Frontier mixed | Sources · Disk SoT + frontier draft |
| Miss | Sources · SoT unavailable |
| Personal | Private personal corpus (not tribal / not product SoT) |

CoTrinity Chat shows the same trust states as a collapsible chip.