DEVELOPERS / Integration guide

Model & identity

Separate stable spatial identity, ownership and capabilities from protocol addresses.

Concept artwork · Stable identity across changing representations.

SYSTEMS / IN DETAIL

Identity follows the installed environment.

The spatial hierarchy and authorisation hierarchy intersect, but they are not identical. Project, delivery unit, home and room each carry a different responsibility.

ENGINEERING / FOLLOW THE FLOW

CONCEPTUAL MECHANISM 01 / 04

Boundary	Responsibility	Engineering consideration
Delivery unit	An engineering anchor	One ETS file can cover multiple homes; anchoring it to a single home loses scope.
Tenant and role	Authority to act	The acting user does not replace the owning tenant or contractor scope.
Reconciliation	Agreement after a revision	Remove stale room and device relationships as well as adding new ones.

Why does deletion need as much attention as creation?

A successful sync can still leave orphaned entities if it only inserts and updates. Reconciliation must identify objects no longer present in the selected revision. Unbinding also needs transaction boundaries so a partial failure cannot leave contradictory ownership or membership.

01 / MODEL & IDENTITY

Separate the entity
from its transport.

A device needs spatial identity and capability context before a protocol address can be useful. Studio authors that context; generated views serve App, Panel, configuration and edge consumers.

Read the reconciliation mechanism

CONCEPTUAL MODEL / NOT AN API SCHEMA

Project / owning tenant
 └─ Delivery unit / engineering file scope
     └─ Installed home
         └─ Room / spatial identity
             └─ Device / stable identity
                 ├─ Capability
                 ├─ Control binding + data type
                 ├─ Status binding + availability
                 └─ Presentation / resident override

Attribute authority is explicit. The acting user is not a substitute for the owning tenant.

Engineering guide · Conceptual representations describe design boundaries, not a public API contract. Discuss project-specific access with our team.

Discuss this integration