> For the complete documentation index, see [llms.txt](https://docs.katara.ai/about/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.katara.ai/about/brains/facts.md).

# Facts and memory

Facts add explicit, attributed knowledge to a Brain without editing a page's narrative. Use them for a statement that needs its own provenance, expiry or correction history.

The contribution interface uses **WORLD** to describe these facts. It does not mean publicly available on the internet: Personal Brain facts are visible to the current owner, while Team Brain facts are visible to authorized Brain readers. Someone who can view only a separately shared original document does not gain fact access.

## Before you start

You need current Brain contribution permission and an enabled [Q\&A agent](https://docs.katara.ai/about/agents-and-answering/qna.md) bound to this exact Brain. The fact workbench calls that agent an alias. It must be explicitly validated; neither the Brain's own identifier nor the literal `default` is a substitute.

Review the Brain's audience and export disclosure before writing. Facts or material derived from them can remain in committed Wiki history and [GitHub exports](https://docs.katara.ai/about/brains/github-export.md) after withdrawal or expiry. Do not contribute secrets on the assumption that later deletion will recall external copies.

## Add a fact

1. Open the Brain's **Knowledge** tab and choose **Add fact**. From a selected Wiki page, authorized contributors can also use **Manage facts**.
2. Select an authorized Brain-backed Q\&A alias, or enter its concrete identifier, and choose **Validate this Brain alias**.
3. Wait for confirmation that it is an enabled alias bound to this Brain.
4. Enter the statement in **Fact**. Keep it specific enough to evaluate and correct independently.
5. Fill in **Attribution / provenance (required)** with the source or basis for the statement.
6. Optionally provide an **Entity slug**. Only eligible existing entity pages can have facts attached; typing a new slug does not create an entity page.
7. Optionally set **TTL** using an accepted duration or supported date. Resolve any validation error before submission rather than assuming an arbitrary date format is accepted.
8. Choose **Contribute WORLD fact** and check for a committed result.

Use **Load active WORLD facts** to inspect current contributions. This returns a bounded list of up to 100 active facts, not a complete inventory or full history. A missing fact in that list alone does not prove it was erased.

## Correct a fact

1. Load active facts and choose **Correct fact** on the intended entry.
2. Review the existing statement and provenance, then edit the required fields and any optional entity or expiry information.
3. Select **Commit replacement, then retire original**.
4. Review the confirmation: the replacement is committed first; retirement of the original is a separate step.
5. Check the final result. If retirement fails after the replacement commits, both may remain active. Use **Retry unfinished retirement only** rather than contributing the replacement again.

An accepted replacement is not rolled back if retirement fails. If the interface offers **Keep replacement without retirement**, that leaves the correction incomplete; it does not mean the original was withdrawn.

## Understand history and failures

Inactive, withdrawn, superseded or expired rows are historical context, not active answer evidence. Withdrawal does not erase previous narrative or exported history. For tool-based withdrawal, see [MCP tools](https://docs.katara.ai/about/connect-ai-clients/tools.md); do not assume this dashboard offers a separate general-purpose delete button.

An uncertain contribution can offer **Retry original contribution**, preserving the original request. A definite rejection requires repairing the issue before starting a new intent. Losing contribution permission blocks further writes even if a draft remains visible. Revalidate the alias after access or target changes; switching aliases can close local page and fact drafts.
