# Researching a deterministic approval and verification layer for SmartThings **URL:** \ **Category:** Developer Programs\ **Created:** [October 15, 2026, 3:59pm UTC](https://community.smartthings.com/t/researching-a-deterministic-approval-and-verification-layer-for-smartthings/311563 "2026-10-15T15:59:27Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Edward\_Chen](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/edward_chen/32/251898_2.png) [@Edward\_Chen](https://community.smartthings.com/u/Edward_Chen)\ **Post date:** [October 15, 2026, 3:59pm UTC](https://community.smartthings.com/t/researching-a-deterministic-approval-and-verification-layer-for-smartthings/311563/1 "2026-10-15T15:59:27Z")
I am researching a SmartThings adapter for Spatial OS, a platform-neutral layer that separates conversational intent from physical device execution using a spatial graph, typed policy, shadow preview, explicit approval and post-action state verification. Home Assistant is the only live connector today. This is not a SmartThings-compatible release announcement. Before registering a Service Integration, I would value developer feedback on the API boundary: - Can OAuth-scoped device access plus subscriptions support a reliable command-and-verify loop? - Should safe automations compile to Rules, remain in an external service, or use both? - Which capabilities should always require explicit human approval? - What lifecycle or rate-limit constraints are easy to miss when building a long-running integration? Architecture and virtual-home demo: > **[Spatial OS | Verified intelligence for the open smart home](https://spatial-os-core.pages.dev/?utm_source=smartthings&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 SmartThings design partners before writing the adapter. Technical objections are welcome. - Spatial OS Team