Skip to content

In development preview

Ask Sadie. Review the action. Inspect the result.

DHoT (DigitalHuman of Things) is our work toward connecting Sadie and ThoxHuman to commissioned THOX device actions. The experience is designed for ThoxOS: a concrete plan to review, bounded execution and a result you can inspect. It is a capability across our ecosystem, not a fourth platform.

Sadie is openly synthetic. This page walks through the flow with a fixed example; it does not connect to any device. The local engineering POC uses simulated nodes. Physical firmware and production ThoxOS integration remain under development.

Walk through one request

Start with a supported request

You

Turn Desk on for 5 seconds; identify Lab.

Desk and Lab are the local demo's simulated nodes. The default POC uses a finite request grammar or validated structured proposals, not live language-model planning. ThoxOS and ThoxHuman integration are receiving-application work, not a service connected to this page.

Stage 1 of 4

Three principles behind DHoT

  • A proposal is not permission.

    Whole-plan validation, owner checks and execution rules run in code. The default demo uses a finite local grammar; evaluated model planning is a separate integration.

  • You review the exact action.

    A device-changing request waits for human approval tied to its concrete steps. An agent cannot approve its own proposal. Commissioning is operator-controlled.

  • An unknown result stays unknown.

    Matching authenticated replies support the reported result. Missing evidence, partial execution and simulated state remain explicit; a portrait or animation does not prove actuation.

What this preview illustrates

Node status
Illustrates a commissioned node's reported fixture state; not a new environmental or battery sensor.
Status light
The local POC supports off or timed on, with ON leases from 0.1 to 30 seconds. Physical output commissioning and measurement remain pending.
Identify
The local POC supports a bounded identify interval, from 0.1 to 5 seconds. This page only illustrates the review flow.

Relays, power control, general-purpose pins and displays are not part of this public walkthrough. The local POC separately contains allowlisted relay and pin actions for low-energy bench fixtures; that is not verified hardware support or a customer release.

Safeguards

  • The POC authenticates commands and results per device, checks expiry and boot state, and persists replay counters before an output action.
  • Owners, routes and allowed outputs are commissioned outside the browser. The model cannot enroll a new output or choose an arbitrary pin.
  • The local default makes no cloud-planner call. Optional hosted identity introduces a network dependency. Authentication alone does not encrypt the device link.
  • Revocation blocks future authority after it completes; it cannot retract an already-sent command. Output leases are software bounds, not physical safety certification.

Where the preview stands

As of October 5, 2026, DHoT v0.2.0 records local software, real HTTP and shared-C simulated-node checks. Browser component evidence is separate from browser-network and hardware proof. The new firmware build, physical bench validation, deployed routes and full receiving-application integration remain outstanding. It is not available to customers yet.

Ask about developer access