Wiki
Check the business knowledge Jarvis uses, together with its source and freshness.
In one sentence
The Wiki is the business memory Jarvis can use and show back to you.

What belongs here
Wiki pages can describe customers, suppliers, items, processes, and exceptions. They grow from Business Notes, reviewed learning, and facts captured during work. You can also create and edit a page yourself. A page has a type and belongs to the company, a role, or one user.
Find and check a page
- Open Skills, then Wiki.
- Search by a customer, supplier, item, process, or exception.
- Narrow by who the knowledge belongs to, such as you, a role, or the company.
- Use the view, filters, and Sort control to separate active, stale, conflicting, or archived pages.
- Open the page and read the latest source.
- Correct it, request a wider audience, archive it, or delete it when needed.
The knowledge graph may also be available. It shows how pages are related, such as a customer connected to a pricing exception and a responsible account manager.
Administrators can choose the knowledge language, ask for an immediate sync to the Agent, and run a Wiki health check. Original language keeps each source’s language. Read the last-sync and last-health-check status before assuming a recent change is already available everywhere.
Read the trust signals
- Latest source tells you where the fact came from and when.
- Conflicting means the page contains facts that do not agree.
- Stale means the fact has not been confirmed recently.
- Archived pages stay in history but should no longer guide new answers.
Delete only when the page must be removed permanently. Archive when you want to keep the history.
Share knowledge at the right level
Personal knowledge can be useful without being correct for everyone. Request promotion when a personal page should become role or company knowledge. A reviewer checks the evidence before widening it. The health check and review queues help administrators find stale, conflicting, or pending knowledge.
Archived pages can be restored. Permanent delete removes the page and should be reserved for knowledge that must not remain. Open the source list before removing anything whose history may matter.
A real example
Acme Retail was promised delivery only on Tuesdays because their warehouse is closed on Mondays. The promise came from a sales call, not an order field. A Wiki page keeps the exception, its source, and its owner where the sales and dispatch teams can find it.
The Wiki helps Jarvis remember. It does not replace the official amount, stock level, or status stored in your business records.