spec: [proposal] USER-ID-1 — participant identity resolution specification - #54
spec: [proposal] USER-ID-1 — participant identity resolution specification#54JarbasAl wants to merge 1 commit into
Conversation
|
Warning Review limit reached
Next review available in: 59 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Merge-ready (MERGEABLE, dev merged in). Template conformance: header present, RFC-2119 boilerplate present, sections numbered 1–9, See also section. Fixed: USER-ID-1 was absent from README spec table and CHANGELOG — both added. Cross-references to OVOS-SESSION-1, OVOS-TRANSFORM-1, OVOS-BRIDGE-1 are forward-pointing specs (correct for an in-review spec). Note: after #55 merges, GLOSSARY.md in this branch will need |
JarbasAl
changed the title
Squashed from: - spec: USER-ID-1 — trust-model rework: gate invariant, level decay, resolution order - spec: cite the SESSION-1 field registry as §2.2 - USER-ID-1: user identity resolution specification Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
JarbasAl
changed the title
1 participant
Closed by the author. Emergent-already — closing on the author's own analysis, reopen if you disagree. Per-peer identity and isolation already fall out of the two primitives:
session_idscopes state per peer/conversation on every Message, and the reply swap keeps the peer addressable along the whole chain.user_id/auth_levelwould re-implement the identitysession_idalready carries. If authorization is wanted it is a layer-2 concern built on evidence this envelope deliberately does not carry.