Skip to content

docs(research-checkpoints): add 2026-05 baseline ecosystem checkpoint#151

Open
MiaoDX wants to merge 2 commits into
mainfrom
docs/research-checkpoint-2026-05
Open

docs(research-checkpoints): add 2026-05 baseline ecosystem checkpoint#151
MiaoDX wants to merge 2 commits into
mainfrom
docs/research-checkpoint-2026-05

Conversation

@MiaoDX
Copy link
Copy Markdown
Owner

@MiaoDX MiaoDX commented May 22, 2026

What

First robowbc ecosystem-research checkpoint, per mithaq Mode A. Output is docs/research-checkpoints/2026-05.md (492 lines).

Anchored to the mithaq/vectors/robowbc.md card created 2026-05-21 (one day before this checkpoint). Covers all six research vectors and audits all eight hidden assumptions (H1–H8) against Q1–Q2 2026 evidence.

Why

The vectors card explicitly required a baseline checkpoint to anchor future comparisons: "When running the first checkpoint, verify two things: (1) all 6 vectors produce useful, distinct output; (2) the hidden assumptions actually get challenged." This PR delivers that baseline.

Key findings

  • GR00T-WBC upstream closed the gap with robowbc wrappers in Q1 2026 — GEAR-SONIC formal release 2026-02-19, SONIC training code 2026-04-10, N1.7 → SONIC end-to-end VLA workflow 2026-05-07. The gear_sonic wrapper is no longer ahead of upstream; it's catching up to a moving target with its own C++ deployment stack.
  • LeRobot v0.5.0 (2026-03-09) made Unitree G1 a first-class humanoid with native GR00T-WBC integration + third-party policy plugin mechanism — strengthens H8 but shortens the window for robowbc-py to ship as a competitive plugin (feat: LeRobot WBC backend integration (Do Later E) #41).
  • Sim substrate consolidated on MuJoCo-Warp via Newton + Isaac Lab 3.0 Beta during GTC 2026 (152x speedup vs MJX for locomotion); mjlab arrived as the lighter alternative.
  • ExecuTorch 1.0 GA (2025-10) is the most credible H2 substitute path; no humanoid adoption observed yet.
  • H5 and H8 strengthen; H6 needs revisit by 2026-08; H1/H2/H3/H4/H7 still betting-worthy.

Relationship to existing docs

This checkpoint operates at the ecosystem-snapshot level. It does not duplicate:

  • docs/ecosystem-strategy.md — strategy & positioning
  • docs/roadmap-2026-q2.md — technical priorities
  • docs/research/2026-05-merged-tech-report.md — deep DDS Rust binding + onboarding UX decisions

These are cross-referenced in §0.4 and Appendix A.7.

Process notes

  • Source tiering follows the vectors card: A-tier (NVlabs, HuggingFace, arXiv, ICLR) cited directly; B-tier (KraneShares, botinfo.ai) flagged inline; D-tier ignored.
  • Items needing primary-source verification next checkpoint are marked [未充分验证].
  • New entities surfaced during research (MotionBricks, Psi-Zero, GMT, mjlab, Newton, Booster T1, etc.) are listed in §8 Changelog so they can be added to the vectors card at the quarterly audit (2026-08-21).

Open questions for next checkpoint (full list in §7)

  • Q1: Does GR00T-WBC's gear_sonic_deploy C++ stack produce identical outputs to robowbc's gear_sonic wrapper?
  • Q4: Should robowbc-py ship as a LeRobot 3rd-party policy plugin or as a standalone package?
  • Q11: Confirm UnifoLM-VLA-0 primary source (currently B-tier only).

🤖 Generated with Claude Code
Co-Authored-By: Claude noreply@anthropic.com

Per mithaq Mode A — first robowbc ecosystem checkpoint, anchored to the
vectors card created 2026-05-21. Covers all six research vectors (WBC
policy upstream, inference runtime, hardware/SDK, middleware, sim
substrate, Python distribution) and audits all eight hidden
assumptions (H1–H8) against Q1–Q2 2026 evidence.

Key findings:
- GR00T-WBC upstream rapidly closed gap with robowbc wrappers
  (GEAR-SONIC formal release 2026-02-19; SONIC training code + HF
  checkpoint 2026-04-10; N1.7 → SONIC end-to-end VLA workflow 2026-05-07)
- LeRobot v0.5.0 (2026-03-09) added first humanoid (G1) and
  third-party policy plugins — validates H8, accelerates urgency on
  robowbc-py plugin shape
- Sim substrate consolidated on MuJoCo-Warp via Newton + Isaac Lab 3.0
  Beta during GTC 2026 (152x speedup vs MJX for locomotion); mjlab
  arrived as lighter alternative
- ExecuTorch 1.0 GA (2025-10) is most credible H2 substitute path,
  no humanoid adoption observed yet
- H5 and H8 strengthen; H6 needs revisit by 2026-08; H1/H2/H3/H4/H7
  still betting-worthy

Output location per mithaq SKILL.md: <repo>/docs/research-checkpoints/
(not in mithaq itself).

Cross-references existing docs/ecosystem-strategy.md (strategy),
docs/roadmap-2026-q2.md (priorities), and the deep technical
docs/research/2026-05-merged-tech-report.md (implementation choices).

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
@MiaoDX MiaoDX added docs documentation Improvements or additions to documentation labels May 22, 2026
…arch)

