Future architecture — REL-DEV-HUM: Device ↔ Human
Planned Device ↔ Human relationship; not current Nautilo behavior.
Stable ID: REL-DEV-HUM
Entities: DEV (Device) ↔ HUM (Human)
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
Installation and workstation identities exist, but a unified durable multi-user Device entity does not.
Target architecture: installation and session identities exist today, but Nautilo does not yet have one durable, first-class Device ownership model.
Design
The target model says Humans use or own Devices. Cardinality is expected to be M:N: one Human may use many Devices and one Device may host sessions for multiple Humans. Agents are Server-resident; they reach local hardware through Relays.
This edge becomes security-sensitive when application encryption and durable Device identity ship: a single Device grant should be revocable without revoking the Human's other authorized clients. The final grant/key model is still owner-designed future work.
Implementation
No human_devices table exists today. Auth sessions, Electron installation
identity, and Relay-token installationId provide partial runtime identities,
but none is a canonical first-class Device entity.
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.