Parallel Verification (PV)

What this is, and why it matters

Unit tests and acceptance tests run inside the system's own worldview. They trust the code's mocks, its in-memory state, and its own assertions about what happened. That trust is exactly the problem: a provider can return a state file saying a certificate exists, an API can return 201 Created, and the code can pass every test — while nothing real ever landed in the backend.

Parallel Verification is the practice of confirming an effect from the outside. You operate the system through its real public interface as a black box, capture what the system claims it did, and then go to the actual system of record through a separate, independent path and check whether the effect is really there. The verification path must not share code, libraries, or trust with the thing under test — that independence is the entire point. The code author (human or agent) can make the code lie; they cannot make psql, RACDCERT, the AWS CLI, or the Vault CLI lie about what is actually stored.