Invented data, run by the code on this page's source

Every refusal gate, on one screen.

7 synthetic requests go through the real code paths. 5 of them are refused, and each lands in the refusal view under the gate that refused it. 2 are not refusals and must not appear: a decision that matched a rule, and a provider that failed.

Watch the agent chase an invoice

38 seconds, no sound. The public demo on the home page, run on two invented failed payments: the rules table picks the action and the wording comes from committed templates. The public demo has no model key and sends nothing. The refusal gates are the tables below.

What was sent

#RequestWhat the system didIn the view
1decision request carrying an unaccepted field422 refused, refusal_id present: Trueappears
2decision for a code outside the rules table200, rule_fired=default, rule_lookup=fell_throughappears
3decision for a listed code (control: not a refusal)200, rule_fired=card_expiredmust not appear
4send to an address not on the allowlistsuppressed (recipient_not_allowlisted)appears
5message the output guard refusessuppressed (failed_output_guard)appears
6provider fails (control: not a refusal)failed (http_500)must not appear
7drafted message replaced with fixed copyrecorded by audit_llm_callappears

What the refusal view then lists

This is what GET /refusals returns for these requests: every refusal, with the store it came from and the gate that refused it. Sources read: message_store: ok, decision_ledger: ok, decision_audit: ok, audit_event_log: ok.

StoreGateReasonInvoice
decision_ledgerinput_validatedunknown_fieldSYN-1
decision_auditrule_lookupfell_throughSYN-2
message_storerecipient_allowlistrecipient_not_allowlistedSYN-4
message_storeoutput_guardfailed_output_guardSYN-5
audit_event_logoutput_guarddraft_replaced_with_fixed_copy-

Why the controls matter

A table of refusals proves nothing if it can be empty for the wrong reason, or full of things that are not refusals. So the run names the rows it expects and fails if one is missing or if either control shows up. A provider that fails is a failure, not a refusal: nobody decided anything. A decision that matched a rule is not a refusal either. Both are absent above, and the build breaks if that stops being true.

What this page does not claim

Read the source