Read the promise
The AI-assisted import turns exact SOW language into measurable criteria. A human confirms what “done” means.
Evidence-backed milestone approval
The page says success.
The API says 500.
A screenshot looks finished. Greenlit checks what actually happened underneath it. Follow the same SOW promise through the hidden failure, a fixed rerun, client approval, and an invoice-ready record.
No sign-in required Catches false-success API failures
The moment screenshots miss
HTTP 500 caughtPromise vs. reality
01 SOW clause
“Submitting the contact form must create a lead and show a success confirmation.”
02 Confirmed criterion
AC-04Contact form creates a lead
03 Browser evidence
/fixture/contact
Page: “Request sent”API: HTTP 500
Greenlit decisionThe promise failed
Next stepFix, then rerun the same criterion
The three-minute story
Watch “done” become
something provable.
The walkthrough follows one frozen SOW through AI-assisted criteria, a deceptive staging failure, the fixed build, and the client's final decision.
Catch the fake success
The page shows success, but the lead request returns HTTP 500. Greenlit marks the promise as failed instead of trusting the UI.
Prove the fix
The same frozen criterion passes on the corrected build, then travels to a focused client decision and approval record.
The memorable momentThe screenshot says done.
The screenshot says done.
The evidence says failed.
A screenshot alone can look convincing. Greenlit checks the browser outcome behind it and attaches that observation to the exact promise the client signed.
Thanks! Your trip request was sent.Looks finished
POST /api/fixture/leadsHTTP 500 · promise failed
From promise to approvalOne promise. One failure.