> ## Documentation Index
> Fetch the complete documentation index at: https://anam.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Knowledge upload checklist

> Follow these steps to release a knowledge update: prepare the files, upload and confirm processing, then verify passages and persona answers.

Follow these steps whether you are uploading documents for the first time or replacing existing ones. The last three matter most: an upload that completes successfully tells you nothing about whether the persona now answers correctly.

<Steps>
  <Step title="Choose the exact files">
    Select the approved files individually rather than uploading a whole working folder. Check that drafts, superseded revisions, prompts, test transcripts, and anything inappropriate for this persona's audience are not among them.

    Keep the originals, and a copy of the persona's current configuration, somewhere outside the active knowledge folders so you can roll back.
  </Step>

  <Step title="Check each file reads correctly on its own">
    Open each file and confirm that conditions, exceptions, and source details sit beside the facts they qualify, that tables keep their units and row labels, and that procedures keep their prerequisites and order.

    Where two sources disagree, resolve the conflict or state plainly what is unconfirmed. See [Prepare documents](/docs/personas/knowledge/preparing-documents) for worked examples.
  </Step>

  <Step title="Confirm which folders the persona will search">
    Check every knowledge tool attached to the persona, not just the one you are changing — a second tool can still reach material you meant to exclude. See [Set the knowledge scope](/docs/personas/knowledge/setup#set-the-knowledge-scope).
  </Step>

  <Step title="Upload and wait for READY">
    [Upload the files](/docs/personas/knowledge/uploading-documents) and record the document ID each one returns. Confirming an upload only queues it for indexing, so wait for each document to reach `READY` before testing anything.

    <Check>
      Every document you uploaded reports `READY`, and none report `FAILED`.
    </Check>
  </Step>

  <Step title="Retire the versions you replaced">
    Skip this step for a first upload.

    Delete the superseded documents, then list the folder's documents and confirm the old IDs are gone and the new ones are present. Uploading a revised file does not retire the old one. See [Replace an existing document](/docs/personas/knowledge/uploading-documents#replace-an-existing-document).
  </Step>

  <Step title="Search for a fact you changed">
    Pick a distinctive fact from the middle of a document — not the opening paragraph — and [search the folder for it](/docs/personas/knowledge/testing#inspect-retrieved-passages).

    Read the passage that comes back: does it name its subject and scope, and does its `documentId` match the file you just uploaded? If a superseded ID still appears, return to the previous step.
  </Step>

  <Step title="Test the conversation, not just the search">
    Start a fresh persona session and ask the questions a user would. Compare each answer against the source text rather than against your memory of it.

    Include the cases that break weak knowledge bases: a detail your documents do not contain, a rule with an exception, and a question where the user changes the context mid-conversation. See [Test your knowledge base](/docs/personas/knowledge/testing#test-persona-answers).
  </Step>

  <Step title="Repeat the cases that matter">
    Run the important questions again in a new session, with the same wording and the same persona settings. One correct answer does not establish that the next one will be.

    Record the failures alongside the passes — a case that fails intermittently is the one worth investigating.
  </Step>
</Steps>

## If a check fails

Correct the release, or restore the previous set of files and persona settings from the copies you kept, and then run the verification steps again. Restore the whole set rather than individual pieces: a folder holding new documents alongside an old persona configuration is harder to reason about than either version on its own.

If retrieval looks right but the answer is still wrong, the problem is usually the persona's prompt or tool instructions rather than the documents. [Diagnose a failed check](/docs/personas/knowledge/testing#diagnose-a-failed-check) covers how to tell those apart.