> 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/knowledge.md).

# Knowledge and pages

The **Knowledge** tab is the starting point for a Brain's Wiki pages and facts. Reading a page requires Brain read access, but does not require selecting a Q\&A alias.

## Find and read a page

1. Open **Brains**, select the Brain, and choose **Knowledge**.
2. Use **Pages** to browse available Wiki pages. The landing also offers **Facts**, **Add fact** and **Upload sources**, subject to your permissions.
3. Open a page to enter the Wiki reader.
4. Use the reader's navigation to search loaded files or load more. Searching the loaded list is not a search of every possible page or source document.
5. Read the page alongside its reported metadata, active facts and history context.

**Authored** and **Generated** describe the reported narrative mode. A missing mode or date is unknown, not proof that the page is generated or has never changed. Source freshness and GitHub export freshness are separate from the page's committed content.

The Knowledge landing does **not** offer **New page**. The reader supports editing an existing selected page, not creating a new page from that entry point. Do not look for page creation by opening the landing's fact controls.

## Before editing

You need current contribution permission, a readable selected page with revision and commit information, and an enabled [Q\&A agent](https://docs.katara.ai/about/agents-and-answering/qna.md) bound to this exact Brain. The editor calls that Q\&A agent an **alias**. The Brain identifier itself is not an alias.

Editing generated prose has an important consequence: even a small prose change makes the entire narrative **Authored** and manually maintained. Source refresh will no longer update that narrative, and there is no return-to-generated action in this workflow. An unchanged save does not transfer narrative ownership.

## Edit an existing page

1. In the Wiki reader, choose **Edit page**.
2. Explicitly choose or enter the authorized Brain-backed Q\&A alias and select **Validate this Brain alias**. Confirm validation succeeds for this Brain.
3. Use **Load canonical page** to verify the page against its current revision. Follow any request to verify the selected page's canonical slug; do not substitute another page or use creation as a fallback.
4. Edit **Editable Markdown draft**. Only editable frontmatter and narrative belong in this field. Managed facts, generated indexes, server metadata and timeline/history are protected; use [fact management](https://docs.katara.ai/about/brains/facts.md) for fact corrections.
5. Select **Save checked revision** and review any authored-narrative or empty-content confirmation.
6. Check the committed result and refreshed canonical read. Saving is separate from search indexing and export, and does not clear source staleness.

Clearing narrative is not deleting the page. Its identity, metadata, facts and history remain and may still support answers. Generated prose becomes authored and refresh will not repopulate it. There is no force, reset, rename or delete-page control here.

## Resolve conflicts and uncertain saves

If another change wins first, the editor preserves your draft. Choose **Load latest separately**, compare the latest content, then explicitly reapply your draft onto that revision or choose **Use latest content instead**. Review again before saving; the editor does not silently merge or overwrite.

For an uncertain save, use **Retry original save** rather than creating a new request. If persistence succeeded but reading the result failed, use **Retry canonical read only**; do not resubmit the write.

Closing the contextual sheet can retain drafts during the same visit, but this is not durable draft storage. Switching aliases, organizations or authority can invalidate the workflow. If editing disappears, recheck current access and the selected page rather than assuming the original permissions still apply.
