- In short
- The placement test sorts an identified fix into one of three homes: a standing instruction for a rule that should always apply, such as a tone or formatting constraint; the knowledge base for reference material every run needs, such as a brand guide or product list; and a Skill for a repeatable multi-step procedure, such as generating a report in an exact format and order. Placing a fix in the wrong home is why some optimizations fail to stick: a procedure squeezed into a one-line instruction loses its steps, and reference material crammed into an instruction bloats every prompt.
Three homes, one quick test
Once a friction audit has produced a list of fixes, each fix needs a home, and there are exactly three: a standing instruction, the knowledge base, or a Skill. The Claude Certified Associate - Foundations (CCAO-F) exam packages the choice as a quick test, is this a rule, a reference, or a procedure, because getting the home right is what makes an optimization actually hold. A well-identified fix placed in the wrong home is a common reason optimizations quietly fail, so the placement decision is not a formality; it is where success or failure is often decided.
This understand-level skill sits between spotting friction and acting on it. The three friction signals from three friction signals in recurring workflows tell you something needs fixing; the placement test tells you where the fix goes. It shares its logic with choosing the right lever in the feedback task statement, but here it is framed around the content type of the fix rather than the frequency of a correction.
- The rule-reference-procedure placement test
- A test for where an identified fix belongs, based on its content type: a rule that should always apply goes into a standing instruction, reference material every run needs goes into the knowledge base, and a repeatable multi-step procedure goes into a Skill. Rules to instructions, references to knowledge, procedures to Skills.
Rules, references, and procedures
A rule is a constraint that should always apply within a Project: a tone the outputs must hold, a formatting standard, a required section, "always include the target segment." Rules are short and universal, which is exactly what a standing instruction is built to carry. Because a rule is a single always-on statement, it fits comfortably in an instruction and applies to every run without taking up much room.
A reference is material every run needs to consult but that is not itself a rule: a brand voice guide, the current product list, a policy document. This belongs in the knowledge base, where runs can draw on it as needed. A procedure is a repeatable sequence of steps that produces a specific result, generating a report in an exact format and order, running a defined multi-step transformation. This belongs in a Skill, which preserves the steps. The quick test names the three cleanly: rule, reference, or procedure, and each answer selects a different home.
Why the wrong home breaks the fix
Placement matters because each home is shaped for its content type, and mismatches fail in predictable ways. A standing instruction is short and always-on, so it suits rules but is a poor container for anything bulky or sequential. The knowledge base holds reference material for consultation but is not where always-on rules or step-by-step procedures belong. A Skill preserves an ordered procedure, which a one-line instruction cannot.
The two classic mismatches show why the test earns its place. Cramming reference material, a whole brand guide, into a standing instruction bloats every future prompt with content that should have been consulted from knowledge as needed, making every run heavier. Writing a multi-step procedure as a single short rule drops the steps needed to reproduce the result reliably; the instruction names the goal but not the method, so the procedure stops being reproducible. In both cases the fix was correct and the placement was wrong, and the placement is what broke it. This is the same steps-loss risk noted in promoting a working fix into a standing instruction or Skill.
What the CCAO-F exam trips candidates on
The first trap is cramming reference material directly into a standing instruction, bloating every future prompt with content that belonged in the knowledge base. A brand guide is not a rule; it is material to consult. Forcing it into a standing instruction makes every run carry it whether or not it is needed, and the credited answer routes reference material to knowledge and keeps instructions lean.
The second trap is writing a multi-step procedure as a single short rule, which drops the steps needed to reproduce the result reliably. A one-line "produce the report in our format" names the outcome but not the ordered steps that create it, so the result becomes inconsistent. The exam rewards recognising that a procedure with steps belongs in a Skill, which preserves the sequence. Both traps are the same error: matching the fix to a convenient home rather than to the home shaped for its content type.
Worked example
A team audits its proposal workflow and identifies three fixes: proposals must always use a formal, confident tone; every proposal should draw on the firm's current pricing sheet; and there is a precise seven-step assembly process for compiling a proposal from sections. Where does each belong, and what goes wrong if misplaced?
Run the quick test on each: is it a rule, a reference, or a procedure?
The formal, confident tone is a rule, a constraint that should always apply to every proposal. It belongs in a standing instruction, where it applies universally and takes little room. This is the natural fit, and there is no real risk of misplacement here, a short always-on constraint is exactly what a standing instruction is for.
The current pricing sheet is reference material every run consults, not a rule. It belongs in the knowledge base. The tempting mistake is to paste it into a standing instruction so it is "always there", but that bloats every future prompt with pricing content whether the run needs it or not, and pricing changes, so it is better consulted from knowledge where it can be kept current. Reference to knowledge, not instruction.
The seven-step assembly process is a procedure. It belongs in a Skill, which preserves all seven steps in order. The classic misplacement is compressing it into a one-line instruction like "assemble the proposal in our standard way", which names the goal but drops the seven steps, so the assembly stops being reproducible and outputs drift. Procedure to Skill. Three fixes, three homes, and in two of the three a wrong home would have quietly broken an otherwise-correct optimization.
Common misreadings to avoid
Misconception
Reference material can be pasted into a standing instruction so it is always available to the model.
What's actually true
Misconception
A multi-step procedure can be written as one short standing instruction naming the desired result.
What's actually true
How this shows up on the exam
Domain 7 questions here give you a fix and ask where it belongs, or explain why an optimization did not stick. The quick test settles most of them: rule to a standing instruction, reference to the knowledge base, procedure to a Skill. When a scenario says an optimization "failed to hold," the diagnosis is usually a placement mismatch, a procedure flattened into an instruction, or reference material bloating one.
This knowledge point builds on three friction signals in recurring workflows, which surfaces the fixes to place, and it feeds consolidating steps and promoting patterns, where placed fixes become durable improvements. It mirrors choosing the right lever from the feedback task statement. Sort by content type, and optimizations stick instead of quietly unravelling.
A team works out a precise multi-step process for generating a monthly board report in an exact format and order. Where should this fix live so it reliably reproduces?
People also ask
Where should a rule, reference, or procedure go?
When does a fix belong in a Skill?
Why do some optimizations fail to stick?
Watch and learn
Official Anthropic Academy lessons first, then hand-picked walkthroughs. Videos load only when you press play.
No videos curated for this concept yet
We are still curating the best official and community videos for this topic.
Official prep for this domain
Anthropic's own free prep module for this part of the syllabus, on the official prep course. Free with an Anthropic Academy sign-in.
References & primary sources
Master this concept with Archie
Practice it inside an adaptive study session. Archie, your Socratic AI tutor, tracks your mastery with Bayesian Knowledge Tracing and schedules the perfect next review.