A verification contract turns intent into testable expectations that an implementation must satisfy before it is accepted. It records what “correct” means in a form a machine can check and a person can sign, covering behavior, performance, and security. section 1.7 section 1.8
The contract is the control point for AI-assisted development: generation may accelerate, but reliability depends on the specification and the verification gate. It replaces dump-and-review with verify-then-merge and keeps human judgment focused on whether the implementation matches intended meaning. section 1.0 section 1.8
A useful verification contract can combine:
- Typed APIs and other executable interface expectations. section 1.4.1
- Unit, property, and behavior tests that make acceptance mechanically checkable. section 1.4.1 section 1.8
- Human review of semantic correctness, because mechanical checks do not establish whether the business meaning is right. section 1.8
A small executable expectation
def test_valid_isbn_with_spaces(): assert is_valid_isbn13("978 0 306 40615 7") is True section 1.4.1
def test_valid_isbn_with_spaces():
assert is_valid_isbn13("978 0 306 40615 7") is TrueBrowse a concrete test-shaped contract that checks accepted input behavior. section 1.4.1
