One authored definition, multiple generated artifacts.
DEVELOPERS / Architecture guide

Authoring to runtime

Follow a shared project model into generated views, configuration and runtime reconciliation.

Concept artwork · One authored definition, multiple generated artifacts.
SYSTEMS / IN DETAIL

Publishing is a state transition, not a file copy.

A configuration is only useful when the edge can receive and interpret it. The engineering record separates authored drafts, published revisions and runtime readiness rather than treating an upload as completion.

ENGINEERING / FOLLOW THE FLOW
CONCEPTUAL MECHANISM 01 / 04
BoundaryResponsibilityEngineering consideration
ReadinessGateway ready · network reachable · protocol connectedReport completion only after the required edge confirmations.
Version orderingA revision sequence with explicit orderingNumeric comparison avoids the “9 versus 10” string-ordering failure.
Atomic promotionA coherent published revisionAvoid presenting a partially updated configuration as a complete release.

What if the project has no conventional chart?

Valid project shapes need explicit handling. Engineering work includes bootstrap drafts and LifeSmart-only configurations. A reliable publisher validates the actual project shape instead of assuming that every installation follows one chart-based path.

PLATFORM ARCHITECTURE / VERIFIED AUTHORING PATH

One authored model, multiple consumers

Select a layer to explore its role.

ONE MODEL / GENERATED VIEWS
CONFIGURATION TO OPERATION
01 / SPATIAL AUTHORING

Room polygons, device placements and project versions provide the spatial context on which engineering configuration depends.

room → device → location

The authored model and its generated views are distinct from the runtime systems that execute automation.

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

Discuss this integration

Continue through the guides

All developer guides