net: party envelopes are bearer documents in the identity flow - #925
Merged
Conversation
The subject signs its party once, audience-free; the same envelope registers, publishes, and verifies with no per-hop signatures. Delivery intent comes from the request token, and the Authority and verifier countersignatures carry the directed iss/aud statements. Deferred who disclosures remain audience-bound, and document deliveries keep the signed aud requirement. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Aug 11, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #925 +/- ##
=======================================
Coverage 94.99% 94.99%
=======================================
Files 327 327
Lines 17712 17732 +20
=======================================
+ Hits 16825 16845 +20
Misses 547 547
Partials 340 340 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Signatures all cover the same payload, so any envelope holder can permute them and position cannot be trusted. VerifyEnvelope is replaced by VerifyParty — the subject is the address the party document declares as its gobl: endpoint, attested by a valid self-signature, which also enforces the previously unchecked endpoint/subject match — and VerifyDelivery, which returns the single issuer with a valid signature bound to the receiving inbox. Who compares the declared subject to the fetched address. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
Follow-up to #924, from review of the live flow: the audience-bound subject signatures required by the registry and verifier inboxes are redundant with the request token, which already carries the fresh origin+destination statement for every request.
Spec change (§2, §5.3, §6.2, §8.3): party envelopes in the registration and verification flows are bearer documents — the subject signs once, audience-free, and that same envelope registers, publishes at
/who, goes to the verifier, and renews, with no per-hop signatures. The directed statements are the countersignatures (iss=<authority|verifier>,aud=<subject>). Each receiving role applies its own rule: registry → token + eligibility; verifier → the registry's countersignature; subject's own inbox → party envelopes whose subject is itself (the returns). Deferred who disclosures remain audience-bound (thataudis what marks them private), and document deliveries keep the signedaudrequirement — the token cannot prevent cross-inbox replay of a captured document, the signed audience does.Third-party submission of a published (public) envelope is at worst an unsolicited renewal: results only ever deliver to the subject's inbox, and endorsements are scoped by each client's trust list.
No code changes in
net—VerifyEnvelope's audience search stays for documents. Companion PRs relax the registry and verifier inboxes: invopop/gobl.lookup#7 and invopop/gobl.kyb.sandbox#4.🤖 Generated with Claude Code