You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/specifications/PSP-3 - Sigchain and Envelope.mdx
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,3 +17,29 @@ Provided by the Grant Payload (PCAP-01):
17
17
- action: A single verb string (e.g., "deploy:to_env").
18
18
- resource: A single resource identifier (e.g., a URI).
19
19
- bind: The Bind object containing capability constraints.
20
+
21
+
Normative rules:
22
+
23
+
- Grants MUST be written on the issuer's (P's) sigchain.
24
+
- The envelope MUST include iss, sub, exp, and a valid signature per SIGCHAIN-01; Presentations beyond exp are invalid.
25
+
- payload.typ MUST be "ClaimGrant".
26
+
- A Grant MUST carry exactly one action (verb) and exactly one resource.
27
+
- action MUST reference a registered verb; for attenuation, child.action MUST equal parent.action unless the verb registry defines a subset sub-verb accepted by TAP.
28
+
- resource MUST conform to a registered scheme; for attenuation, resource.child MUST be a subset of resource.parent per the scheme's subset relation.
29
+
- bind MUST be enforceable by CEPs and MUST be included as a bind_snapshot in the Access PoAR (PRSC-01).
30
+
- Required Bind dimensions declared by the verb's registry entry (e.g., nbf/exp, channel, policyRef) MUST be present; otherwise the CEP MUST deny.
31
+
- Unknown verbs, unknown resource schemes, or unresolvable scheme comparators MUST cause deny.
32
+
- CEPs MUST check revocation status (see Revocation) before enforcement.
33
+
- Presentations MUST reference the Grant via its canonical digest (grant_ref) derived per SIGCHAIN-01.
34
+
35
+
Recommended fields:
36
+
37
+
- aud: DID or array of DIDs of acceptable enforcers (e.g., `"did:pk:P"` or `["did:pk:P","did:pk:R"]`)
38
+
- purpose: semantic hash or descriptor of intent (e.g., `"sha256:artifact-H"`, `"door-visit-123"`)
0 commit comments