CertSafari
    Anthropic Claude Certified Associate – Foundations (CCAO-F)· Lessons

    Domain 5 · Lesson 23/30

    Maintaining Claude projects: stale knowledge, instructions and archiving

    Inform, maintain, and update Claude configurations, knowledge sources, and instructions

    15 min read
    3% of exam
    5 sources
    Published 20 Oct 2026
    Docs as of 14 Oct 2026

    What you will be able to do

    • Explain why a project that was configured correctly starts giving outdated answers, and trace a wrong answer back to a file or instruction
    • Replace or remove outdated project knowledge so superseded versions stop shaping answers
    • Move a correction you keep repeating in chat into the project instructions
    • Identify who on a shared project has permission to change its knowledge and instructions
    • Choose between archiving and deleting a finished project, and say what each one keeps

    Key concept

    Stale project configuration — A project's knowledge files and instructions shape every chat in it, and they stay exactly as you left them. When the real policy, price list or template changes but the project doesn't, Claude gives confident answers that match the old material.

    1.Why a configured project drifts out of date

    A project gets old in a way a single chat doesn't. Its knowledge base and instructions load into every chat you start in it, so one file uploaded in January keeps shaping answers in October. The project has no way to know the benefits handbook was rewritten, the discount tiers were retired, or the report template was replaced. It works from what is in the knowledge base.

    This is why a stale file causes so much trouble. Suppose a benefits administrator uploaded last year's policy handbook. Claude quotes the old deductible clearly and with confidence, because that figure really is in the source it was given. Asking the question five different ways doesn't help. Every version of the question goes to the same handbook and gets the same outdated figure back. Rewording a question can fix a misunderstood request, but it can't fix wrong data.

    Document length isn't the cause either. On paid plans, a project whose knowledge grows large switches to retrieval-augmented generation (RAG) and keeps working. It doesn't read the first pages and drop the rest. A long handbook gets searched. An outdated handbook gets quoted.

    Checkpoint 1 of 9· Check yourself

    A benefits administrator set up a Claude project in January and uploaded the policy handbook. In October, Claude keeps quoting a deductible that was changed months ago. The administrator has asked the question five different ways and gets the same figure every time. What should they do first?

    Checkpoint 2 of 9· Exam question

    A benefits administrator keeps last year's policy handbook in a project's knowledge base. Claude keeps quoting the old deductible, and the administrator has now rewritten the question five different ways. What is the greatest concern here?

    Sources12

    2.Tracing a wrong answer to its source

    A project has three places a wrong answer can come from: the knowledge base, the project instructions, and the chat you are in. They persist differently. Knowledge and instructions apply to every chat. What you say in one chat stays in that chat. Knowing which layer holds the error tells you where to fix it.

    When a specific fact is wrong, such as a price, a deductible or a date, check the knowledge base first. Open the project's files and look for the retired price list or last year's handbook. That check takes a minute and usually finds the problem. Other fixes miss it. A fresh chat reloads the same files. Asking Claude to search the web brings in a second source without removing the wrong one. Adding a line to the instructions saying that all prices are provisional makes every answer vaguer and leaves the outdated file in place.

    Where a recurring problem lives, and where to fix it
    SymptomMost likely sourceFix
    A specific fact is out of date (price, limit, policy rule)An outdated file in the project knowledge baseReplace or remove the file
    Tone, format or template is wrong in every chatProject instructions that are missing or out of dateEdit the project instructions
    A correction you made yesterday is ignored todayThe correction lived only in the earlier chatMove it into the instructions or the knowledge base

    Checkpoint 3 of 9· Match them up

    Match each recurring problem in a project to the fix that addresses where it actually lives.

    Tap a term, then the definition that fits it.

    Checkpoint 4 of 9· Exam question

    A pricing analyst notices Claude quoting a discount tier that was retired at the last price review. What should the analyst do first?

    Sources1

    3.Adding, replacing and pruning project knowledge

    Uploading a new version doesn't remove the old one. If a team adds this year's travel policy and leaves last year's in the knowledge base, Claude has both and can draw on either. Nothing marks one as superseded, so Claude may cite the old rules, and nobody notices unless they compare the answer with the policy. The project doesn't reject the duplicate or archive the older file. It keeps both.

    When a new reference document is issued, follow these steps in order:

    1. Remove the version it replaces from the project knowledge.
    2. Upload the new document.
    3. Read the project instructions for anything that names the old document or its rules, and update it.
    4. Ask a question whose answer changed between versions, and confirm Claude gives the new answer.

    Old versions aren't the only cause. A knowledge base that dozens of people have added to over time ends up with overlapping drafts, partial copies and notes that disagree with each other. When answer quality drops in a project like that, uploading more files makes it worse. The fix is to consolidate: keep one current document per subject and delete the rest. Conflicting instructions cause the same problem: when two of them disagree, Claude may follow either one.

    Google Docs added from Drive are the exception to manual replacement. They sync from Drive, so the project uses the latest version of the doc instead of a copy from the day you added it. This option is limited: the Drive connector can only add files to private projects. In a shared project, every knowledge file is an upload, and someone has to replace it by hand when the original changes.

    How the two kinds of project knowledge stay current
    Knowledge typeStays current by itself?Available in
    Google Doc added from DriveYes, it syncs from Google DrivePrivate projects only
    Uploaded file (document, text, code)No, replace it when the original changesPrivate and shared projects

    Checkpoint 5 of 9· Check yourself

    For two years, many people have added material to a team's shared Claude project. The knowledge base now holds overlapping drafts of the expense policy and notes that contradict them. Two project instructions also disagree about which report format to use. Answers have become inconsistent. What fixes this?

    Checkpoint 6 of 9· Exam question

    A team uploads the new travel policy to a project but leaves the previous year's version in the knowledge base as well. What is the greatest risk?

    Sources34

    4.Turning repeated corrections into project instructions

    A correction typed into chat lasts only for that chat. Say a team tells Claude in every new chat to use the quarterly report template, not the old monthly one. Each correction works until the chat ends. Then the next chat starts without it, because chats in a project don't share context with each other. The only things every chat inherits are the knowledge base and the project instructions.

    The durable fix is to put the correction in the project instructions, which Claude applies to every chat in the project. A good signal is repetition. If you type the same correction you typed last session, or Claude gets the same thing wrong a second time, a rule is missing. Add it as one specific line, such as "Use the quarterly report template in the knowledge base", not a general reminder to be careful.

    Instructions go out of date too. A rule written for last year's template, team or policy keeps being applied after the thing it refers to has changed. Outdated instructions are worse than none, because they confidently point Claude at something that is no longer true. Review the instructions whenever the knowledge changes, and on a schedule. Delete rules that no longer apply, and fix any two rules that contradict each other.

    Checkpoint 7 of 9· Check yourself

    Every week, a finance team member opens a new chat in the team's Claude project and types the same reminder: use the quarterly report template, not the old monthly one. Claude follows it in that chat, but the next chat goes back to the monthly template. Which change stops this for good?

    Sources145

    5.Who can maintain a shared project

    On Team and Enterprise plans, each member of a shared project has a permission level, which decides who can do the maintenance described above (Sharing projects and permissions covers how sharing works). Members with Can edit can change the project instructions and knowledge. Members with Can view can see the knowledge and instructions and chat in the project, but they can't change anything. A viewer who finds an outdated file has to report it to an editor. The project creator manages who has access and can change permissions or remove a member.

    This affects how stale files spread. Several editors can each add documents, and that is how shared knowledge bases end up with overlapping versions. Giving one editor responsibility for each subject area keeps replacements happening, so nobody assumes someone else removed the old file.

    Checkpoint 8 of 9· Check yourself

    On a Team plan, three editors of a shared project have each uploaded their own version of the onboarding guide over the past year. Nobody removed the older copies. A member with Can view permission notices that Claude gives different onboarding steps from one chat to the next. What should happen?

    Sources12

    6.Archiving or deleting a finished project

    When a project's work ends, you choose between archiving and deleting it. Archiving takes the project out of your active list and keeps everything. It suits a campaign that is over but whose material the team may want to look back at later. An archived project moves to the bottom of your projects list and to the archived projects tab, and you can still open its conversations. When you unarchive it, members, permission levels and project knowledge come back exactly as they were.

    Archiving keeps members' access, so it doesn't lock anyone out. To revoke a member's access, remove them in the project's sharing settings. You also can't delete an archived project directly. Unarchive it first, then delete it from the project's menu and confirm. Deleting removes the project, so use it only when nobody will need the material again.

    Archive compared with delete
    QuestionArchiveDelete
    Can you still open the conversations?YesNo, the project is removed
    Are members and permissions kept?Yes, restored exactly on unarchiveNo
    Best forFinished work you may need to look back atMaterial nobody will need again
    Works on an archived project?Already archivedOnly after you unarchive it

    Checkpoint 9 of 9· Match them up

    A team lead is cleaning up shared projects after a campaign ends. Pair each goal with the action that achieves it.

    Tap a term, then the definition that fits it.

    Sources1

    Sources

    (5)

    Every claim above is drawn from one of these pages, quoted as it was written on the date shown.

    1. 1.
      “Anything you upload to this space will be used across all of your chats within that project.”
      ↩︎ Why a configured project drifts out of date
      “Claude will use these instructions for all the chats within the project.”
      ↩︎ Tracing a wrong answer to its source
      “Context is not shared across chats within a project unless the information is added into the project knowledge base.”
      ↩︎ Tracing a wrong answer to its source
      “Claude will use these instructions for all the chats within the project.”
      ↩︎ Turning repeated corrections into project instructions
      “Can edit: Members can modify project instructions and knowledge, update member settings, and actively contribute to the project.”
      ↩︎ Who can maintain a shared project
      “All members, permission levels, and project knowledge are preserved, and everything is restored exactly as it was when you unarchive the project.”
      ↩︎ Archiving or deleting a finished project
      “There is no way to delete archived projects at this time (you must unarchive it first).”
      ↩︎ Archiving or deleting a finished project
      “You can still access conversations from archived projects.”
      ↩︎ Archiving or deleting a finished project
      “Anything you upload to this space will be used across all of your chats within that project.”
      ↩︎ Key concept
      “Anything you upload to this space will be used across all of your chats within that project.”
      ↩︎ Exam trap 1
      “Anything you upload to this space will be used across all of your chats within that project.”
      ↩︎ Exam trap 2
      “Context is not shared across chats within a project unless the information is added into the project knowledge base.”
      ↩︎ Exam trap 3
      “All members, permission levels, and project knowledge are preserved, and everything is restored exactly as it was when you unarchive the project.”
      ↩︎ Exam trap 4
      “Anything you upload to this space will be used across all of your chats within that project.”
      ↩︎ Prediction
    2. 2.
      “When your project knowledge approaches context limits, Claude seamlessly enables RAG mode to expand capacity by up to 10x while maintaining response quality.”
      ↩︎ Why a configured project drifts out of date
      “Project creators can modify permissions or remove access as needed.”
      ↩︎ Who can maintain a shared project
    3. 3.
      “Google Docs added to chats and projects sync directly from Google Drive”
      ↩︎ Adding, replacing and pruning project knowledge
      “The Google Drive connector is only available when adding to Files in private projects.”
      ↩︎ Adding, replacing and pruning project knowledge
    4. 4.
      “if two instructions contradict each other, Claude may pick one arbitrarily.”
      ↩︎ Adding, replacing and pruning project knowledge
      “You type the same correction or clarification into chat that you typed last session”
      ↩︎ Turning repeated corrections into project instructions
      “Review your CLAUDE.md files, nested CLAUDE.md files in subdirectories, and .claude/rules/ periodically to remove outdated or conflicting instructions.”
      ↩︎ Checkpoint
      “You type the same correction or clarification into chat that you typed last session”
      ↩︎ Checkpoint
      “if two instructions contradict each other, Claude may pick one arbitrarily”
      ↩︎ Checkpoint
      “if two instructions contradict each other, Claude may pick one arbitrarily.”
      ↩︎ Checkpoint

    Spotted a mistake, or was something unclear? Tell us.