Future architecture — REL-CHN-DEV: Channel ↔ Device
Planned Channel ↔ Device relationship; not current Nautilo behavior.
Stable ID: REL-CHN-DEV
Entities: CHN (Channel) ↔ DEV (Device)
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
No canonical Channel–Device relationship exists; MLS/device fan-out belongs to the future security model.
Target architecture: Nautilo does not currently have a durable, first-class Device entity or Device-specific channel-key relationship.
Design
The target model says Devices host client Channels. Cardinality would be M:N: one Device may host multiple client surfaces, while one logical Channel type may appear on many Devices. Current clients and sessions do not materialize this as one canonical relationship.
Device-specific application-encryption grants may eventually attach at this edge, but the protocol and durable Device model are not yet release-current.
Implementation
No dedicated join table exists today. Client/session/install identifiers are runtime-specific. Durable Device identity and per-Device application keying remain future work.
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.