# HSIMC · Two Physical T736 Seed Nodes / 双实体种子节点工程手册

**C0-003 · 2026-10-16 · Public Engineering Continuity**  
**Artifact:** HRI-HSIMC-T736-TWO-SEED-NODES-GLOBAL-ENGINEERING-C0-003-20261016  
**Public URL:** https://hsimc.tech/rd/t736/seed-nodes/  
**Parent:** https://hsimc.tech/rd/t736/  

*Repeat the engineering method — not another board's firmware, mobile identity, device token or production Authority.*

## 1. Why two independent seed nodes matter / 为什么不是简单复制第二块板

A single board can demonstrate a lucky working configuration. AIS B and USA2 independently verified something more transferable: an engineering sequence that separates physical source, connectivity, boot and display, native compute, remote owner pairing, recoverability, human language input, and the Work/Authority contract. The two boards have their own board identities, source images, SIM and network contexts, account authorization, and operational receipts.

从一个能运行的 T736，到两块真实板卡各自成功走通 Ubuntu、HDMI、GPT 远程调用与恢复，重要资产不是某个安装文件，而是**Prompt → 现场判断 → 最小修改 → 人工实测 → 机器回读 → 证据 → 下一轮接续**。未来全球工程师可以跳过已证明没有必要重复的探索，但新设备仍须逐项验收。

These are historical tests on 15–16 October 2026, **not claims of both devices being continuously online today**.

## 2. Evidence hierarchy / 证据与授权边界

| Evidence | Accepted scope | Not automatically accepted |
| --- | --- | --- |
| Hostname, board boot ID, USB/DRM and route readbacks | One observed physical machine and boot | Another board or future boot |
| Source archive SHA-256 and post-install readback | Correct release bytes on named target | Globally approved firmware or installer |
| systemd active and owner credential presence | Local managed service | Cloud provider Online or Work authority |
| Direct owner-authorized Desktop Commander tools | Specific device Ping, file, directory and benign command | Unrestricted physical work execution |
| Human sees pixels and types Chinese | A user-confirmed desktop or browser input test | Every UI/application/reboot |
| e-Person Work and human supervision | Separate future Governance/consumption contract | Not created by SIM or Remote MCP pairing |

## 3. Seed A / AIS B — first independently addressable physical node

Ubuntu 24.04.3 ARM64, T736; human-tested graphical HDMI; Desktop Commander Remote 0.3.0. The owner registered AIS B as its own Remote Device. ChatGPT selected and directly called the actual board using Ping, file/directory read and benign process tools. Mac SSH was used for provisioning and independent recovery, **not to impersonate direct Remote MCP acceptance**.

**HDMI lesson:** T736 vendor Linux BSP originally routed the native display toward DSI, requiring node-owned source preservation and an offline narrowly scoped FDT/HDMI candidate. DRM/EDID becoming connected was not the same as Xorg/LightDM succeeding. A vendor DRM BITMASK compatibility issue was worked around **only inside the Xorg subprocess**; global libdrm was not replaced. Human FHD and AIS B QHD acceptance were separate from machine-readable modes. Source boot images and original SHA are private, not universal downloadable firmware.

**Remote lesson:** A device-code expiry required a fresh owner verification step, not reinstalling the ARM64 Node.js runtime. The later user-scoped systemd deployment retained the registered identity, and an independent Mac SSH session proved controlled stop → start → restart. Provider Online/Ping was independently read back rather than inferred from a running PID.

**Mac recovery lesson:** SSH timed out while AIS B was alive because the Mac's Ethernet auxiliary IPv4 disappeared. Restoring the correct interface/route revived SSH without resetting the T736. A guarded Mac LaunchDaemon later re-applied the auxiliary address and passed periodic checks; a real future Mac reboot test remained pending.

**Storage/USB lesson:** A four-port Genesys Logic USB hub previously enumerated a WD 4TB and keyboard/mouse successfully. Another boot's last available log occurred around WD enumeration, while bypassing the hub coincided with AIS B recovering. The causal USB fault is *unknown*; electrical overcurrent was not proven. FAT/exFAT previously logged improper unmount warnings. An RW mount is not a filesystem health certificate.

## 4. Seed B / USA2 — a separate SIM-connected, Chinese-capable Reality

Ubuntu 24.04.3 ARM64; independently verified HDMI and XFCE; Quectel LTE modem; SIM and PPP network; independently paired Desktop Commander Remote 0.3.0; user systemd; real Fcitx5 and Firefox Pinyin acceptance.

**Network presence:** The old Mac SSH alias jumped through AIS B and was invalid after hardware was moved. A direct Mac↔USA2 Ethernet route found the actual second board. Before the user inserted a SIM, ModemManager said sim-missing and the LTE gateway had no ppp0. After owner SIM insertion and a new boot, modem connected/roaming, PPP and policy-routing table regained a default path. The first unsynchronized 2026-10-14 clock recovered via NTP. A guarded manual correction script refused to change the clock because Boot ID and routing had changed. This is a correct stop condition.

