Cases open only when the chain can be inspected.

• Reproducible ≠ physically supportedThe computation can repeat while the evidence still cannot own the physical relation.
  Case 02 · battery · local candidate · release gate pendingWhat Survived Audit—and What It Refused to Call CouplingA persistent relation survives reproduction but not the stronger physical-coupling claim.
• Claim refused after generationThe sentence was produced, then the evidence discipline refused it.
  no public case yet
• Wrong object identityThe record is real, but it is not yet tied to the object the claim names.
  no public case yet
• Wrong time basisThe timestamp or interval is valid, but not the physical interval the claim needs.
  Claim qualification · house energy + weather records · public case · release clearedSame Row Does Not Establish the Same Physical MomentA house's energy records and airport weather share a table. Their correlation can be reproduced; a shared physical measurement instant is not established.
• Proxy ≠ propertyA visible proxy cannot carry a stronger property claim by itself.
  Worked example · classical neural-network geometry · public caseSame Model, Different CurvaturesA new local classical-network calculation: at one selected model point and direction, model-label Fisher curvature is positive while fixed-label loss curvature is negative. This worked example does not replay or refute the authors’ historical experiment.

  Case 01 · battery · public case · release clearedOne Pack's Visible Carrying Roles Narrowed Without a Mirroring Capacity DeclineCapacity and response organisation remain separate claims on the same pack history.
• Shared assumption → false agreementTwo systems agree because they inherited the same assumption.
  no public case yet
• Missing observation channelThe decisive channel is not present in the trace.
  no public case yet
• Inference exceeds evidenceThe available trace supports a smaller sentence than the proposed conclusion.
  Battery records · battery · public case · release clearedSimilar summaries, different recorded pathsTwo pairs of BESS records — and a question about what a summary leaves out.

Local candidates are deliberately not linked from this index. The detail bytes may exist in git for review, but the public path stays closed until the release gate changes the case artifact. Future grid daily reports use the same rule: dated report/card binding first, case row second, public link last. If you are carrying a real record/claim fracture, start with Bring us a trace.