Contact match verification

Verification Boundary

The suite calls persistence or service behavior against the prepared local database. The structured assertion evidence names the individual checks read at the pinned revision.

What This Suite Proves

The listed bindings record this file’s contribution to capability or feature proof. Several files may contribute different assertions to the same scenario.

What It Does Not Prove

Source inspection establishes that the suite exists. It does not establish a passing run or complete product conformance. Any dependency replaced by the harness remains outside the resulting proof.

Real Dependencies and Test Doubles

The database and service transactions remain real where the suite uses them. Clocks, providers, delivery, queues and participant functions may be doubled as declared in the pinned suite.

Must Not Be Doubled

Keep the persistence, constraints and transactions used by a database assertion real. Keep the request handler and permission enforcement real when claiming public-request proof.