[RCP-54] ULI Resolution Protocol#222
Draft
darnjo wants to merge 2 commits into
Draft
Conversation
darnjo
force-pushed
the
221-uli-resolution-protocol
branch
2 times, most recently
from
June 27, 2026 22:08
12728f8 to
653041d
Compare
darnjo
force-pushed
the
221-uli-resolution-protocol
branch
4 times, most recently
from
June 28, 2026 01:12
be053a5 to
68b4342
Compare
Specifies the Unique Licensee Identifier (ULI) resolution protocol: a threaded ActivityPub conversation across a network of certified resolvers that resolves a licensee to a single linking identifier, with no licensee data stored on or pooled through the network. Covers participation and data isolation (pre-arranged OAuth2 authorization), the broadcast model (a shared resolver collection, mandatory resolvers named by Mention, an identifiability gate), reply obligation, floor(2/3 R) consensus, and a ULI lifecycle built from a small set of primitives (consensus-gated mint, silent local adopt, holder-initiated tombstone/redirect, merge as a composition, decline by re-broadcast) with self-healing correction. Proof of resolution is per-org signed attestations over a keyed, PII-free licensee reference committed in an RFC 6962 Merkle tree. Adds credit-score-style weighted matching, a Data-Dictionary-linked ULI field table, a public PII-free governance feed, sandbox and continuous certification, and five schema-validated worked examples. Tracks #221. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
darnjo
force-pushed
the
221-uli-resolution-protocol
branch
from
June 29, 2026 00:01
68b4342 to
2cf8450
Compare
Member
Author
|
Added a section that preserves the origin and requires a signature to mint a ULI. Do we need this? Should we track the origin and its authenticity? cc: @psftc |
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.
VIEW PROPOSAL
Draft proposal for RCP-54, the ULI Resolution Protocol. Tracks #221.
Adds
proposals/uli-resolution-protocol.md— a resolution protocol for the RESO Unique Licensee Identifier (ULI) over W3C ActivityPub. A network of certified resolvers broadcasts a licensee, replies match or no match, and reachesfloor(2/3 × R)consensus to mint or adopt a single linking identifier. No licensee data is stored on or pooled through the network; it is referenced only by OAuth2-protected RCF links.Highlights:
Ris its certified ∩ compliant ∩ active view.The five worked examples in §2.12 are schema-validated against Data Dictionary 2.0 (Member resource, strict).
Status: IN PROGRESS — the draft is content-complete (all sections, the EULA and the license are filled) and open for Workgroup review; it has not been ratified. See #221 for discussion.