DEV SITE — deployed from the dev branch · NOT production · production is falsegreen.com

Independent Verification

Build it here. Accept it there. Prove the link.

Whoever writes the code cannot be the one who accepts it. A FalseGreen Job separates the two — permanently, on the record.

The problem

A demo proves nothing to the party paying for it.

“Done” is the vendor's word

A demo that runs is not evidence that it works — and the client has no way to tell.

Nothing to point at

When a delivery is disputed, there is nothing both sides can open and check.

No agreed bar

Without a written definition of done, acceptance is opinion — and disputes have no referee.

Separated by construction

Builder and referee, never the same party.

A referee neither side controls

Requirements frozen before the work starts; FalseGreen — not the vendor, not the client — decides.

One report both sides open

Verdict, evidence, findings, proofs — bound to the exact source, re-verifiable offline by anyone.

Lineage, not snapshots

Every re-run names the exact source it checked; a replacement run names what it replaces.

Same surface for both sides

Vendor and client open the same report and the same verify command. No shared secret.

See how the FalseGreen Job works →

One FalseGreen Job

Vendor builds
↓
FalseGreen decides
↓
Report both sides check

Requirements in. Verified Rust out.