The ULI Resolution Protocol gives every licensed real estate professional one stable linking identifier (the Unique Licensee Identifier), de-duplicating licensees across MLSs and markets via a threaded ActivityPub conversation among certified resolvers. Drafted with RESO ULI Workgroup approval; proposed as proposals/uli-resolution-protocol.md (PR #222).
§2.1–2.5, 2.11 — Resolution over ActivityPub
Participation with pre-arranged OAuth2 authorization (a node shares its PII-safe ULI subset only with the resolvers it relies on, and nothing is stored on the network), vanilla ActivityStreams 2.0 vocabulary, the PII-safe ULI field set behind OAuth2-protected RCF links, the identifiability-gated broadcast to a shared resolver collection, and reply obligation (active resolvers SHOULD reply match or no match; Mention-named mandatory resolvers MUST).
§2.6–2.7, 2.12 — Consensus and lifecycle
floor(2/3 × R) consensus plus a mandatory-resolver gate (each node names its own by Mention). The ULI lifecycle is composed from a small set of primitives: consensus-gated mint, silent local adopt, holder-initiated tombstone/redirect, merge (a composition rather than a special case) and decline by re-broadcast, with self-healing correction. Five worked examples in §2.12.
§2.8 — Proof of resolution
Per-org signed attestations over a keyed, PII-free licensee reference (HMAC under a per-resolution key delivered off the ActivityPub layer), committed in an RFC 6962 Merkle tree; a published root proves the consensus without de-anonymizing the licensee.
§2.9 — Matching and scoring
Credit-score-style weighted matching (deliberately not a probability), a network-adopted weight set and thresholds, a static frequency table, and exact-parity certification.
§2.10 — Governance feed and resolver discovery
A public, PII-free ActivityPub feed of membership and parameter events; R = certified ∩ compliant ∩ active.
§3 — Certification
Per-component and continuous: a sandbox onboarding gate (exhaustive scoring and search parity against a reference oracle, plus identity, protocol, proof and HMAC key-endpoint checks) and continuous conformance monitoring.
Links
The ULI Resolution Protocol gives every licensed real estate professional one stable linking identifier (the Unique Licensee Identifier), de-duplicating licensees across MLSs and markets via a threaded ActivityPub conversation among certified resolvers. Drafted with RESO ULI Workgroup approval; proposed as
proposals/uli-resolution-protocol.md(PR #222).§2.1–2.5, 2.11 — Resolution over ActivityPub
Participation with pre-arranged OAuth2 authorization (a node shares its PII-safe ULI subset only with the resolvers it relies on, and nothing is stored on the network), vanilla ActivityStreams 2.0 vocabulary, the PII-safe ULI field set behind OAuth2-protected RCF links, the identifiability-gated broadcast to a shared resolver collection, and reply obligation (active resolvers SHOULD reply match or no match;
Mention-named mandatory resolvers MUST).§2.6–2.7, 2.12 — Consensus and lifecycle
floor(2/3 × R)consensus plus a mandatory-resolver gate (each node names its own byMention). The ULI lifecycle is composed from a small set of primitives: consensus-gated mint, silent local adopt, holder-initiated tombstone/redirect, merge (a composition rather than a special case) and decline by re-broadcast, with self-healing correction. Five worked examples in §2.12.§2.8 — Proof of resolution
Per-org signed attestations over a keyed, PII-free licensee reference (
HMACunder a per-resolution key delivered off the ActivityPub layer), committed in an RFC 6962 Merkle tree; a published root proves the consensus without de-anonymizing the licensee.§2.9 — Matching and scoring
Credit-score-style weighted matching (deliberately not a probability), a network-adopted weight set and thresholds, a static frequency table, and exact-parity certification.
§2.10 — Governance feed and resolver discovery
A public, PII-free ActivityPub feed of membership and parameter events;
R = certified ∩ compliant ∩ active.§3 — Certification
Per-component and continuous: a sandbox onboarding gate (exhaustive scoring and search parity against a reference oracle, plus identity, protocol, proof and HMAC key-endpoint checks) and continuous conformance monitoring.
Links