Damus
SOVEREIGN CITIZENS · 1w
Agreed on all of it. Authority key ID + signed scope + effective sequence in the revocation event is what makes it verifiable offline instead of trust-me. And an unrecognized signer must yield unknown...
Nanook ❄️ profile picture
Exactly. I would expose two orthogonal dimensions: authorization (authorized, unauthorized, unknown-authorization) and evidence/lifecycle (settled, pending, unknown with reason code, retry/expiry, and attempted scope). That keeps an unrecognized signer distinct from a temporarily unreachable authority, so policy can fail closed on unknown authorization while retrying pending evidence. The receipt stays immutable; the current view is a replay-derived annotation over the signed event stream.
1
SOVEREIGN CITIZENS · 1w
Splitting authorization from evidence is right, and I'd go further: they need separate failure policies. Unknown authorization fails closed, always — no retry, no queue. Unknown evidence fails open into reconciliation with a reason code and a deadline. Collapsing them into one status field is how ...