Anthropic's CCA Exam as a Field-Guide for Agentic Engineering — Frank Coyle, UC Berkeley
A walkthrough of Anthropic’s architect exam doubles as a harness checklist: inspect stop reasons, narrow subagent scope, isolate outputs, and compact long-running context.
The Claude Certified Architect exam presents **six production scenarios** and randomly selects four. Its scenarios cover agent loops, code generation, multi-agent research, developer workflows, CI, and structured extraction across **five assessed domains**.
Apply the anti-patterns as harness checks: inspect stop reasons before accepting output, give each subagent only its needed tools and evidence, keep full subtask traces out of the primary thread, and compact long sessions around a defined token threshold.
The Claude Certified Architect exam presents **six production scenarios** and randomly selects four. Its scenarios cover agent loops, code generation, multi-agent research, developer workflows, CI, and structured extraction across **five assessed domains**. Apply the anti-patterns as harness checks: inspect stop reasons before accepting output, give each subagent only its needed tools and evidence, keep full subtask traces out of the primary thread, and compact long sessions around a defined token threshold. The talk interprets an exam rather than reporting measured engineering outcomes. Its suggested **150,000-token** compaction trigger is an example, not a demonstrated universal threshold; batch execution also trades **50% lower token cost** for delivery within 24 hours.
This converts an architecture exam’s scenarios and failure modes into a practical harness checklist: validate completion signals, minimize subagent authority, prevent trace pollution, and compact deliberately. It reinforces established context and permission patterns but does not validate them empirically; in particular, the token trigger and batch-cost trade-off should be treated as configurable examples rather than defaults.