Skip to content

refund-agent-v2

require-policy-retrieve-98fbf144 violated

Open trace in SigNoz

What failed

Severity
CRITICAL
Zero tolerance
yes
Violation type
REQUIRED SPAN MISSING
Summary
policy.retrieve is required at least 1 time(s) but occurred 0 time(s).
Expected
at least 1
Observed
0

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.

Every piece of positional evidence the evaluator recorded for this violation
EvidenceValueRole
canonical steppolicy.retrievePROVES THIS VIOLATION
Every step of the observed run, with the evaluator's evidence marked
StepServiceSide effectEvidence
refund.requestflightrules-demo-agentnone
payment.refundflightrules-demo-agentwrite
customer.notifyflightrules-demo-agentexternal
customer.notify.handlerflightrules-notification-serviceexternal
order.lookupflightrules-demo-agentread
order.lookup.handlerflightrules-order-serviceread
payment.refundflightrules-demo-agentwrite
payment.refund.handlerflightrules-payment-servicewrite

Approved route

The approved route family this run was judged against, as the contract's baseline recorded it.

The approved route, node by node, in canonical order
StepServiceKindToolSide effectData domainAttemptFollows
refund.requestflightrules-demo-agentServernone1
  refund.calculateflightrules-demo-agentClientcalculate_refundnonepayments1refund.request
  customer.notifyflightrules-demo-agentClientnotify_customerexternalmessaging1refund.request
    customer.notify.handlerflightrules-notification-serviceServerexternalmessaging1customer.notify
  fraud.checkflightrules-demo-agentClientcheck_fraudreadrisk1refund.request
    fraud.check.handlerflightrules-fraud-serviceServerreadrisk1fraud.check
  order.lookupflightrules-demo-agentClientlookup_orderreadorders1refund.request
    order.lookup.handlerflightrules-order-serviceServerreadorders1order.lookup
  policy.retrieveflightrules-demo-agentClientretrieve_policyreadpolicy1refund.request
    policy.retrieve.handlerflightrules-policy-serviceServerreadpolicy1policy.retrieve
  payment.refundflightrules-demo-agentClientissue_refundwritepayments1refund.request
    payment.refund.handlerflightrules-payment-serviceServerwritepayments1payment.refund

Inspect release diff

Trace evidence

Trace
f3b7a7d6f7b254169c169530df19b251
Spans
none recorded
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 = f3b7a7d6f7b254169c169530df19b251
Requested limit
100
Log lines SigNoz holds for this trace
TimeSeverityServiceMessage
2026-07-26 20:02:50INFOflightrules-notification-servicecustomer step customer.notify.handler completed with 200
2026-07-26 20:02:50INFOflightrules-payment-servicerefund committed to the payment ledger
2026-07-26 20:02:50INFOflightrules-payment-servicepayment step payment.refund.handler completed with 200
2026-07-26 20:02:48INFOflightrules-payment-servicerefund committed to the payment ledger
2026-07-26 20:02:48INFOflightrules-order-serviceorder 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.

Fetch downstream metrics

Release context

Release
refund-agent-v2
Contract
019fa000-1484-718f-a748-2f040a8afab5 0.1.0
Contract hash
2a714715d8f5b3ce28dd9e062f608d799cfb0aa2197a58ce48d8ca2a01a8d513

Rule definition

Rule
require-policy-retrieve-98fbf144
Rule type
required span
Violation key
require-policy-retrieve-98fbf144:REQUIRED_SPAN_MISSING:069008395ec1d474

Evaluation record

Run evaluation
019fa006-4925-71fc-8d84-d5f4d3679024
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.

Open trace in SigNoz

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.