The method behind Did It Actually Pay? Public on purpose, so you can hold every entry, and us, to the same standard.
A referee that will not show its rulebook is just an opinion with a scoreboard. So here is ours, in full. If we ever grade an entry in a way this page would not allow, that is a mistake you are entitled to point out, and we will fix it in the open.
The record answers a single question, and refuses every other one: did a specific, dated, checkable promise happen on its stated terms by its stated time? It does not ask whether something is a good idea, a good investment, or a scam. It does not predict. It compares a promise, written down on a known date, against what the official record later shows.
An entry can only exist if the promise contains something testable. That discipline is what keeps the record honest and keeps us out of opinion.
Qualifies: "We will ship feature X by [date]." "Backed one-to-one and redeemable." "Deposits are insured." "This will reach [number] by [year]." Each of these can be checked against a later fact.
Does not qualify, and is never entered: "We will revolutionize finance." "The future is on-chain." Vague ambition has no test, so it has no place here. Ruling it out of scope is itself a quiet statement about hype.
Every entry is the same three parts. If it cannot be built in this shape, it does not run.
The stated thing happened, on the stated terms, by the stated or a reasonable time. We use this tier prominently. A record that never says Paid is not a referee.
Something shipped or was returned, but materially less, later, or on changed terms. The entry states exactly which part fell short.
The record shows the stated thing did not happen and will not: cancelled, not returned, contradicted by a court or regulator finding. The tier grades the promise, not the person.
The clock is still running. Every Too Early entry names a public check date on which we will re-grade, whatever the outcome. Writing the promise down before the outcome is known is the entire point of the record.
The promiser formally retracted or restated the promise before its deadline. Recorded neutrally, with both dates. Honest retraction is not punished.
The repeatability test. The rubric passes only if a stranger, handed the two source documents, would reach the same verdict we did. If a verdict needs judgment beyond comparing document A to document B, we narrow the claim until it does not, or we drop the entry.
Receipts are built from primary records, in this order of preference:
Every factual sentence in a receipt must be attributable to a document you can open. If we cannot link it, we do not write it.
These are not style choices. They are what makes the record trustworthy.
A dated record cannot be back-filled, because time only runs one way. Anyone can write, after a collapse, that the collapse happened. No one can retroactively create the entry that says we logged this promise, on this date, before the outcome, and committed to a check date. That is why we would rather publish two bulletproof entries a month, forever, than twenty in a launch and silence after. The value is not in any single entry. It is in a long record that was still standing when the check dates came due.