Skip to content

reference-approval-controller.md

Latest commit

 

History

History
84 lines (62 loc) · 2.59 KB

reference-approval-controller.md

File metadata and controls

84 lines (62 loc) · 2.59 KB
Raw

Build the reference approval controller

This Developer Reference uses two buttons to demonstrate approval/1. It is not the only or default shape of a Nexting device. A successful local test proves a bounded physical approval path, not production identity, signed firmware, live Agent mapping, or physical security.

1. Gather and wire

You need a Seeed XIAO nRF52840 or XIAO nRF52840 Sense, two normally-open momentary buttons, jumper wires, and a data-capable USB-C cable.

Button Connect
Allow D0 to GND
Deny D1 to GND

The reference firmware enables internal pull-ups. Do not connect either input to 3.3 V.

2. Get the exact release

git clone --branch devices-v0.2.0-experimental.2 --depth 1 \
  https://github.com/Nexting-ai/nexting.git
cd nexting/devices

3. Build

On macOS or Linux with Python 3.11+:

./scripts/bootstrap-zephyr.sh \
  --board xiao-nrf52840-sense \
  --install-sdk \
  --build

The script creates an isolated Python environment beside devices/, initializes the pinned Zephyr 4.3.0 workspace, installs west 1.5.0, optionally installs Zephyr SDK 0.17.4, and builds:

devices/build/xiao-nrf52840-sense/zephyr/zephyr.uf2

Rerunning is safe. Use --dry-run to inspect every resolved version and path without changing the workspace.

4. Flash

  1. Connect the XIAO over USB-C.
  2. Double-press Reset. A volume named XIAO BLE appears.
  3. Copy zephyr.uf2 to that volume. It ejects automatically.
  4. The Pending LED remains off until a Host presents an approval.

5. Prove the public device path

From nexting/devices, run the protocol and firmware checks:

npm run test:reference
npm run test:firmware

These checks prove bounded framing, the approval/1 state machine, and the reference firmware build without requiring Agent credentials or a custom Host. When developer-device enrollment is available, use the official Nexting App to pair the board and perform the same physical interaction.

6. Understand the evidence boundary

The result is a local protocol proof. It is not production enrollment or a live Agent connection, and it does not make this Developer Reference a certified approval device. Before a production claim, add authenticated application identity, signed firmware, explicit enrollment and revocation, and the dated real-board evidence required by Conformance and Board verification.

Public third-party enrollment is tracked in availability.json. Do not use an unpublished App build or weaken BLE authorization while that gate is closed.