SHUNYAYA FRAMEWORK

A bounded way to check whether declared reset evidence is complete, consistent, and linked to the declared subject, credential, and recovery request. 🔄 SLANG-ResetPassword Password-reset systems often combine several very different questions: Was identity proofing completed? Was a reset token, one-time password, or recovery code validated? What credential-replacement authorization result did the external authorizer declare? Was the evidence intended for this subject, credential, replacement request, relying party, and recovery case? Do multiple declared authorizers agree? Is the evidence complete? Is the outcome allowed to be shown? Can the result later be reconstructed and checked? SLANG-ResetPassword separates the operational recovery process from the structural admission of the resulting declared authorization evidence. It does not establish whether identity proofing occurred, whether a reset token was valid, whether a recovery code was genuine, or whether an external authorize...

A bounded approach to checking whether declared password-verification evidence is complete, consistent, and correctly bound. 🔐 SLANG-Password Password-related systems often combine several very different questions: What password-verification result did an external component declare? Which declared verifier or verifiers supplied the evidence? Was the evidence correctly bound to the declared subject, credential, request, relying party, and challenge? Do multiple declared verifiers agree? Is the evidence complete? Is the result allowed to be shown? Can the result later be reconstructed and checked? SLANG-Password separates the external password-comparison process from the structural admission of the resulting declared evidence. It does not establish whether the comparison actually occurred or whether the external verifier was trustworthy. Raw passwords are not supported inputs. SLANG-Password does not compare passwords or derive a result from password material. An existing security c...