Replaces v1 (commit 680cd36) with deeper evidence after a full deep
research pass over the Mar–May 2026 window. v1 was a single-pass
sketch; v2 audits each of H1–H8 against multiple A-tier primaries.

Major judgment changes vs v1:

- H1 (one-contract WBC abstraction) — downgrades from "holds" to
  "holds only in joint-target codomain; falsified in latent /
  relative-EEF / Cartesian codomains". Concrete counter-examples:
  * GR00T N1.7 UNITREE_G1_SONIC outputs latent action tokens
  * GR00T N1.7 default cross-embodiment outputs relative EEF deltas
  * Psi-Zero (USC PSI, RSS 2026) Teleop outputs 14D wrist Cartesian
  Drives concrete trait redesign (predict_latent / predict_cartesian
  as first-class branches, not py_model black box).

- H8 (LeRobot as distribution channel) — verdict stays validated but
  urgency drops. Two months after the third-party policy plugin
  mechanism shipped (v0.5.0, 2026-03-09), the ecosystem has produced
  exactly ONE third-party plugin (lerobot_policy_ditflow). Channel is
  public but largely unused. Recommend dual-path distribution
  (maturin standalone + lerobot_policy_robowbc) rather than
  single-path bet.

- Strategic threat reordering — v1 framed LeRobot as the direct
  threat. v2 reorders to:
  gear_sonic_deploy cross-family reuse > LeRobot framework absorption
  > NVIDIA building robowbc-equivalent. gear_sonic_deploy already
  serves two policy families (SONIC + Decoupled WBC) and is one
  ONNX-config away from absorbing BFM-Zero or UnifoLM-VLA.

- Hidden assumption audit, full table — every H1–H8 now has primary
  evidence delta and concrete action, not just "still betting".

New A-tier evidence v1 lacked:
- UnifoLM-VLA-0 primary repo + license (CC BY-NC-SA 4.0)
- Newton 1.0 LF release + 252×/475× MuJoCo-Warp benchmarks (v1's
  152× number is corrected — v1 was from a single search result, v2
  cites NVIDIA Technical Blog primary)
- Booster T1 SDK + booster_gym arXiv as concrete second-platform
  candidate (v1 had this as "could be useful")
- AgiBot G2 wheeled architecture + AimRT C++20 middleware
- Psi-Zero codomain split (Teleop = 14D Cartesian, MP = joint-space)
- Pi0-FAST RTC latency benchmark (76ms baseline / 97ms RTC)
- Unitree IPO A-tier confirmation via CNBC

New vectors card proposals for 2026-08-21 quarterly audit:
- V7: Real-time + safety certification (PREEMPT_RT, ISO 25785-1)
- V8: License/IP + dataset schema tracking

Concrete actions queued: 12 items across immediate (5–6 weeks),
6–12 weeks, and quarterly horizons. See §6.

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
@MiaoDX
Copy link
Copy Markdown
Owner Author

MiaoDX commented May 22, 2026

v2 update pushed (commit bf8bc39)

Deeper research pass over Mar–May 2026 with full A-tier verification. Same file replaced with 520 lines of v2 content. Reviewer can see the v1 → v2 diff in the second commit if interested in the evolution; or just review the final state.

Key judgment changes vs v1 (review-critical)

v1 v2
H1 — one-contract WBC abstraction holds holds only in joint-target codomain. Three counter-examples in Mar–May 2026: GR00T N1.7 UNITREE_G1_SONIC (latent tokens), N1.7 default (relative EEF), Psi-Zero Teleop (14D Cartesian)
H8 — LeRobot distribution channel strengthens, ship urgently holds, urgency dropped. 2 months post-v0.5.0, only 1 third-party plugin (lerobot_policy_ditflow) exists. Recommend dual-path (maturin + plugin), not single-path
Strategic threat #1 LeRobot gear_sonic_deploy cross-family reuse > LeRobot absorption > NVIDIA building runtime
MuJoCo-Warp speedup 152× (B-tier) 252× locomotion / 475× manipulation on RTX PRO 6000 Blackwell (A-tier, NVIDIA Technical Blog)

What v2 added that v1 missed

  • §3.1.7 interface table — 12 humanoid WBC families × action shape + codomain side-by-side. This is the H1 falsification evidence in one screen.
  • §4 blind spots — proposed new sub-vectors V7 (RT/safety, PREEMPT_RT + ISO 25785-1) and V8 (license/IP/dataset schema). Defer add to mithaq vectors card until 2026-08-21 quarterly audit.
  • §5 strategic threats — honest section on what would falsify robowbc's value proposition, with 5 ranked scenarios.
  • §6 recommendations — 12 concrete actions split across immediate / 6-12 weeks / quarterly. Top 3 immediate: SONIC wrapper alignment to 2026-02-19 release + ZMQ v4 header, WbcPolicy trait extension for latent/Cartesian codomain, license-aware notices.
  • A-tier source upgrades — UnifoLM-VLA-0 primary repo, Newton 1.0 LF press, Booster T1 SDK + booster_gym arXiv, Psi-Zero codomain split, Pi0-FAST RTC latency, Unitree IPO via CNBC.

Still unresolved (carry to next checkpoint)

  • ISO 25785-1 Working Draft content (paywalled)
  • MuJoCo-Warp 252×/475× numbers are NVIDIA self-reported; no independent third-party reproduction yet

Ready for review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants