The claim existed on @SignOfficial . Fine. The chain can prove that.
Now what.
Thats the Sign version. The permanent part is easy. The live part gets dumped somewhere else.
Historical claims look clean. Attestation there. Issuer there. Signature also there. and... Timestamp there. Alright . Sign's SignScan happy to surface the whole thing like history itself settled the present-tense decision. Great. Very reassuring. Until a workflow has to act on it now.
On Sign $SIGN , the record can prove the claim was made. Who signed it. Under what schema. Which evidence pointer sat behind it. Good. Useful.
Still doesn't tell the workflow what to do with it today. Especially once current policy, issuer scope, or freshness rules have already drifted past what the attestation was built to answer.
Fine.
Sign can preserve the claim path. Sign can't clear the current one for you.
And that burden lands exactly where people hoped it wouldnt. Ops. Governance. Review. Whoever inherited the file after the easy part got immortalized and the annoying part stayed alive.
So now the stupid version starts. The claim is historically valid. The payment release still pauses. The access request still sits. The resolver passed it. The queue still didn't move. Ops says the record exists. Governance wants current policy, not a museum tour. Review wants to know whether the old claim still counts under the rule that exists now, not the one that existed when the issuer signed it three quarters ago.
Same attestation on Sign though.
...clean.
Still resolving.
Old claims keep showing up like they still get a vote.
So someone adds a freshness check. Then a side approval. Then a governance override that was supposedly temporary. Sure. That word does a lot of damage. Then the override starts getting cited more than the attestation. Then that patch starts deciding more than attestation does, because proving the claim existed was never the hard part.
Once the override is doing more work than the attestation... what exactly is it still settling on Sign protocol?