A Polygraph engine

polyvers — evolve a live system without breaking what's already running

The moment you change a state machine's definition, every instance already running it is still running the old one. polyvers classifies the change, seeds it against real in-flight state pulled from the live fleet, and gates the deploy on the verdict.

How it works

The step most verification tooling skips entirely.

1

Classify the change

Every version diff is sorted into a compatibility lane before anything else happens: additive, migrated, or breaking.

2

Seed the live fleet

The new definition is checked against snapshots of instances that are actually running right now, not a clean synthetic dataset.

3

Gate deploy on the verdict

A breaking change with no valid migration for in-flight state is blocked before it ships, named offenders included.

Fits with: The step after polygraph or polygen has verified the new version in isolation — polyvers is what verifies it's safe for the fleet that's already live.