Independent acceptance

Requirements in. Verified software out.

Define done. Build with your agent or ours. FalseGreen decides if the exact change is accepted.

$2,999per Job

Buy a Job

One bounded consequential engineering scope. Production Beta.

Independent acceptance

Tests passed

The agent said done

FalseGreen: FAILED

The agent doesn’t get the final say.

Product demonstration

See independent acceptance in action.

A coding agent says the work is done. Tests pass. FalseGreen checks the frozen definition before that exact revision earns acceptance.

Coding agent reports implementation complete after 47 passing tests. FalseGreen independently evaluates the frozen definition of done and returns Failed because a revoked refresh token can still mint a new session. The implementation is repaired and reverified against the unchanged boundary. FalseGreen returns Accepted for the exact revision, and FalseGreen PR Gate then accepts that same revision in CI.

When to buy

Use FalseGreen when being wrong costs more than the Job.

Authentication, billing, migrations, infrastructure, access control, and release-critical behavior.

If this change is commodity work, don’t buy a FalseGreen Job.

The acceptance gap

Green evidence. Wrong result.

Evidence can be green

  • ✓ Tests passed
  • ✓ CI passed
  • ✓ Static analysis passed
  • ✓ Human review passed

The Job can still be wrong

  • ✕ Required behavior missing
  • ✕ Important invariant violated
  • ✕ Edge case outside the test suite
  • ✕ Agent declared completion too early

Tests and review produce evidence. They do not define what “done” means.

The acceptance platform

One authority. More ways to establish what is true.

Software, formal, security, and UI evidence meet at one frozen boundary.

FalseGreen independently evaluates one consequential software change against the definition of done agreed before the result is judged.

Software verification

Does the exact implementation satisfy the frozen requirements?

See Jobs →

Existing workflow

Bring your coding agent.

Enforcement after acceptance

Acceptance stays bound to the exact source.

PR Gate checks that the accepted result belongs to the current PR head. A new commit needs its own result.

Explore PR Gate →

How a Job works

Freeze done before judging the work.

  1. 1. Define done

    A human defines the consequential outcome.

  2. 2. Freeze it

    FalseGreen freezes the definition before judgment.

  3. 3. Build

    A human or agent implements the change.

  4. 4. Verify

    FalseGreen checks the exact resulting source.

  5. 5. Result

    Accepted / Failed / Insufficient Evidence.

If repair is allowed, the builder repairs against the same frozen boundary. The target does not move.

Proof

FalseGreen has actually said FAILED.

Tests passed. FalseGreen still refused to call it done.

FalseGreen found a production integrity problem after ordinary signals were green.

Read FalseGreen on FalseGreen →

The implementation looked correct. The evidence said otherwise.

Formal evidence showed the frozen boundary was not established until repair and reverification.

2h 44m from frozen target to FalseGreen ACCEPT. Less than 30 minutes of estimated human attention.

Read Ada / SPARK →

Qualification

Is this a FalseGreen Job?

Tell us the change. We can determine whether it belongs inside one bounded Job.

Probably yes

A consequential change with a definition of done and an independent result worth the price.

Probably no

Commodity work, routine cleanup, or a request for another generic reviewer.

The offer

One FalseGreen Job

$2,999

One bounded consequential engineering scope under one frozen definition of done.

  • Definition of done frozen before judgment
  • Independent verification of the exact resulting work
  • Accepted / Failed / Insufficient Evidence
  • Eligible repair + reverification against the same boundary
  • Durable source-bound report

Job support

One acceptance model across the stack that matters.

Language and framework support is scoped to the Job, including Lean formal proof evidence.

See Job language and framework support →

Trust

FalseGreen does not promise bug-free software.

  • ✓ Result is bounded to the frozen Job
  • ✓ Result is bound to the exact work that earned it
  • ✓ Insufficient Evidence is allowed
  • ✓ Tests, CI, and human review do not establish completion by themselves

What consequential software change is next?

If being wrong about it would cost substantially more than $2,999, it may be a FalseGreen Job.