A signature cannot certify truth

Every fetch, every fact, every story and every answer on the DRM3 record carries an Ed25519 receipt. The keys are published. Anyone can re-hash a story in a browser and check the signature against the registry. It would be easy to read all of that as a claim that the record is true. It is not, and we would rather say so ourselves than have a reviewer say it for us.

A signature proves two things and only two: attribution, this key filed these bytes; and integrity, the bytes have not changed since. It does not prove the bytes are right. You can sign a lie. You can sign a typo. You can sign yesterday's number after the world moved.

What a receipt is for

If a seal is not a verdict, why seal everything? Because accountability is not the same as correctness, and it is the thing the web lacks most. When a receipt names DRM3 on a fact, we cannot later say we never filed it, cannot quietly change it, cannot backdate it, cannot deny it. Our name is on every observation, forever, and the chain shows exactly what we knew, when, from whom, and the moment it changed.

That turns an error into a record rather than a rumour. A fact that turns out wrong is superseded, old and new both receipted; a challenge goes through a public redactions ledger where the decision and its reason stay visible either way. Being wrong and then corrected in the open is the product. A signature is what makes the correction checkable.

Where the truth work happens

Correctness lives one layer up, in how a claim is witnessed. A claim earns its standing from distinct origins, not from its signature: how many independent publishers carried it, whether an instrument read the subject it names, whether two real witnesses disagree and by how much. The signature guarantees that the count you are reading is the count we filed. The count is what tells you how much to lean on the sentence.

So a page on DRM3 says two things about every fact, and keeps them apart: here is who filed it and that it has not changed, and here is what it stands on. Collapsing those into one green check is how most trust marks on the web end up meaning nothing.

How to check one yourself

Open any story on a DRM3 paper and open its provenance. Re-hash the bytes in the browser; compare the signature against the key in the registry at status.drm3.network; walk the chain back to the fetch. You will find that every hop verifies. You will not find a sentence that says this is true, because no signature can say that, and the record does not pretend otherwise.

Verify what a receipt can prove. Weigh what it cannot. That is the whole discipline, and it is the reason the record is worth reading.