CLAUDE CODE AGENTS: ADVANCED ORCHESTRATION - Chapter 10 (Capstone), Exercise 2
Why Styling Constraints Belong in Shared State, Not Just the First Brief
====================================================================================

QUESTION:
Explain why the accent color and wrapper class constraints are placed in
shared state rather than only stated once in Stage 1's own brief, using
Chapter 7's own reasoning.

SOLUTION / EXPLANATION:

Chapter 7 is explicit that a pure point-to-point handoff chain only carries
forward whatever the immediately prior step's own output happens to
include - something stated once early in a chain can silently disappear a
couple of hops downstream if each successive step's own summary doesn't
happen to repeat it. This capstone's own pipeline has four real stages
after the initial research (planning, generation, review, and potentially
a failure-handling step), meaning the accent color and wrapper class
constraint would need to survive several separate handoffs if it were only
ever passed forward as part of each stage's own distilled output.

The constraint that actually matters here - which accent color and wrapper
class this specific course uses - is exactly the kind of original,
chain-wide requirement Chapter 7 says is at real risk of quietly dropping
out in a purely point-to-point chain: the planning stage might reasonably
focus its own summary on the content outline rather than repeating styling
details, and if that summary is what feeds the generation stage, the
styling constraint could vanish well before the chapter actually gets
written.

Placing it in shared state instead - visible to every stage of the
pipeline independently of what any single intermediate stage's own summary
happened to include - guarantees the generation stage still has it when
actually writing the chapter, and guarantees the review stage still has it
when checking the chapter afterward, regardless of how many hops separate
either of those stages from where the constraint was first stated. This is
precisely the problem Chapter 7 says shared state exists to solve.

--------------------------------------------------------------------------
WHY THIS WORKS AS AN ANSWER:
It applies Chapter 7's own point-to-point-chain risk directly to this
capstone's specific pipeline shape, explaining concretely at which stage
the constraint could plausibly get lost if it weren't in shared state, and
why shared state specifically prevents that loss.