**Offline ARM64 delivery:** Official Node.js 22.23.3 Linux ARM64 source archive was SHA-verified on the Mac, transferred over wired SSH and checked again on USA2's own data partition. A pinned Desktop Commander 0.3.0 package plus Linux ARM64 dependencies was prepared on the Mac without running package lifecycle scripts, then transferred and verified. This avoided relying on a roaming SIM to pull a large dependency tree. The system root partition and WD 4TB were not used as a shared clone of AIS B.

**The IPv4 trap:** On the active PPP network, curl with IPv4 successfully returned HTTP 200 from the Desktop Commander endpoint, while default Node.js fetch timed out (IPv4 timeout and IPv6 network unreachable). A process-local Node.js compatibility setting disabled network-family autoselection and preferred IPv4; a new Node fetch returned HTTP 200, Remote MCP connected, and the user completed a new independent device-code authorization. This was a specific observed stack/transport issue, *not* a global Linux DNS rule.

**System service vs real tool reachability:** USA2 was paired with its own unique Remote Device identity. Mac SSH stopped the previous manual process, started the new user systemd service and observed a short provider Offline period followed by the *same* device reappearing Online with a real ChatGPT Ping. Controlled stop/start/restart, PID changes and direct provider readback passed. User-service autostart and linger were then enabled; the final unit was corrected to run after basic.target, not after the default.target that wants it. A post-install physical power-cut/reboot recovery test remained NOT_RUN.

**Fcitx5 offline installation:** Chinese Noto CJK font and locale were already available; the input method framework was not. APT simulation for Fcitx5 and Chinese/Pinyin GTK frontends planned 38 added Ubuntu ARM64 packages, 0 upgrades and 0 removals. The required ~47.5 MB compressed packages were downloaded on Mac and matched by SHA-256 against Ubuntu APT package indexes, then transferred to USA2 and reverified 38/38 before installation. The user actually typed **你好** in a standalone XFCE Chinese test field.

**Firefox is a separate gate:** Firefox's parent process was started before Fcitx5 and lacked GTK_IM_MODULE, QT_IM_MODULE and XMODIFIERS. The user-owned browser launcher was backed up. Only its process environment was augmented, retaining the existing Firefox binary and profile. The user saved current web work, quit Firefox normally and reopened a new Firefox process; the new parent inherited all three input-method exports, and the user **actually typed 你好 in Firefox**. A webpage refresh could never replace these inherited process variables. This is stronger than “Fcitx5 installed”.

**Optional Chrome/PDF:** Desktop Commander separately attempted a startup Chrome download for PDF generation, staying at 0% under the observed cellular environment. It is not proof the Remote MCP pairing failed; PDF/Chrome remains a separate unaccepted optional capability, to avoid wasting carrier data.

## 5. Eight gates to the next board / 全球工程师的最短复制流程

| Gate | Verify before advancing | Explicit stop condition |
| --- | --- | --- |
| G0 Physical identity | New board revision, own firmware/boot source, boot ID, local authority, recovery path | Identity mismatch, copied secrets or no rollback |
| G1 Power/storage | Disk mounts, safe WD handling, logs, backup plan | Mounted-disk fsck or uncontrolled power-cut |
| G2 Cellular/LAN/time | SIM/modem, PPP, routing, DNS, HTTPS, NTP | Stale Boot ID, missing route, unsynced clock |
| G3 HDMI/GUI/browser | DRM/EDID, Xorg, LightDM, human screen image, working app | Treat machine EDID as physical display PASS |
| G4 Native runtime | Verified official archive, ARM64 native dependencies, node-local data mount | Generic OS upgrade, wrong architecture or shared root image |
| G5 Device pairing | User-approved new device ID, actual provider connection, direct Ping/read | Copying another node's credentials |
| G6 Operability | Independent SSH, PID + provider readback, stop/start/restart, scoped autostart | PID active but provider Offline; untested reboot claimed |
| G7 Human and handoff | Real Chinese keyboard/browser typing; raw Prompt + evidence + correction + next stop | IME package installed only, no human proof |

The accompanying checklist.json gives G0–G7 as portable machine-readable review objects, **not an unbounded executable installer**.

## 6. Useful read-only checks / 只读探测，不改动现场

Only after identifying the board and obtaining normal operator permission:

    hostname
    uname -m
    cat /etc/os-release
    cat /proc/sys/kernel/random/boot_id
    ip -br address
    ip -4 route
    timedatectl status
    lsusb -t
    lsblk -o NAME,SIZE,FSTYPE,MOUNTPOINTS
    systemctl is-active lightdm
    systemctl --user list-units --type=service

