Writing Testable Verification Instructions (CCAO-F)

Making verification a checkable behavior

Some of the highest-value standing instructions govern how Claude verifies itself. The CCAO-F exam treats writing these as an apply-level skill, because verification is exactly the kind of behavior that must be specified concretely to work: a vague wish to "be accurate" fails silently, while a testable verification rule actually constrains the output.

Two verification instructions carry most of the weight. "Cite the source document for every factual claim" makes grounding checkable: you can inspect any claim and confirm whether a source is attached. "Say 'I don't know' rather than guessing when the documents do not cover something" makes uncertainty explicit: instead of a confident guess filling a gap, the gap is surfaced. Together they turn verification from an aspiration into behavior you can audit.

The citation rule and the uncertainty rule

The citation rule works because it is testable. "Cite the source document for every factual claim" specifies a behavior you can verify by inspection: for any factual claim in the output, either a source is cited or the rule was broken. That checkability is what makes it effective where a vague "be accurate" is not, and it is a direct application of writing precise rather than vague instructions.

The uncertainty rule addresses the failure the citation rule alone does not. Without an explicit instruction to admit ignorance, a model can produce a confident, well-formed answer even where its sources say nothing, and that confident guess is hard to spot precisely because it looks like every other answer. "Say 'I don't know' when the documents do not cover something" makes the uncertainty visible instead of hidden, so a gap presents as a gap rather than as a fluent but unsupported claim. The two rules together reduce the risk of confident-sounding but unsupported output.

The uncertainty rule does not have to be phrased as a bare "I don't know". For structured or numeric output, the same discipline can be wired into the format itself: an instruction such as "for every figure in a report, state its source, and if a figure is not in the provided data, mark it 'unverified' rather than including it" turns each unsupported value into a visible flag on the page instead of an invisible guess. The mechanism is identical - surface the gap rather than paper over it - but the flag rides inside the deliverable, which is often more useful than a blanket disclaimer when the output is a table or a set of planning numbers.

Verification instructions must be paired with sources

There is a dependency the exam insists on: a citation instruction only functions when the knowledge base actually contains the sources to cite. This is the pairing rule in its most important application. Tell Claude to cite the source document, but leave the knowledge base empty of those documents, and the instruction has nothing valid to cite; it cannot do its job, and it may even invite fabricated citations.

So writing a good verification instruction is only half the work. The other half is ensuring the referenced material is present. A citation rule wired to a well-curated knowledge base produces checkable, grounded output; the same rule with no sources behind it is inert. Verification behavior is a two-part configuration, and both parts have to be in place.

What the CCAO-F exam trips candidates on

The exam sets two traps. The first is writing a citation requirement without ensuring the underlying source documents are present in the knowledge base. The instruction looks complete, but with no sources to cite it cannot function; the credited answer supplies the documents so the rule has real material. A well-worded citation rule with an empty base is the tell.

The second is omitting an explicit "say I don't know" clause, which allows confident guessing to pass unchecked. A verification setup that requires citations but never tells Claude to admit gaps still lets fluent, unsupported claims through in the places the sources are silent. The credited answer adds the uncertainty rule alongside the citation rule. Both traps reward treating verification as a complete, paired configuration: a testable citation rule, an explicit uncertainty rule, and the sources to back them.

Common misreadings to avoid

How this shows up on the exam

Domain 5 questions ask how to stop confident, unsupported output. The credited answer combines a testable citation rule, an explicit uncertainty rule, and a knowledge base that actually holds the cited sources. Watch for the trap of a citation rule with an empty base or a setup that never tells Claude to admit gaps.

This apply-level skill draws directly on vague versus precise instructions for the testability and on the pairing rule for the knowledge-base dependency. It is the sharpest instance of the purpose of standing instructions, where a persistent verification discipline holds across every conversation.