Describe a site's devices — what's there, how it's wired together, what each can measure or do, and concretely how to read and control it — as a document any consumer ingests with zero per-vendor code. The same model is scale-free: one battery cell, a home, a building, or a whole city.
A graph of nodes (typed relationships: contains / measures / controls / powers) → each offering capabilities (domain-agnostic read/control) → with concrete bindings reachable via ranked access paths (gateway or cloud, with fallback) → a protobuf data plane over MQTT, typed by the document.
JSON Schema 2020-12. The canonical $id.
Protobuf telemetry + control over MQTT.
A vendor-neutral home site (validates).
Spec, governance, licence, RFCs.
A live editor + validator (Swagger-Editor style) is coming at editor.lattice-spec.org — paste a document, validate it, and visualise the topology graph.
Aligns with Eclipse Sparkplug B (data plane), W3C WoT Thing Description (capabilities), ETSI SAREF (vocabulary), IEC CIM / NGSI-LD (city/grid), and feeds IEEE 2030.5 / OpenADR. The new bit is the cross-vendor, scale-free orchestration graph with independent read/control routing and access-path fallback.