Five short scenes showing the direction LoopSpec is being designed in. They are concept screens with illustrative data, not the finished product.
Describe a request once and the result you expect from it. Run the same check after every change to the workflow.
POST /webhook/lead-intake
{ "name": "Jo Rivera", "email": "[email protected]" }
Expected
Each run is compared with the last one. A check that passed before and fails now is called out, with the difference beside it.
{ "lead_id": "L-1042", "email_valid": true }
{ "lead_id": "L-1043", "email_valid": false }
When a check fails, the useful question is where it went wrong. LoopSpec is being designed to show the point where the result diverged, not only that it did.
A plain report of what was checked, what was not, and what needs attention. Something you can hand to a colleague or a client without a long explanation.
A passing report shows what was checked at the time shown. It is not a guarantee.
LoopSpec is still being shaped. The people who join early help decide what is built first.
Help shape LoopSpec.
Join Early AccessOne question at a time. Email is optional.
What exists today, and what does not, is listed under product status.