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.
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.
| # | Request | What the system did | In the view |
|---|---|---|---|
| 1 | decision request carrying an unaccepted field | 422 refused, refusal_id present: True | appears |
| 2 | decision for a code outside the rules table | 200, rule_fired=default, rule_lookup=fell_through | appears |
| 3 | decision for a listed code (control: not a refusal) | 200, rule_fired=card_expired | must not appear |
| 4 | send to an address not on the allowlist | suppressed (recipient_not_allowlisted) | appears |
| 5 | message the output guard refuses | suppressed (failed_output_guard) | appears |
| 6 | provider fails (control: not a refusal) | failed (http_500) | must not appear |
| 7 | drafted message replaced with fixed copy | recorded by audit_llm_call | appears |
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.
| Store | Gate | Reason | Invoice |
|---|---|---|---|
decision_ledger | input_validated | unknown_field | SYN-1 |
decision_audit | rule_lookup | fell_through | SYN-2 |
message_store | recipient_allowlist | recipient_not_allowlisted | SYN-4 |
message_store | output_guard | failed_output_guard | SYN-5 |
audit_event_log | output_guard | draft_replaced_with_fixed_copy | - |
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.