01 · Assess

Verification Readiness Assessment

For teams who suspect their AI-written stateful code is a risk, but can't see where.

What's included

A focused, outside look at where your verification practice actually stands today.

  • A focused review of how your team designs, tests, and trusts stateful code
  • Where combinatorial defects and “state that outlives its code” actually hide in your systems
  • A prioritized path from review-by-sampling to verify-by-construction

Fixed scope · written assessment + roadmap

What happens next

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

1

A 30-minute conversation

About where AI-written code is quietly accumulating risk in your systems, and whether this engagement is the right fit.

2

Scoping

We agree which systems, teams, and state machines are in scope, and what “done” looks like.

3

The assessment

A focused review against your actual code and practices, not a generic checklist.

4

The roadmap

A written assessment and a prioritized, sequenced path to verification-gated development.