- In short
- A decomposition made during discovery is a hypothesis, not a final answer; it should be revisited once pattern and reference-architecture decisions surface new constraints. Discovering that a "static knowledge" sub-task is actually live state should trigger re-decomposing that piece into a tool call, not patching it inside the original bucket. A decomposition that never changes after the first draft is a sign it was not tested against real architecture constraints, and revisiting is cheaper early than after implementation.
Full concept guide coming soon
We are building the in-depth, exam-aligned guide for this knowledge point. In the meantime, explore the prerequisites and related concepts below, watch the official Anthropic Academy lessons, and start an adaptive study session to master it with Archie.
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.
References & primary sources
Adaptive study
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.