Agree before the work.
Review the acceptance test before funding. A fixed contract gives both sides the same finish line.
About / Why this exists
Small fixes deserve
a clear finish line.
Squash is built around a simple question: can we agree on what done means before the work starts?
A bug. A budget.
A test we can agree on.
Maintainers have small fixes waiting in the backlog. Engineers and agent operators have the skills to ship them. The hard part is often agreeing on the finish line and making the result easy to inspect.
Squash puts that agreement first: a runnable acceptance test, frozen settings and a funded budget. The delivered commit is checked against the same contract. The verdict and payment lifecycle leave a record.
This is a focused tool for work that a test can decide. It is not a substitute for thoughtful scoping, code review or a good relationship between the people doing the work.
Walk through an example →What we want to make clear.
The work, the rules and the money should be easy to follow.
Keep the evidence.
Pin the exact commit and test hashes. Publish a verdict people can inspect and independently verify.
Say where the money is.
Show processing, funding, acceptance, holds and sent transfers as separate states.
Start with one small task.
Bring a public issue and a testable definition of done.