Project Anatomy: Instructions, Knowledge, History for CCAO-F

What a Project actually holds

The value of a Project is that it remembers, but to use it well you need to know exactly what it remembers. The CCAO-F exam treats this at the understand level: a Project is not one undifferentiated blob of saved context but a bundle of three distinct, persistent parts. Knowing what each part does, and where each kind of information belongs, is what separates a Project that quietly saves time from one that is set up wrong and disappoints.

The three parts are standing instructions, a knowledge base, and the Project's own conversation history. Together they solve the most common productivity drain in AI-assisted work: re-explaining the same background at the start of every session. You set the context once, and every conversation that follows begins with it already in place. This knowledge point builds directly on the recognition that a Project is one of the four entry points.

Standing instructions: the persistent brief

Standing instructions define what Claude should consistently know and do inside that Project. They are the persistent brief -- the role, the tone, the constraints, the format rules that apply to everything done in the space. The distinction the exam cares about is that standing instructions are not a one-time message typed into a single chat. A message you type into a lone Chat applies only to that conversation; standing instructions apply automatically to every conversation you ever start inside the Project.

That difference is what makes the setup pay off. Instead of re-typing the escalation thresholds, the house style, or the reporting rules each session, you write them once into the Project's instructions and they are silently present every time. The instructions describe behaviour and knowledge that should hold constantly; the knowledge base holds the reference material that behaviour draws on.

Knowledge base and conversation history

The knowledge base holds reference documents -- policies, prior reports, background files -- uploaded once and reused across every conversation in the Project. The trap the exam probes is the belief that these files must be re-attached in each new conversation. They do not. Upload once, and every conversation in the Project can draw on them without re-uploading. That single fact is most of why a Project saves time on recurring work.

The third part is conversation history. A Project keeps its own conversation list, distinct from your general chat history, so the work done inside a workstream stays grouped with that workstream. This is also where a subtle boundary lives: conversations in a Project share its instructions and knowledge base, but they do not automatically share each other's context. That boundary is important enough to have its own knowledge point in conversation isolation.

What the CCAO-F exam trips candidates on

The exam tests two misunderstandings. The first is believing uploaded knowledge-base files must be re-attached in every new conversation inside the Project. The credited answer is that files live in the Project once and are available everywhere in it -- re-attaching is exactly the manual work a Project exists to remove.

The second is confusing a Project's standing instructions with a one-time message typed into a single chat. A one-time chat message dies with that conversation; standing instructions persist across every conversation in the Project. A question may describe someone re-typing the same brief each session and ask what they should have done -- the answer is to move that brief into standing instructions rather than keep pasting it.

Common misreadings to avoid

How this shows up on the exam

Questions describe how someone has configured or is using a Project and ask what belongs where, or point out redundant re-setup and ask for the fix. Anchor on the three parts: constant behaviour and knowledge go to standing instructions, reusable reference files go to the knowledge base, and the conversation list belongs to the Project rather than your general history.

This knowledge point unlocks the project worth-building test, which decides when building this bundle is justified, and conversation isolation, which explains the one thing a Project does not automatically share. It also connects to memory persistence and curation, since durable facts can be persisted alongside the Project's knowledge base.