USER-ID-1: user identity resolution specification#54
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ 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 |
Closes #53
What this PR adds
spec/user-id/ovos-user-id-1.md— new specification for user identity resolution and authentication levels at the bus protocol layer.Companion edit:
ovos-session-1.md— seven new fields added to the §2.1 field registry.Spec summary
Skills read
session.user_idandsession.auth_levelfrom the message they receive on dispatch — no query round-trip, no race condition. The recognition plugin (transformer chain, standalone service, or bridge injection) populates the fields before the utterance enters the pipeline.Four enrolled signals → four opaque session IDs:
voice_id— voice-print match (audio transformer, pre-STT)face_id— face-print match (out-of-band camera plugin;site_idselects camera)name_id— self-declaration match ("I am Alice"; utterance transformer, post-STT)passphrase_id— secret-phrase match (utterance transformer, post-STT)auth_level0–5: anonymous → configured default → self-declared → single biometric → multi biometric → explicit credential.Identity persists within a session — once established,
auth_levelcarries forward without re-recognition; skills can prompt for an upgrade via CONVERSE-1response_mode.Layer-2 bridges may inject all fields directly (e.g. authenticated chat interface, single-user satellite terminal via
default_user_id).Files changed
spec/user-id/ovos-user-id-1.mdovos-session-1.mdRelated