Registry Notes
Fields first, interpretation second.
These notes define how public registry rows should be read. Unknown fields should stay unknown; they should not be inferred into stronger claims.
Core fields
| Field | Meaning | Common failure |
|---|---|---|
claim_id |
Stable pointer to a bounded claim, formula, protocol, or benchmark result. | Using one claim ID for multiple incompatible claims. |
evidence_role |
Whether the row is main evidence, support, negative result, boundary, or manifest. | Treating support evidence as decisive evidence. |
evidence_status |
The current strength of the evidence: public support, protocol stage, negative result, pending repair, or boundary only. | Reading protocol-stage evidence as if it were deployment-grade evidence. |
artifact |
The public file, DOI, code, table, figure, or manifest that can be checked. | Pointing to a page that describes evidence but does not expose it. |
boundary |
What this row does not prove. | Letting a narrow result silently expand into a broad claim. |
counterexample_route |
The smallest way a critic can weaken, falsify, or narrow the claim. | Making criticism possible in theory but impossible in practice. |
downgrade_trigger |
The condition that should narrow, weaken, or retract the claim. | Keeping the same claim after a reproduction failure, leakage finding, or stronger baseline. |
credit_policy |
Whether a row can count as proof, repair intent, or no-credit context. | Awarding credit to repair work before closed evidence exists. |
Reading rule
A public registry row is a pointer, not a victory lap. It should tell a reader: what is being claimed, what evidence is exposed, what is still not proven, and how to attack it.
{
"claim": "bounded",
"evidence": "publicly checkable",
"boundary": "explicit",
"counterexample_route": "open",
"private_system_details": "not included"
}
Public-private boundary
Public registries may expose protocols, manifest hashes, negative results, and reproducible toy gates. They do not expose private financial execution details, customer data, internal agent orchestration, commercial schedulers, or anonymous conference material.