No model call
The critique is assembled from the diff, not generated. Zero tokens, milliseconds, and byte-identical on every machine — which is what makes it safe to gate a pipeline on.
Proves an AI-authored change didn't pass by weakening the tests.
The yield point is where a material stops springing back and deforms for good — the moment it quietly stops being as strong as it was. A test suite does the same under an agent's edits.
- assert invoice.total == Decimal("42.00")
+ assert invoice.total is not NoneThe suite is green. Coverage is unchanged — the weaker assertion executes the same lines. The linter is silent. Nothing in a normal toolchain reports this, because every tool in it grades the code as it now stands, and this is a statement about what was taken away.
Yieldpoint grades the transition. Deterministically, with no model call, and with the same answer on every machine.
No network, no dependencies
The verification core has zero runtime dependencies and opens no socket. The whole supply chain can be audited in one sitting.
Never a false pass
A change nothing could analyse returns
unverified and exit code 3 — not pass.
Silence is never mistaken for safety.
Two commands
pip install yieldpoint
yieldpoint init # config, MCP server and editor hook
yieldpoint review # what you have already broken