docs: SD-JWT predicate disclosure for mandates#42
Merged
Conversation
Issue #18: verifying a plaintext Mandate hands the counterparty the negotiation envelope (max_value = reservation price, escalation_threshold, allowed_counterparties = relationship map). s5.3 (M4) now requires that Mandates SHOULD be issued as SD-JWT VCs with predicate support — strongly RECOMMENDED for contracting scope — proving 'value within cap' and 'counterparty in allowed set' without disclosing cap or list. The inherent escalation-time threshold leak is documented as acceptable. s6.6 cross-references mandates explicitly; new s11 threat row; Appendix C updated.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Eleventh PR of the v0.3 draft.
Issue #18 — mandate verification disclosed negotiation-sensitive caps: for an action to be binding, the counterparty must check the Mandate (§5.3) — and a plaintext Mandate hands them
max_value(the Principal's reservation price),escalation_threshold, andallowed_counterparties(a business-relationship map). The spec already had the right tool (§6.6 SD-JWT predicates) but never applied it to its most negotiation-sensitive credential.contracting-scope Mandates strongly RECOMMENDED — so the Agent proves "this action's value is within my per-action cap" and "this counterparty is within my allowed set" without disclosing the cap or the list.Closes #18
Affected spec section(s)
§5.3 (M4), §6.6, §11, Appendix C.
Trust impact
None. No trust root moves; counterparties can verify the same authority predicates as before with strictly less information disclosed. Strengthens design goal §3.1(7) (privacy-preserving, selective disclosure off-chain).
Checklist
docs-checkpasses