Skip to main content

Governance-as-Onboarding: Sabotage Demos Create the Aha Moment

The Core Insight

When onboarding someone to an agent governance system, the happy path is forgettable. Running validate and seeing “passed” teaches nothing about why the system exists. The moment that converts skeptics is when they try to break it and fail. Building the ATHENA council showcase (documentation domain, 3-step publish pipeline), we discovered that the “break it on purpose” section — running intentionally-tampered fixtures against the CI pipeline — is what makes a developer say “this is real infrastructure.”

What Changed

We now structure every council demo as a 5-act walkthrough where Act 4 (“Break It”) is the centerpiece, not an afterthought:
  1. Meet the Council (agent roster, governance roles)
  2. Explore the Units (validate, fingerprint, dependency graph)
  3. Compile & Run (multi-target compilation, live execution with gates)
  4. Break It on Purpose (3 sabotage scenarios: tampered fingerprint, removed protected agent, removed gate)
  5. Visualise Everything (Meridian pages)
The sabotage fixtures are pre-built YAML files with exactly one governance rule broken. Running stratt ci on them produces clear, specific failure messages that map to named failure modes (FM-01, FM-04, FM-05).

Why This Works

The psychology: trust in safety nets comes from watching them catch things, not from being told they exist. CI pipeline documentation says “we check 11 things.” A sabotage demo proves those checks work by failing deliberately. For business stakeholders: this pattern translates directly to compliance conversations. “Show me the audit trail” becomes “here’s what happens when someone tampers with a prompt artifact — the system blocks it before it reaches production.”

Actionable Takeaway

For any governance or compliance feature: build the demo around the failure case, not the success case. Ship pre-broken fixtures alongside every council. Budget ~4 minutes of demo time for the sabotage section — it’s the highest-ROI segment of the onboarding experience.