Episode Zero is a short guide to the difference between the Claude Certified Architect Foundations and Professional content. Both certifications are about designing useful, reliable systems with Claude, but they examine that work from different altitudes. Foundations stays close to implementation. It focuses on whether you understand the parts that make a Claude application work and how those parts should be controlled. The first major area is agentic architecture. This covers the loop around the model, including how an application handles model responses, tool requests, results, retries, stopping conditions, and human approval. The emphasis is on making the workflow explicit instead of assuming the model will manage everything by itself.

Foundations also covers tool design and Model Context Protocol. You need to understand how capabilities are described, how inputs and outputs are constrained, and how permissions remain enforced outside the model. Another area is Claude Code and the way teams configure it for repeatable software work. That includes project guidance, reusable skills, automated checks, and the difference between instructions that guide Claude and controls that actually enforce a rule. Prompt design and structured output form another part of Foundations. The important idea is to define what a good result looks like, provide useful instructions and examples, request a predictable structure, and validate the meaning before another system trusts it.

The final Foundations area is information management and reliability. This is about giving Claude the right material, preserving important state outside the conversation, handling missing or conflicting evidence, and making failures visible. Taken together, Foundations asks whether you can build the individual components of a Claude system correctly and connect them into a controlled workflow. Professional starts from that implementation knowledge and moves outward. Its focus is the complete production solution, the organisation operating it, and the decisions that justify its design. Professional content begins with understanding the business problem before selecting a model or architecture. It covers choosing between a simple model-assisted workflow, a more flexible agent, or a larger coordinated system according to the real variability and risk involved.

It goes deeper into model and deployment choices, system boundaries, service expectations, resilience, and cost. Integration is broader at the Professional level. You are expected to think about enterprise data, retrieval, identity, permissions, source quality, external services, and how failures can be traced through the whole path. Evaluation also becomes a system-level responsibility. That means defining useful success measures, testing representative work, separating different kinds of failure, and balancing quality with latency, cost, review effort, and operational impact. Professional also gives greater attention to governance, safety, security, privacy, and risk. The architect must identify who can be affected, which actions need deterministic control, what evidence must be retained, and how incidents or changes will be handled.

The remaining content concerns delivery and ownership. It includes stakeholder decisions, rollout, support, monitoring, change management, developer enablement, and the continuing work required after a system reaches production. The simplest distinction is that Foundations is about building the components well, while Professional is about owning the entire solution responsibly. Professional is not merely a harder version of Foundations. It widens the frame from model interactions and component behaviour to business value, architecture, operations, organisational responsibility, and long-term improvement. The first part of this series follows the Foundations content from agent loops through reliability. The later episodes use those same building blocks to explain the broader Professional responsibilities.

That progression lets you learn how the machinery works before judging how it should fit into a production organisation.