Matter Unified Smart Home Devices. The Protocol Still Separates Data From Authority.
by Nick Clark | Published March 27, 2026
Matter achieved what the smart home industry could not for a decade: a single interoperability standard backed by Apple, Google, Amazon, and Samsung. Devices from different manufacturers work together through a common application layer. But Matter messages carry application payloads without embedded routing policy, trust scope, or propagation governance. The controller node manages the fabric. Messages are content the network moves. Resolving this requires protocol semantics where authority travels with the object.
Matter's achievement is significant. Ending the fragmentation between HomeKit, Google Home, Alexa, and SmartThings required coordinating the largest companies in consumer technology around a shared standard. The gap described here is not a criticism of that achievement. It is an observation about the protocol architecture that interoperability alone does not resolve.
The fabric governs. Devices participate.
Matter organizes devices into fabrics. A fabric is a trust domain managed by a controller, typically a smart speaker or hub. The controller commissions devices into the fabric, issues operational certificates, and maintains the access control list that determines which devices can communicate with which.
When a Matter device sends a message, it sends an application-layer command such as turning on a light or reporting a sensor reading. The message is encrypted with fabric-scoped keys. But the message itself carries no routing policy, no trust scope beyond the fabric boundary, and no propagation rules. The fabric's controller holds the governance. The message is a command the fabric delivers.
Multi-fabric and bridging expose the gap
Matter supports multi-fabric operation, where a single device can belong to multiple fabrics simultaneously. A light switch might be in both an Apple Home fabric and a Google Home fabric. But each fabric governs independently, and there is no protocol-level mechanism for governance to span fabrics.
Bridging between Matter and legacy protocols like Zigbee or Z-Wave introduces another governance boundary. The bridge translates commands but does not translate governance. A command crossing the bridge loses whatever fabric-scoped authority it carried and enters the legacy protocol's governance model.
In both cases, the governance of how messages flow, who can send them, and what authority they carry is held by the infrastructure, not by the messages themselves.
What memory-native protocol semantics address
A memory-native protocol embeds routing policy, trust scope, and mutation permission into the content itself. Each message carries its own governance rather than depending on fabric infrastructure to enforce it.
In a smart home operating on memory-native semantics, a door lock command could carry trust constraints that persist across fabric boundaries, validated at each node against locally held policy. A sensor reading could carry propagation rules specifying which systems can receive it and under what conditions. Multi-fabric governance would be handled at the protocol level rather than requiring each fabric controller to independently enforce access control.
The remaining gap
Matter solved device interoperability. The remaining gap is in the protocol semantics: whether messages can carry their own governance across fabric boundaries, trust domains, and protocol bridges. That requires a protocol layer where authority is intrinsic to the object being transported.
