Records / Buyer contract clauses
Turing (Lazarus): Acceptance
Turing's evaluator counts a pull request only if it changes at least one test file, has a test that fails before it and passes after it, and an earlier test that still passes; a new feature with no earlier tests is rejected.
Dated 2 Nov 2026Source checked 2 Nov 2026Its page gives an automatic check no text to read (last tried 3 Nov 2026)Basis: stated
Selling a company's data? This is one of the terms buyers set, and the guide beside the button reads it in plain words.
- No data upload
- About two minutes
- No email needed
In the source's own words
“PR must modify ≥1 test file ... At least 1 F2P test (proves the PR fixes something) At least 1 P2P test (proves existing tests still pass, no regressions) ... PRs that add entirely new features with no pre-existing tests will be rejected because they have no P2P tests.”
Where it was read
Turing (Lazarus), checked 2 Nov 2026
Everything read from this source (6)Archived copy, 3 Nov 2026
What it is about
Figures it counts in
It is shown on its own, not counted into a figure.
Cited in these 8 guides
- micro1, Handshake, Turing, Mercor: Data Programs Compared
- How to prepare company data for sale to AI labs
- How to prove your data is good without handing it over
- Selling Game Code and Game Data to AI Companies
- Selling Jira and Linear issue history for AI training
- How to Sell Your Codebase or Source Code to AI Companies
- What Is Turing's Project Lazarus? Pay, Terms and Process
- What an AI lab checks before it buys your data: the due diligence questions