Interpretation notes
spec 1.0-draft-1
This guide links cross-cutting protocol rules to their normative sections. It is informative; the linked requirements define implementation behaviour.
| Topic | Requirement |
|---|---|
| Handle encoding and derivation | A3 exact alphabet, JCS domain-separated framing, 32-character new handle, recipient entry aliases |
| Request disclosure ceiling | A5 single scalar request intersected independently with each grant-domain ceiling |
| Declared-only and confidence combination | A5 logical OR and maximum threshold |
| Token validity | A6 one-hour valid UTC example; complete token rules explicit |
| Sensitivity and inference | A4/A14 prohibit inference for non-inferable, sensitive and safety keys |
| Vocabulary and rendering | Appendix A and generated core.json define all 30 vocabulary 1.1 keys; candidates rejected |
| L1 versus L2 structure | A5 identifier-free structure allowed at L1; names only when the key explicitly allows them at L2 |
| Sparse-level and free-text fallback | A5 highest supported permitted level; approved text or omission |
| Signature boundaries | A5/A15 exact signed object boundary and representations |
| Briefing authority and read count | A7 shared authorised transaction, both domains required, one read |
| Advertising policy | A6.7 explicit three-key, adult-only, one-read policy |
| Temporal representation | A4 explicit kind, interval, overlay target/activation/selection |
| Contributor identity, correction and replay | A14 strict event schema, authenticated source, stream namespaces and replay rules |
| Role claims and certification | A17 role/version/category evidence; self-declaration only |
| Global IDs and migration privacy | A3 recipient-specific aliases, owner-only canonical IDs, no credential redirects |
| Purge polling after grant expiry | A10 authenticated client lifecycle channel with no record-read authority |
| Export encryption and delegated offers | A11 exact JWE/KDF; A6 exact OAuth exchange/redemption |
| Legal equivalence claims | A16.1 informative support mapping; A16.2 to A16.8 normative deployment evidence, not legal certification |
See conformance status for implementation and test coverage.
References to other standards and projects describe intended technical alignment only and do not imply endorsement or partnership.