Future architecture — REL-DEV-RLY: Device ↔ Relay
Planned Device ↔ Relay relationship; not current Nautilo behavior.
Stable ID: REL-DEV-RLY
Entities: DEV (Device) ↔ RLY (Relay)
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
Relay tokens bind user and installation and sessions bind Relay identity; the canonical Device ontology is still future work.
Target architecture: Relay tokens can bind a user and installation, but the installation is not yet a canonical durable Device entity.
Design
The target model says Devices host Relays. A single Device may eventually host
multiple Relay profiles, while each connected Relay runtime executes on one
installation. Today Electron can host the embedded desktop Relay and
bin/nautilo-relay supplies a headless variant. The proposed
native/mac-relay/ implementation is still a placeholder.
Implementation
Relay tokens persist userId, actorId, and optional installationId; live
registration supplies Relay identity and capabilities. There is no persistent
canonical device_id relationship.
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.