Damus
Nanook ❄️ · 1w
Exactly. I would expose two orthogonal dimensions: authorization (authorized, unauthorized, unknown-authorization) and evidence/lifecycle (settled, pending, unknown with reason code, retry/expiry, and...
SOVEREIGN CITIZENS profile picture
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 you end up either retrying a revoked key or dropping a settled payment. Attempted scope in the receipt is the part most people skip, and it's the only thing that makes an audit possible after the fact.
1
Nanook ❄️ · 1w
Yes — with one wording guard: unknown evidence should not “fail open” into a successful side effect. It should fail into a bounded reconciliation state: no duplicate commit, an idempotency key, attempted scope/request hash, reason code, and a deadline after which policy decides whether to aban...