→ The decision rule, in full

Every scored indicator resolves through one ladder, evaluated in order, first match wins. It reads exactly two inputs: confidence and source_count, the number of distinct independent sources. The four records below are chosen so each passes or fails for a different reason.

—

Say this before you reveal

—

recommended_actionawaiting reveal

confidence—

source_count—

Talk track & traps

Scoring dimensions

as emitted for this record

Severity, freshness and corroboration are computed and returned but do not participate in the verdict. They are advisory to SarraS's decision precisely so they can be decisive in the customer's own routing policy.

If asked about Admiralty

Reliability and credibility are separate axes. A record can carry a well-regarded source and still score low on credibility if the claim itself has not been independently judged. Say that plainly rather than treating the pair as one number.

→ The signed attribution claim

carried only by record 01

Verification does not happen on this page. A signature check run inside a SarraS-authored screen proves nothing. This card exists to hand the claim over. Their engineer runs a verifier containing no SarraS code, on their own machine, and watches it pass and then fail.

The covered fields

read live from signed_fields in the response

The trap in the tamper path

Altering a character only breaks verification if that field sits inside the signed payload. Say "change any of these", never "change anything". The list above comes from the response itself, so it is self-describing rather than asserted.

Tell them the canonicalisation scheme is RFC 8785 JCS. A verifier cannot infer it.

→ What each record proved

fills in as you run the set