Stamp outcomes: when a check is not just pass or fail

Not every check ends in pass or fail. This page lists the other outcomes, what you get for each, and what it costs. Every notice is signed and logged; none is ever edited or deleted. What our stamp means has the promise itself.

The outcome types

Outcome	What it means	What you get	Charge
Pass	Every listed check passed and none was left unchecked.	The service's signed stamp.	Normal price.
Fail	At least one listed check failed.	The service's signed stamp with the failed checks named.	Normal price.
Cannot determine	No one is at fault: a source was offline, the evidence was incomplete, sources conflicted, or the question is out of scope.	A signed Inconclusive notice with a plain reason code, what would resolve it, and a free retry window.	No charge.
Partial	Some claims passed and none failed, but some could not be checked. A service may call this its own 'inconclusive'; we report it as partial because it names what passed.	A signed notice listing which claims passed and which could not be checked.	Charged for the claims checked only.
Our fault	An outage, a bug or a wrong stamp on our side.	An incident is opened, affected callers are told, nothing is charged or the charge is refunded, and the root cause is published at /security#incidents.	No charge or refund.
Revoked and corrected	A wrong stamp is withdrawn in a public signed log with the reason; a corrected stamp links back to it.	Anyone who checks the old stamp's id sees it was revoked, why, and which stamp replaced it.	Corrected stamp is free.
Dispute and appeal	Either party can challenge a result. A fresh reviewer who did not build or issue it re-checks; one appeal goes to a second fresh reviewer.	A signed decision: upheld, overturned or modified.	Free to open.
Abuse or fraud refused	We refuse to stamp when the request looks like farming, fraud or flooding, and log it.	A refusal with a code (no detection details); nothing is stamped, so the honest party is not harmed.	No charge.
Legal hold or privacy request	A hold freezes deletion and shows 'on hold' with no details. A privacy request erases personal text we hold unless a hold forbids it.	A signed record that the hold or request exists and what was done, never the content.	Free.

Cannot determine: the four reasons

An inconclusive result is signed, says which reason applies, what would resolve it and how long a free retry stays open. Send the same request with retry_of set to the notice id.

SOURCE_OFFLINE. A source we needed to check was offline or did not answer. Nothing for you to do. Send the same request again with retry_of set to this notice id; the retry is free.
EVIDENCE_INCOMPLETE. The evidence sent was not enough to check the claims. Send the missing items (see missing) and ask again with retry_of set to this notice id; the retry is free.
SOURCES_CONFLICT. Two sources disagreed and we could not tell which is right. Wait for the sources to settle or send a third independent source. A retry with retry_of is free.
OUT_OF_SCOPE. The question is outside what this service can check. Ask for a check this service supports (see /stamp for what each service covers). No retry is needed for this request.

Checking whether a stamp still stands

Give a stamp id to https://llpro.ai/outcomes/v1/stamp/{stamp_id}. The answer is signed and says revoked (with the reason and the corrected stamp), on_hold, under_review, incident_open or no_notice. The last one does not prove a stamp is genuine; check its signature as well. The full withdrawn list is at /outcomes/v1/revocations. Revoking is final: a withdrawn stamp is never un-withdrawn; a corrected stamp is a new one that links back.

Disputes and appeals

Either party can challenge any stamp (tool outcome_dispute). A reviewer who did not build, issue or earlier review it re-checks and a signed decision follows: upheld, overturned or modified. One appeal is allowed within 30 days (tool outcome_appeal), decided by a second fresh reviewer. We cannot yet prove which party you are, so your role is recorded as you declare it. Targets: reviewer within 3 days, decision within 10. These are targets, not history.

Abuse, holds and privacy

We refuse to stamp farming, flooding and fraud and do not publish how we spot it. A legal hold shows only on hold. A privacy request (tool outcome_privacy_request) erases the personal text we keep unless a hold forbids it, and the log keeps only hashes, so the record stays intact.

Counts, last 30 days

Outcome	Count
Pass	35
Fail	22
Cannot determine	6
Partial	1
Abuse refused	0
Incidents open	0
Incidents closed	0
Stamps revoked (all time)	0
Corrected stamps (all time)	0
Disputes opened (all time)	0
Disputes upheld	0
Disputes overturned	0
Appeals	0
Holds active	0
Privacy requests done	0

As data: /outcomes.json.

Page dated 12 November 2026. Written by our Quality, Legal and Chief Architect seats; not yet reviewed by a licensed attorney.