Config
Freeze unit, firmware, compute, network, payload and code. Hash raw and sanitized evidence.
PROFILEUNITREE G1 / GO2 / GO2-W
Fleet uptime is an evidence problem
A robot that reconnects once, returns success once or finishes one patrol is not a reliable fleet unit. Release decisions need an exact hardware/firmware profile, immutable timing evidence, confirmed command ownership, fault injection and a reproducible recovery path.
01 / INPUT
Freeze the unit before debugging
The model name is not a sufficient reproduction key. Every result remains scoped to the recorded unit and release.
| Layer | Required fields | Unsafe shortcut |
|---|---|---|
| Robot | Exact SKU/edition, hardware revision, serial-safe identifier, firmware, battery/dock and motion mode. | “Go2 compatible” or “same SDK” without a per-model profile. |
| Compute | Onboard/external computer, OS, architecture, power, network interface, container and clock source. | Using a developer laptop result as a fleet unit result. |
| Software | SDK/ROS/client commit, dependency lock, parameters, API version and deployment artifact hash. | Testing a moving branch or undocumented binary. |
| Transport | DDS/WebRTC/API route, identity, renewal/reconnect path, latency, loss and server/cloud dependency. | Equating local request success with robot acceptance. |
| Payload | Sensor/arm wiring, publisher, frame, source stamp, rate, power and failure behavior. | Restamping stale data until synchronization errors disappear. |
02 / TRACE
One bounded first engagement
- 01Provide one redacted failure trace and the exact robot, firmware, network and software configuration.
- 02Separate observed facts, missing evidence and hypotheses; define the smallest deterministic reproduction.
- 03Return an evidence matrix covering connection, state freshness, command ownership, STOP, sensor time and recovery.
- 04Prioritize one narrow change or additional trace instead of replacing the whole stack.
- 05Only after no-motion evidence passes, agree a bounded hardware cell with explicit operator and safety authority.
03 / GATES
Five release gates
No motion
Prove connection, consecutive fresh state, clock provenance, topic silence/decoder failure and clean lifecycle.
READ ONLYCommand / stop
Use one owner, generation-scoped freshness and an independent watchdog. Keep failed or unknown STOP pending.
STOP PENDINGFault injection
Test process death, network loss, server loss, stale callbacks, delayed packets, mode change and power recovery.
FAULTSRollout
Promote only the exact passing artifact and configuration. Canary, observe, rollback and retain the evidence bundle.
RELEASE04 / CONTRACT
What gets measured
| Contract | Evidence | Failure state |
|---|---|---|
| Connection | Handshake branch, identity, renewal, reconnect generation, source/receive time and dependency status. | Connected UI with stale or unauthenticated robot state. |
| Command | Producer ID, generation, issue/receive/accept time, bounds, mode and state-correlated response. | Late command accepted after cancel, reconnect or process restart. |
| STOP | Cancel result, zero/stop result, fresh state, physical response and confirmed-through generation. | Request sent but physical stop or command exclusion unconfirmed. |
| Sensor time | Immutable source stamp, receive stamp, clock offset/uncertainty, frame and stale/pair rejection. | Host `now()` used to manufacture alignment. |
| Recovery | Safe initial state, operator authority, replayed fault, bounded retry, rollback and post-recovery health. | Automatic restart that restores motion without a new authorization. |
05 / DATA
Work from redacted traces
- 01No customer faces, site maps, credentials, robot account secrets or private endpoints are required for the first review.
- 02Retain raw evidence internally; share a sanitized derivative with hashes and a removal record.
- 03Replace identifiers consistently so reconnect, command and sensor generations remain traceable.
- 04Do not use a different model, firmware or payload result to claim fleet-wide support.
06 / BOUNDARY
Capability boundary
Real-hardware experience is on Unitree G1 and Go2-W navigation/field integration. Go2 Air, Pro or EDU fleet claims require the exact target hardware and agreed authority. Source review, replay design and sanitized trace analysis can start without robot motion; no firmware, account, network or site change is implied.
| Can start remotely | Requires target hardware | Not claimed |
|---|---|---|
| Source/architecture review, evidence schema, log contract, replay test, release gates and failure-hypothesis ranking. | Command acceptance, physical stop time, wheel/leg behavior, payload power/thermal behavior, reconnect and site recovery. | Blanket Unitree compatibility, official affiliation, 99% uptime, autonomous fleet deployment or access to private Unitree interfaces. |
Send one failure class
Include the exact model/edition, firmware, compute, network path, SDK/ROS commit, expected safe state and a redacted trace. The first response will define what is proven, missing and smallest to reproduce.