Bring an agent or an MCP server you're already running, yours or a public one. We put it inside a containment boundary, then probe it adversarially: tool-call arguments shaped to pass a schema check while still doing something the schema never anticipated, outputs built to slip past a type-confused validator, and a handful of other concrete failure classes pulled from real, recurring defects in verification code, agent-adjacent and otherwise. Everyone leaves with two things: a containment setup they can point at their own agent afterward, and a small, re-checkable evidence artifact from the session itself, something a third party could look at and verify independently rather than a log the same system wrote about itself.

The format stays hands-on throughout; nothing you bring needs to be production-facing.