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

**URL:** <https://discourse.nodered.org/t/would-a-deterministic-approval-and-verification-layer-add-value-to-node-red-smart-home-flows/101656>\
**Category:** General\
**Created:** [18 August 2026 13:47 UTC](https://discourse.nodered.org/t/would-a-deterministic-approval-and-verification-layer-add-value-to-node-red-smart-home-flows/101656 "2026-08-18T13:47:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![spatialos\_core](https://avatars.discourse-cdn.com/v4/letter/s/43a26b/32.png) [@spatialos\_core](https://discourse.nodered.org/u/spatialos_core)\
**Post date:** [18 August 2026 13:47 UTC](https://discourse.nodered.org/t/would-a-deterministic-approval-and-verification-layer-add-value-to-node-red-smart-home-flows/101656/1 "2026-08-18T13:47:20Z")

</div>

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:

> **[Spatial OS | Verified intelligence for the open smart home](https://spatial-os-core.pages.dev/?utm_source=node_red&utm_medium=community&utm_campaign=design_partners)**
>
> Describe the outcome. Inspect every device action. Simulate, approve and verify before the home moves.

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

Spatial OS Team

---

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [19 August 2026 04:51 UTC](https://discourse.nodered.org/t/would-a-deterministic-approval-and-verification-layer-add-value-to-node-red-smart-home-flows/101656/2 "2026-08-19T04:51:20Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![spatialos\_core](https://avatars.discourse-cdn.com/v4/letter/s/43a26b/32.png) [@spatialos\_core](https://discourse.nodered.org/u/spatialos_core)\
**Post date:** [21 August 2026 02:07 UTC](https://discourse.nodered.org/t/would-a-deterministic-approval-and-verification-layer-add-value-to-node-red-smart-home-flows/101656/3 "2026-08-21T02:07:16Z")

</div>

Thanks — fair criticism. For mature Node-RED setups with explicit business rules, Spatial OS should not be positioned as a replacement or an extra $19 layer. We have not built a Node-RED node; the current page is a virtual workflow, not a release.

The trust point is also valid. The product needs a verifiable operating identity, contact path and real integration before asking this forum for further feedback. I will not make compatibility or value claims here until that exists. Thank you for the direct feedback.