02 · Train

“Verify, Don’t Review” Workshop

For engineering teams adopting verification-gated development.

What's included

Half a day to two days, worked against code your team actually owns.

  • The SAM pattern v2 — modeling stateful code
  • Turning intent — the “must never happen” list — into deterministic gates
  • Hands-on with your own code, not toy examples

Half-day to two-day · remote or on-site

What happens next

If this sounds like your team, here's the process.

1

A 30-minute conversation

About your team, your stack, and which of your systems would make the best hands-on material.

2

Prep

We pick the state machine(s) to work against and confirm format — remote or on-site, half-day or two-day.

3

The workshop

Modeling, invariants, and gates, worked live against your own code with your own engineers.

4

What you leave with

A modeled, verified first machine, and a team that knows how to model the next one.