Would a deterministic approval and verification layer add value to Node-RED smart-home flows?

General
1

I am researching a Node-RED adapter for Spatial OS, a platform-neutral policy layer that keeps natural-language intent separate from physical device execution.

The core builds a spatial graph, compiles requested outcomes into typed actions, runs a shadow preview, asks for explicit approval, and verifies observed state after execution. Home Assistant is the only live connector today. This is not a Node-RED-compatible release announcement.

Before writing code, I would value feedback from Node-RED users and node developers:

  • What is the right integration boundary: custom nodes, the Admin API, a runtime plugin, or an MQTT/HTTP bridge?
  • How should an external service distinguish a command being accepted from the physical outcome actually being observed?
  • Which smart-home flow actions should require preview or explicit approval by default?
  • Would a small set of plan / approve / execute / verify nodes fit Node-RED well, or would that add unnecessary ceremony?

Architecture and virtual-home demo:

I am looking for two design partners before implementing an adapter. Technical objections are especially useful.

Spatial OS Team

2

At 19$ per month....????.....my smart home automation based on Node-RED has managed fine many years now without the need for such additional layer. I have my own "business rules" fully implemented. For me personally that would not add value, only add new layer of cost

In addition, your site seem to be a bit too anonymous for me to be trusted, no company or contact/location details tells me instinctively, raising a warning flag