Future architecture — REL-DEV-RMS: Device ↔ Room
Planned Device ↔ Room relationship; not current Nautilo behavior.
Stable ID: REL-DEV-RMS
Entities: DEV (Device) ↔ RMS (Room)
Relationship status: target
Future architecture — not current behavior
This relationship describes the planned durable Device and application-encryption model. Current installation, session, or Relay identifiers do not make it implemented.
Audited relationship
Durable per-Device Room/MLS membership is future application-encryption work.
Target architecture: Room membership remains Actor-based. Devices do not become direct Room members; future cryptographic access is derived through the owning Human's Crypto Domain participation and the Room's Namespace binding.
Design
This relationship becomes load-bearing when application-level encryption and durable Device identity ship, but it remains derived rather than a direct Device↔Room membership edge. A Human may authorize many crypto devices; each device participates in every relevant Crypto Domain for that Human. A Room's stable Namespace binds to the exact-human-set Domain, so a device reaches Room history through Domain participation plus the Namespace keyring. Revoking a device advances every affected Domain without editing Room membership.
Agents are not devices or Domain participants. They receive bounded grants to the AI-readable branch.
Implementation
Not implemented. Today Rooms have Actor members and no durable crypto-device identity or Domain participation. Wave 7 owns device enrollment, recovery, Delivery Service, revocation, and the durable schema; Wave 6 adds only dark Domain/Namespace storage and no Device behavior.
Verification state
This article remains at the original relationship granularity for AI and
maintainer use. Its current-versus-target classification was reconciled before
migration; public code-anchor verification remains in progress against
Nautilo 4b3ea604.