refund-agent-v2
single-payment-refund-write-8846bedd violated
What failed
- Severity
- CRITICAL
- Zero tolerance
- yes
- Violation type
- CARDINALITY ABOVE MAX
- Summary
- payment.refund, agent.side_effect = write occurred 2 times; the contract permits at most 1 per run.
- Expected
- at most 1 per run
- Observed
- 2
Observed route
The route this run actually took. A step is marked as evidence only when the deterministic evaluator named its canonical index — nothing here searches for a step that merely looks similar.
| Evidence | Value | Role |
|---|---|---|
| canonical step | payment.refund | PROVES THIS VIOLATION |
| canonical node | 1 | PROVES THIS VIOLATION |
| canonical node | 6 | PROVES THIS VIOLATION |
| span | f0b9335b2b642927 | PROVES THIS VIOLATION |
| span | 0acdcfa27a8964b6 | PROVES THIS VIOLATION |
| Step | Service | Side effect | Evidence |
|---|---|---|---|
| refund.request | flightrules-demo-agent | none | — |
| payment.refund | flightrules-demo-agent | write | NAMED BY THE EVALUATOR |
| customer.notify | flightrules-demo-agent | external | — |
| customer.notify.handler | flightrules-notification-service | external | — |
| order.lookup | flightrules-demo-agent | read | — |
| order.lookup.handler | flightrules-order-service | read | — |
| payment.refund | flightrules-demo-agent | write | NAMED BY THE EVALUATOR |
| payment.refund.handler | flightrules-payment-service | write | — |
Approved route
The approved route family this run was judged against, as the contract's baseline recorded it.
| Step | Service | Kind | Tool | Side effect | Data domain | Attempt | Follows |
|---|---|---|---|---|---|---|---|
| refund.request | flightrules-demo-agent | Server | — | none | — | 1 | — |
| refund.calculate | flightrules-demo-agent | Client | calculate_refund | none | payments | 1 | refund.request |
| customer.notify | flightrules-demo-agent | Client | notify_customer | external | messaging | 1 | refund.request |
| customer.notify.handler | flightrules-notification-service | Server | — | external | messaging | 1 | customer.notify |
| fraud.check | flightrules-demo-agent | Client | check_fraud | read | risk | 1 | refund.request |
| fraud.check.handler | flightrules-fraud-service | Server | — | read | risk | 1 | fraud.check |
| order.lookup | flightrules-demo-agent | Client | lookup_order | read | orders | 1 | refund.request |
| order.lookup.handler | flightrules-order-service | Server | — | read | orders | 1 | order.lookup |
| policy.retrieve | flightrules-demo-agent | Client | retrieve_policy | read | policy | 1 | refund.request |
| policy.retrieve.handler | flightrules-policy-service | Server | — | read | policy | 1 | policy.retrieve |
| payment.refund | flightrules-demo-agent | Client | issue_refund | write | payments | 1 | refund.request |
| payment.refund.handler | flightrules-payment-service | Server | — | write | payments | 1 | payment.refund |
Trace evidence
- Trace
- fc4213ada8be595cd919cf1bbcbb1f9a
- Spans
- f0b9335b2b642927, 0acdcfa27a8964b6
- SigNoz
- no deep link was recorded
Correlated logs
Fetched from SigNoz on request, correlated strictly by this violation's trace identifier — never by a time window or a service name, either of which would attach another run's logs to this finding.
- Result
- OK
- Correlated by
- trace_id = fc4213ada8be595cd919cf1bbcbb1f9a
- Requested limit
- 100
| Time | Severity | Service | Message |
|---|---|---|---|
| 2026-07-26 20:02:39 | INFO | flightrules-notification-service | customer step customer.notify.handler completed with 200 |
| 2026-07-26 20:02:39 | INFO | flightrules-payment-service | refund committed to the payment ledger |
| 2026-07-26 20:02:39 | INFO | flightrules-payment-service | payment step payment.refund.handler completed with 200 |
| 2026-07-26 20:02:38 | INFO | flightrules-payment-service | refund committed to the payment ledger |
| 2026-07-26 20:02:38 | INFO | flightrules-order-service | order step order.lookup.handler completed with 200 |
Downstream metrics
What this violation actually caused, and — just as importantly — what kind of claim each number is. FlightRules reports what it measured and what the evaluator observed. It does not estimate a financial loss, because the telemetry does not show one.
Release context
- Release
- refund-agent-v2
- Contract
- 019fa000-1484-718f-a748-2f040a8afab5 0.1.0
- Contract hash
- 2a714715d8f5b3ce28dd9e062f608d799cfb0aa2197a58ce48d8ca2a01a8d513
Rule definition
- Rule
- single-payment-refund-write-8846bedd
- Rule type
- cardinality
- Violation key
- single-payment-refund-write-8846bedd:CARDINALITY_ABOVE_MAX:dc1edd9c49fa4a2a
Evaluation record
- Run evaluation
- 019fa006-492d-7020-a75f-ff01d672f8a3
- Evaluator version
- 1.0.0
- Evaluated at
- 2026-07-26 20:03:14
- Recorded at
- 2026-07-26 20:03:14
Evidence summary
A deterministic, safe summary for an issue or a review. It carries identifiers, hashes and the evaluator's own expected-versus-observed statement, and no prompt, tool argument, tool result or customer field — because it is assembled from fields that carry none.
A violation is never dismissed. A new contract version, or an explicit fixture exclusion, is the only way to change this outcome, and both write an audit record.