# HSIMC · Physical T736 → Direct ChatGPT Remote MCP

**Public engineering milestone C0-001 · 2026-10-15**  
**Product:** T736 MCP-Ready Reality Node / HSIMC R&D Product 001  
**Reference hardware:** AIS B, Allwinner T736 development board  
**Accepted result:** Device-specific and **read-only** direct ChatGPT tool calls  
**Source status:** User-authorized laboratory trial, not production certification.

## 1. The actual milestone / 真实的第一步

On 15 October 2026 an authorized user connected an AIS B T736 Ubuntu ARM64 device to the Desktop Commander Remote MCP service, approved its device-code pairing, and ChatGPT independently invoked read-only tools against that **registered device itself**, not through Mac SSH.

Four tool classes were actually tested:

| Tool | Observed acceptance |
| --- | --- |
| **ping** | The registered AIS B endpoint responded directly |
| **read_file** | Returned actual Ubuntu system-release information |
| **list_directory** | Listed a local engineering directory on AIS B |
| **start_process** | Ran benign read-only commands reporting local Linux, HDMI/LightDM and storage presence |

The physical OS observed was Ubuntu 24.04.3 LTS, AArch64, with the prior working HDMI graphical desktop. Desktop Commander Remote 0.3.0 used a compatible, independently installed Node.js 22 LTS runtime.

This is stronger evidence than "the app is installed" or "a Mac can SSH into the board": the model's connected tool selected AIS B as a separate remote endpoint, and the returns came from that board.

## 2. What the work consisted of / 工程过程

1. **Keep a proven Reality intact:** Start from AIS B's existing native Linux, HDMI, XFCE/LightDM and CJK browser working state. No bootloader, device-tree or display driver replacement is part of the Remote MCP installation.
2. **Keep runtime dependencies isolated:** The compatible ARM64 Node.js runtime and pinned Desktop Commander package were installed within the board's own user-owned development-data filesystem, rather than overwriting Ubuntu's global runtime.
3. **Separate software installation from cloud pairing:** Installation alone does not provide account access. The human owner confirmed a short-lived verification code through the official Desktop Commander account workflow.
4. **Use the real target:** ChatGPT discovered AIS B as a distinct online device and tested tool calls directly against it, independent of the earlier Mac SSH setup transport.
5. **Read the outcomes back:** Capture endpoint presence, board identity class, return results and system invariants. Keep machine evidence distinct from visual/physical and service authority.
6. **Stop at the honest boundary:** Automatic system startup and restart/power-loss recovery were not installed or accepted during this milestone.

## 3. Distinct layers / 必须分开的四件事

**Device Reality:** AIS B is a real T736 board, not a cloud simulation. Its hardware, image and operating conditions are its own.

**Remote MCP connectivity:** Desktop Commander Remote transports approved tool calls from a connected ChatGPT account to the actual local device. This is the accepted layer here.

**Local MCP service and HSIMC Contracts:** The separate HSIMC local-MCP work/ledger and Azure canonical writer retain their own identities, protocols, authorities and evidence. The existence of this remote connection does not alter those contracts.

**Human Authority:** Account/device-code approval gives the owner access to a bounded remote tool surface; it does **not** grant unlimited physical execution, third-party access, e-Person authority, manufacturing approval or production safety certification.

Do not reuse AIS B's secrets, firmware, node credentials or operator database when preparing another T736. New devices need their own identity, authority, capability and acceptance.

## 4. A key usability detail

A first verification code expired before the human completed sign-in. Rather than reinstalling Node.js or Desktop Commander, the operator restarted the unregistered remote session and requested a **new** device code. After owner authorization, the AIS B endpoint appeared independently in the device list.

**General lesson:** Software package state, remote transport state, human account authorization and live device status are separate things. Troubleshoot each separately instead of repeating successful installation steps.

## 5. Hardware + evidence boundary

| Item | Status on 2026-10-15 |
| --- | --- |
| Remote package on AIS B | Desktop Commander Remote 0.3.0 — VERIFIED |
| Compatible runtime | Linux ARM64 Node.js 22 LTS — VERIFIED |
| Owner-authorized pairing | PASS |
| ChatGPT-to-registered-AIS-B direct tool calls | PASS |
| Filesystem/OS readback | PASS |
| Benign read-only terminal | PASS |
| HDMI + LightDM still operative during test | PASS |
| Linux service manager autostart of Remote Device | NOT INSTALLED |
| Reboot and power-loss remote reconnection | NOT TESTED |
| Cross-user/third-party authorization | NOT GRANTED |
| Industrial production/physical operation | NOT ACCEPTED |

A device can appear online during a tested window without being continuously online in the future. This public page is a historical evidence record, not a live status page.

## 6. Next acceptance / 下一次可独立完成的工作

For AIS B, a future work package should define user-controlled **start, stop, status and restart**, select a safe systemd policy and prove restart persistence with the same registered device identity. Power-loss recovery must be treated separately, with mounted external storage protected against unsafe shutdown. The existing HDMI and Chinese input successes should remain frozen.

After one physical T736 can be restarted and recovered independently, the same bounded pattern may be tested on a third T736—but with its **own** firmware, identity, authorization and evidence.

## 7. Public references

- [T736 Product 001 · Physical Reality](https://hsimc.tech/rd/t736/)
- [T736 two-board HDMI acceptance](https://hsimc.tech/rd/t736/hdmi/)
- [MCP-Ready Local Edge · Infrastructure](https://hsimc.tech/mcp-ready/)
- [Open Engineering Reality](https://hsimc.tech/rd/open-engineering-reality/)
- [Machine-readable public milestone evidence](https://hsimc.tech/rd/t736/remote-node/evidence.json)

Private accepted operator logs and source records are retained inside HSIMC's authorized engineering archive. Public material deliberately omits device IDs, verification codes, credentials, private file-system details and native boot images.

---

**HSIMC · The Human Reality Infrastructure Company**  
**Public URL:** https://hsimc.tech/rd/t736/remote-node/  
**GENAI NATIVE DOCUMENT · URL → QR → COPY → PRINT → NFC**  
Sharing this public engineering URL does not create or expand any access or execution rights.
