Candidate Universal Shell amendment: Breakdown-Detection Mechanism (two paired halves). HALF A — Council Watchdog Obligation: each council brain, on receiving any cross-poll prompt from the orchestrator, must perform a procedural-compliance scan of the prompt and flag any visible protocol violation BEFORE answering the substantive question. Examples brains could catch: orchestrator sends single-round ratification without 'Round 1 of 2' framing (violates 926869fb); orchestrator presents a synthesized Layer B asking sovereign to ratify a Tier-2 artifact (violates 83614b20); orchestrator asks a technical sub-question via menu instead of converged recommendation (violates FORCED_RULE_11). HALF B — Orchestrator Self-Audit: orchestrator must recite applicable protocol rules at every user-facing-output transition (synthesis to user, cross-poll to council, ratification request, cycle close) and verify compliance before sending. Catches breakdowns brains can't see because they happen in orchestrator-to-sovereign chat outside council observability — most of project-onboarding-v0-1 Cycle Zero's six breakdowns were in this category. The two halves are complementary: brains catch what they observe, orchestrator catches what they can't. Surfaced by Tommy after Cycle Zero close: 'do we have a rule for the other council members to notify when a breakdown has occurred so that if they catch it? for example, if you ship something and ask for review, they should catch it that you shipped without council ratification?' Candidate for new Section 4.x in Universal Shell.