What kept bothering me with SIGN was never issuance. It was the moment a verifier says, "this passed, but I still need the residency code."
The holder already shared a selective disclosure view. The schema is valid. The attestation verifies. But the residency code is outside that authorized view, so approval blocks and the holder is stuck at the desk while the verifier reopens the case.
That is the exact failure I keep coming back to. One field missing, access paused, and the whole flow is suddenly at risk of falling out of the credential path into screenshots, PDFs, and document resend.
What matters is whether that next question can stay inside the same flow. With selective disclosure and private or hybrid storage, the verifier should be able to request only the residency code through the same authorized read path, clear the check, and let access continue without forcing the holder to overshare.
That is still my real test for SIGN. When one more answer is needed, does the system ask for just that field and keep the flow moving, or does it quietly fall back to "send us everything again"?