Work with us

Bring verification to the code your team ships with AI.

Code generation is solved. Trust is the bottleneck. Advisory and training from the author of the SAM pattern — so your team can gate AI-written code deterministically, on every change, instead of reviewing and hoping you catch every defect.

Teams shipping AI-written stateful code
Coding-agent & dev-tool builders
Safety-critical & regulated teams
Frontier AI labs
01 · ASSESS
Verification Readiness Assessment
For teams who suspect their AI-written stateful code is a risk but can't see where.
A focused review of how your team designs, tests, and trusts stateful code
Where combinatorial defects and “state that outlives its code” actually hide
A prioritized path from review-by-sampling to verify-by-construction
Fixed scope · written assessment + roadmap
02 · TRAIN
“Verify, Don't Review” Workshop
For engineering teams adopting verification-gated development.
The SAM pattern v2 — modeling stateful code
Turning intent into deterministic gates
Hands-on with your own code, not toy examples
Half-day to two-day · remote or on-site
03 · EMBED
Verification Architect
For teams standing up a verification practice for the long run.
Ongoing, hands-on guidance embedding verification gates into your lifecycle
Design reviews of your hardest state machines, on call
A direct line to someone who has spent a career on this exact problem
Monthly retainer · continuous
04 · PARTNER
Design Partner Program
For coding-agent builders, dev-tool companies, and frontier labs.
Early access to the Polygraph engines as they mature
Co-develop the verification layer for your agent or platform
Shape a critically missing piece of coding-agent architecture
Selective · partnership-based
Jean-Jacques Dubray, Ph.D.
Author of the SAM pattern
A career spent on stateful systems you can trust — a 1987 Ph.D., the IMSC closed-loop control project at Hughes Research Labs, chief architect of the NEC Boston Technology Center, and a contributor to the standards that formalized how systems coordinate.
What's different now: the spec is ordinary code — no specialist team required to write the math.

Tell me about your stateful code.

A 30-minute conversation about where AI-written code is quietly accumulating risk in your systems — and whether verification is the answer.
Book a call Send a message