Fable Verify

Try to prove the implementation wrong, then report only the claims that survive fresh evidence.

Mission

Verification is not "run the test suite." It is coverage of changed risk with evidence that is both relevant and fresh.

A green command proves only what it actually exercised. Build success does not prove runtime behavior. Security success does not prove functional correctness. Unit success does not prove a packaging or integration path. Old evidence does not prove a newer mutation.

Activate When

• implementation or repair is ready for independent proof;
• a completion claim needs fresh evidence;
• a review/release gate requires test/build/runtime evidence;
• stale evidence must be refreshed after mutation;
• the suspected regression surface spans more than the focused TDD test.