The method
A straight line
from plan to proof.
A requirement becomes a check. The check is challenged. The finished work is tested. Every decision keeps its evidence.
Explore belowStart with a requirement
A human approves what matters. Demaloa keeps the exact wording attached to every check.
Build a check that can fail
The verifier runs candidate checks against deliberately broken versions of the code. Weak checks never become release gates.
Run it against the real work
The finished app is exercised in an isolated environment. The observed response is compared with the approved requirement.
Keep the evidence
A pass or block comes with the request, response, and check that produced it.
The visuals below explain the intended workflow. They are concept illustrations; a working public demo is coming soon.
Same task.
Same expectations.
The plan shouldn’t disappear when the agent starts building. Keep the requirement beside the work, all the way to the check.
Allow booking cancellations.
Cancellation route implemented.
Anonymous request returned 204.
Start with the rule a person approved.
Illustrative workflowA check should
earn your trust.
Before a check can judge the work, test whether it catches a deliberate mistake. A test that always passes tells you very little.
01 async function cancel(request) {02 requireAdmin(request.session)03 await bookings.delete(id)04 return response(204)05 }Example fault: remove the permission guard.
Illustrative workflowLess “try again.”
More “fix this.”
Give the next run the exact mismatch, not another open-ended prompt. The goal: fewer review loops and more from your AI budget.
Add the administrator guard before deleting the booking.
+ requireAdmin(request.session)The response points to the missed permission rule.
Illustrative workflow