What you asked for.
The caller’s intent remains visible in the result. It gives your workflow a concrete value to compare with what the form holds.
SEE IT WORK / INTERACTION LAB
The interesting part is
what happens next.
Change the supplied values, run the local example, and inspect the result. Try a valid form, a date rejected by the page, or a choice the form doesn’t offer.
Browser-only simulator. This is an educational illustration, not the SettleOn engine. It operates on the sample form below and sends nothing to a server.
TRY A CASE
01 / YOUR INPUTJSON
Edit these three values or load a case above. The JSON is sample input for this lab, not an API request schema.
02 / THE SAMPLE FORMLOCAL
Project intake
The start date must be a weekday.
03 / OBSERVED RESULTREADY
Run an example to see field-by-field results.Nothing has been submitted.
WHAT TO LOOK FOR
A filled box isn’t
the whole answer.
What actually landed.
A dropdown can only hold an available choice. A date field can hold a date while still failing the page’s weekday rule. Inspect both state and validation.
What your agent does next.
Correct the date, choose a supported option, or ask a person. A structured failure gives your workflow something useful to act on.
YOUR NEXT STEP
Build around the result.
Explore the proposed session lifecycle and field-result contract.