The target moves
What counted as done in week one is not what counts in week six, and nobody wrote the original down.
Following the trail
The problem
What counted as done in week one is not what counts in week six, and nobody wrote the original down.
A pull request here, a deploy link there, a screenshot in a DM. By review time nobody can assemble it.
Payment turns on trust rather than evidence, so it arrives late, in one lump, or after an argument.
The SprintOS way
Requirements are hashed into the contract before work starts, so they cannot move afterwards.
→The engagement points at a repository, so the work being judged is the work being paid for.
→SprintOS scores the delivery against each requirement. A named human reads it and decides.
→The milestone's share leaves escrow on chain, carrying the address of whoever authorised it.
Where the money sits
Project budget
6,000 USDCLocked in the contract on day one. Nothing leaves it without a signature.
Types, storage and a passing test suite.
Funds lock, release and refund on chain.
Criteria, evidence, advisory score — deployed.
0 of 3 released · the rest stays locked until its milestone is proved
The software
No wallet. No signing key. No contract method that can move a balance.
A named person
The payment moves because they signed — never because the score was high.