The read-only output is a *preflight* — not proof that a flash, restart, pairing or production action is authorized.

### Process-level IPv4 experiment — USA2 only

    NODE_OPTIONS="--no-network-family-autoselection --dns-result-order=ipv4first"

The above worked for the observed Node 22 + PPP transport behavior on USA2. Do not apply globally or automatically on other carriers. First compare DNS A/AAAA, curl IPv4, Node fetch error and current routing.

### Firefox Fcitx5 environment — USA2 only

    GTK_IM_MODULE=fcitx
    QT_IM_MODULE=fcitx
    XMODIFIERS=@im=fcitx

Changes to launcher process environment do not change already-running Firefox. Save user input, quit normally, then relaunch through the verified wrapper. On USA2 the browser parent then showed these exact variables and human-entered Chinese text passed.

### Service readback — not just a PID

During future *operator-authorized* setup, keep an independent SSH path, inspect the node-specific user service status and provider account state, and verify that the **same device identity** resumes after service stop/start/restart. Do not issue destructive controls solely through the remote connection being stopped.

## 7. Confirmed but unaccepted / 不扩大验收的真实停点

- **OS cold reboot:** USA2 user systemd autostart and linger are installed and service-level restart passed. A *new physical cold-reboot/forced power-cut* followed by automatic Remote MCP and GUI/CJK return has NOT RUN after this installation. Do not call the new unattended runtime certified.
- **WD:** Both FAT and exFAT volumes previously reported unclean unmount. The WD 4TB mounted and was accessible on both observed arrangements, but full filesystem integrity requires backup and safe unmounted maintenance.
- **USB HUB:** The Genesys Logic 4-port HUB was identified by USB descriptors; past enumeration succeeded and one boot ended around WD discovery, but hub current limitation, power fault or USB incompatibility has not been proven.
- **Chrome/PDF renderer:** The optional DC startup Chrome download showing 0% is not an accepted PDF rendering capability.
- **Network coverage:** One operator or SIM testing case is not evidence of global coverage, licensed service, unlimited roaming or adequate local data protection.
- **Model generality:** T736 NPU fixed-model/Golden test is not evidence that arbitrary models, drivers or physical actions are accepted.
- **Work and law:** e-Person identity, Human Supervisor, Consent, official service language, Work Authority, payment, consumption evidence and cross-border regulatory requirements are outside Remote MCP device pairing.

## 8. Engineer's new-node Work envelope / 下一位工程师的交接单

Record before first privileged operation:

1. Node-specific Reality ID, actual hardware revision and originating firmware; source/backup digest.
2. Actual network, physical SIM / modem, operator region and data path, timezone/NTP.
3. Available I/O, connected USB/HDD, mounts and data-safety constraints.
4. Intended capability, model/software version, supported ABI and user language.
5. Independent operator/recovery channel and Human Supervisor authority.
6. Candidate change, preflight guard, SHA and explicit stop/rollback criteria.
7. What *machine* readback proves and what *human* physical action proves.
8. Whether provider reachability, canonical HSIMC Work and physical execute authorization are distinct and actually accepted.
9. Receipt hashes, complete Prompt/decision/evidence trail and an exact next continuation point.
10. Costs, maintenance, carrier tariffs, consumption and long-term support ownership.

The right asset to copy is **a contract + a checked method + dated evidence**, not a boot image or credential.

## 9. Public source lineage / 相关既有研究

- [HSIMC T736 Product 001](https://hsimc.tech/rd/t736/)
- [AIS B owner-approved direct ChatGPT Remote MCP C0-001](https://hsimc.tech/rd/t736/remote-node/)
- [USA2 → AIS B: network and physical continuation C0-002](https://hsimc.tech/rd/t736/usa-to-ais/)
- [Two-board HDMI and scoped Xorg acceptance](https://hsimc.tech/rd/t736/hdmi/)
- [T736 NPU / Golden / restart evidence](https://hsimc.tech/rd/t736/ecosystem/evidence/)
- [HSIMC Engineering Continuity](https://hsimc.tech/rd/engineering-continuity/)
- [T736 capability collaboration](https://hsimc.tech/rd/t736/continue/)
- [e-Person for Me — governed Work concept](https://hsimc.tech/e-person-for-me/)

Private chronological evidence and original source material remain in the HSIMC Mac/operator archive. They are *not* part of this public package. The public files omit private IPs, hardware MACs, Remote device UUIDs, enrollment codes, SSH secrets, SIM identifiers, boot images, 4TB files and local Work ledgers.

---

**HSIMC · The Human Reality Infrastructure Company**  
*Instant. Globally. Through to Reality.*  
**GENAI NATIVE DOCUMENT · URL → QR → COPY → PRINT → NFC**  
https://hsimc.tech/rd/t736/seed-nodes/  
Sharing this public engineering URL grants no new account access, execution authority or safety certification.
