domain: Anchor the credential vocabulary (consume, mint, displace) #84
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
rosa/vernier!84
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "domain/authorization-code-vocabulary"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Three commits that anchor the credential vocabulary in the glossary and bring the code in line with it:
c601f43retires "claim" from the authorization-code vocabulary: the port doc, domain-service comments, Postgres adapter comment, and conformance behaviours now say consume, and the glossary's Authorization Code entry states the redeem/consume distinction explicitly.a3c3f1cadds a Credentials section to CONTEXT.md anchoring Confirmation (the identifier + hashed-verifier credential for email confirmation and password reset), Mint (the one verb for bringing any credential into existence), and Displace (minting a reset confirmation atomically removes prior reset confirmations for that user only), and rewords doc comments that said a code or token "was issued" where minting was meant.225ece1retires the remaining synonyms from the API surface: the service'sissue_*methods, the port's credentialcreate_*methods, and theirCreate*Requestpayload types becomemint_*/Mint*Request, with test names and Postgres error contexts following.create_userandcreate_postkeep "create" — they are not credential mints.No behaviour changes anywhere — documentation, naming, and glossary only. The full
citask passes.Closes #79. Closes #82.