astra: research session 2026-05-12 — 4 sources archived

Pentagon-Agent: Astra <HEADLESS>
This commit is contained in:
Teleo Agents 2026-05-12 06:10:33 +00:00
parent ba102e8d73
commit 62d30378b1
2 changed files with 157 additions and 0 deletions

View file

@ -0,0 +1,81 @@
---
type: source
title: "Figure 03 + Helix 02: Kitchen Demo and Manipulation Breakthrough in Unstructured Environments (January-February 2026)"
author: "Figure AI (@FigureAI)"
url: https://www.figure.ai/news/helix-02
date: 2026-01-28
domain: robotics
secondary_domains: [manufacturing]
format: thread
status: unprocessed
priority: high
tags: [humanoid-robots, Figure-03, Helix-02, manipulation, unstructured-environments, kitchen-demo, tactile-sensing, full-body-autonomy]
intake_tier: research-task
---
## Content
**Helix 02 overview (released January 28, 2026):**
Figure AI unveiled Helix 02, a full-body visuomotor neural network that replaces all prior C++ control architecture with a unified AI system. Architecture breakdown:
- S0: 10M-parameter neural prior at 1 kHz (low-level motor control)
- S1: Unified visuomotor at 200 Hz (whole-body coordination)
- S2: Semantic reasoning layer (task understanding)
- ALL C++ code from Helix 01 BMW deployment eliminated — the architectural ceiling identified at BMW is resolved
**Kitchen demo (4-minute autonomous task, 61 loco-manipulation actions):**
- End-to-end autonomous execution, no human resets, no hard-coded sequences
- Walk to dishwasher → unload dishes → navigate across kitchen → stack in cabinets → reload dishwasher → start cycle
- Tests: walking, grasping, object recognition, spatial navigation, sequenced multi-step planning, all integrated
**Dexterous manipulation capabilities demonstrated:**
- Tactile fingertip sensors: 3-gram force detection ("sensitive enough to feel a paperclip")
- Pill extraction from medicine organizer (uses palm-level visual feedback)
- 5mL syringe actuation (force-controlled to exact volume)
- Cluttered box singulation (objects overlapping, shifting during interaction, self-occlusion)
- Unscrewing bottle cap (bimanual coordination with tactile-regulated grip force)
**Hardware improvements (Figure 03 vs. Figure 02):**
- Camera: 2x frame rate, 1/4 latency, 60% wider field of view per camera
- More compact form factor
- Embedded tactile sensing in each fingertip and palm cameras (new hardware)
**Figure 03 and BotQ factory:**
- BotQ facility (Sunnyvale, California): dedicated high-volume humanoid manufacturing
- Production ramp: 1/day → 1/hour (24x improvement in under 120 days, announced ~May 2026)
- Units delivered: 350+ Figure 03 robots to partners/pilots by May 2026
- Current pace: ~55 robots/week
- First-pass yield: 80% at BotQ
- Infrastructure: 150 networked workstations with custom MES
- Target capacity: 12,000 units/year initially; 100,000 total over 4 years
- Consumer pricing target: $20,000 (aggressive; requires significant manufacturing scale)
- Home deployment timeline: select partner testing in 2026; broader consumer availability late 2026 to 2027
**From Time Magazine (Figure 03 profile):** "Figure 03 Is The Robot in Your Kitchen" — framing the consumer market as the target
**From GoPenAI/Medium (May 2026 analysis):** "Figure Just Solved the Hardest Problem in Robotics" — referring to unstructured manipulation
## Agent Notes
**Why this matters:** This is the leading indicator I flagged in the May 11 musing for the manipulation constraint crossing. The May 11 session identified three binding constraints on humanoid robot deployment: hardware reliability, software architecture generalization, and manipulation in unstructured environments. Helix 02 / Figure 03 addresses all three: the C++ architectural ceiling is resolved (architecture), the kitchen demo demonstrates genuine unstructured manipulation (capability), and BotQ's 80% first-pass yield suggests manufacturing maturity (reliability). This is the most significant robotics development of May 2026.
**What surprised me:** The specific manipulation tasks — pill extraction, syringe force control, cluttered box singulation — are not structured factory tasks. These are healthcare and household ADL tasks. Figure is targeting the home market directly, not the factory market. This is a different commercial thesis than Figure 02's BMW deployment. It also means the "kitchen is still more structured than full unstructured" objection is weakening — healthcare manipulation in particular is high-variability.
**What I expected but didn't find:** Expected the consumer deployment timeline to be 2027+. The BotQ 24x production ramp and 350+ units delivered by May 2026 suggests the scale-up is proceeding faster than I anticipated. The $20K price target is still aspirational — current units are being deployed to partners, not sold at consumer prices. The cost threshold crossing is still 2027+ at earliest.
**KB connections:**
- Belief 11 (robotics is binding constraint): The manipulation constraint — the hardest of the three — is being meaningfully breached. The "unsolved" characterization from prior sessions needs updating.
- [[three conditions gate AI takeover risk autonomy robotics and production chain control and current AI satisfies none of them]] — the robotics condition is now further along toward crossing than the prior framing
- [[knowledge embodiment lag means technology is available decades before organizations learn to use it optimally]] — Figure's C++ → full-body neural network transition is knowledge embodiment lag in reverse: the knowledge IS being embodied, rapidly
**Extraction hints:**
- CLAIM CANDIDATE 1: "Figure AI's Helix 02 demonstrates autonomous kitchen-task execution across 61 loco-manipulation actions including pill extraction, force-controlled syringe operation, and cluttered-object singulation — the first credible evidence that unstructured domestic manipulation is achievable by humanoid robots"
- CLAIM CANDIDATE 2: "Figure 03's BotQ manufacturing facility achieved 24x production throughput improvement (1/day to 1/hour) with 80% first-pass yield in under 120 days, demonstrating that humanoid robot manufacturing is entering serial production at commercially relevant volumes"
- SCOPE NOTE: Capability breakthrough ≠ cost threshold crossing. $20K consumer price target requires further manufacturing scale. The manipulation capability is demonstrated; the economics at mass-market scale are not yet closed.
**Context:** Figure AI is a California-based humanoid robotics company founded by Brett Adcock. Valuation as of early 2026: $39B. BMW deployment (Figure 02, 30,000 vehicles, 1,250 hours) was Gate 1b commercial validation (see prior archive). Helix 02 is the direct successor, released after BMW deployment lessons.
## Curator Notes (structured handoff for extractor)
PRIMARY CONNECTION: Belief 11 (robotics is binding constraint) — specifically the manipulation-in-unstructured-environments constraint identified as the hardest gate
WHY ARCHIVED: First credible public demonstration of domestic unstructured manipulation capability by a humanoid robot. The kitchen demo (61 actions, 4 minutes, autonomous, no resets) is materially more complex than prior humanoid demonstrations. Combined with BotQ production ramp, this is the leading indicator for the manipulation constraint crossing.
EXTRACTION HINT: Two claims, not one: (1) capability demonstration (what Helix 02 can do), (2) manufacturing ramp (what BotQ is achieving). Keep separate — they address different constraints.

View file

@ -0,0 +1,76 @@
---
type: source
title: "Starship IFT-12 Pre-Launch Update: Booster 19 Second 33-Engine Static Fire (May 9), NET Confirmed May 15"
author: "Tesla Oracle / NASASpaceFlight (@NASASpaceflight) / SpaceLaunchSchedule"
url: https://www.teslaoracle.com/2026/05/09/flight-12-starship-booster-19-performs-a-full-duration-33-engine-static-fire-test-ahead-of-launch/
date: 2026-05-09
domain: space-development
secondary_domains: []
format: thread
status: unprocessed
priority: high
tags: [Starship, IFT-12, V3, Booster-19, Raptor-3, static-fire, OLP-2, NET-May15, launch-status]
intake_tier: research-task
---
## Content
**As of May 12, 2026 (today):**
IFT-12 (Starship Flight 12) has NOT yet launched. The first window (May 12 at 22:30 UTC) was not used. The NET (No Earlier Than) date is confirmed as May 15, 2026 at 22:30 UTC.
**New development: Second static fire of Booster 19 (May 9, 2026):**
- Booster 19 performed a second full-duration 33-engine static fire on May 9, 2026
- First static fire was April 15-16, 2026 (also 33 engines, all Raptor 3)
- This is unusual: prior V2 Super Heavies typically performed one static fire before flight
- No official explanation from SpaceX for the second test
- Interpretation: Either (A) the April static fire surfaced marginal data requiring verification, or (B) this is SpaceX's standard V3 diligence protocol for the all-Raptor-3 configuration debut
**Current launch status (May 12, 2026):**
- FAA clearance: Confirmed (May 8 investigation closure)
- Vehicle: Booster 19 + Ship 39, both V3 / Block 3 configuration
- Site: OLP-2 (Orbital Launch Pad 2) — inaugural launch from this pad
- Trajectory: Revised southerly Caribbean corridor (debris into open ocean rather than near populated areas)
- No booster catch attempt: Booster 19 to splashdown in Gulf of Mexico; Ship 39 to Indian Ocean powered splashdown
- FCC license: Valid through October 2026, covers Flights 12 and 13
**Launch window schedule (per Local Notice to Mariners):**
- NET May 15 at 22:30 UTC (5:30 PM CT)
- Daily ~2-hour windows available May 15-18
**What IFT-12 will tell us:**
1. Raptor 3 in-flight performance (first ever — all prior flights used Raptor 2)
2. V3 upper stage reentry survival (no V2 Ship ever survived reentry intact)
3. OLP-2 inaugural performance
4. Vehicle mass fraction and Isp measurements (derivable from telemetry)
5. SpaceX booster reuse declaration post-flight (when will they attempt first V3 booster catch?)
**IPO context:**
- SpaceX IPO roadshow targeting June 2026 (Nasdaq)
- IFT-12 success/failure is the most visible near-term data point for the IPO narrative
- A successful reentry survival demonstration would directly validate V3 full-reuse economics claims
## Agent Notes
**Why this matters:** The second static fire on May 9 is new information not in prior IFT-12 archives (which covered through May 8). A second 33-engine static fire 3.5 weeks before NET May 15 suggests additional pre-flight verification was required. The most plausible reason: V3's all-Raptor-3 configuration (33 new-gen engines) has never operated simultaneously in flight, and the April static fire may have revealed engine interactions or thermal patterns requiring confirmation. This adds uncertainty — if the second static fire itself revealed issues, a further delay is possible.
**What surprised me:** The shift from May 12 to May 15 NET is not explained in any source. The second static fire (May 9) could be the proximate cause: performing the static fire 3 days before the first window means SpaceX needed several days to assess results before declaring launch readiness. The NET shift from May 12 to May 15 maps closely to this timeline (static fire results → 3-4 day evaluation → launch readiness declaration).
**What I expected but didn't find:** A specific technical explanation for either the NET shift or the second static fire. SpaceX does not publicly disclose pre-flight anomalies or hold-points in real time.
**KB connections:**
- [[Starship achieving routine operations at sub-100 dollars per kg is the single largest enabling condition for the entire space industrial economy]] — IFT-12 is the primary 2026 test of this claim; second static fire adds pre-launch uncertainty
- [[reusability without rapid turnaround and minimal refurbishment does not reduce launch costs]] — V3's pre-launch process (2 static fires, extensive checks) suggests turnaround time for early V3 flights will not yet be "airline-like"
- [[the space launch cost trajectory is a phase transition not a gradual decline analogous to sail-to-steam in maritime transport]] — V3 maiden flight is the next data point on this trajectory
**Extraction hints:**
- STATUS UPDATE (not standalone claim): Update existing IFT-12 archives with the second static fire data point and NET May 15 confirmation. Do NOT create a standalone claim — this is procedural data.
- POTENTIAL FUTURE CLAIM (post-flight): If post-flight analysis reveals the reason for the second static fire (anomaly vs. protocol), that would be claim-worthy. Currently unknown.
- TURNAROUND NOTE: Two static fires before V3 maiden flight vs. one before V2 flights — this may indicate V3's increased complexity requires more extensive pre-flight validation. Flag this when assessing the "airline-like turnaround" claim timeline.
**Context:** NSF (NASASpaceFlight.com) posted the May 12 first-window scrub confirmation. Tesla Oracle covered the May 9 static fire with technical detail. SpaceLaunchSchedule and RocketLaunch.Live both show May 15 as current NET. Polymarket odds were at 91% as of May 7 and are likely higher given FAA clearance and second static fire completion.
## Curator Notes (structured handoff for extractor)
PRIMARY CONNECTION: [[Starship achieving routine operations at sub-100 dollars per kg is the single largest enabling condition for the entire space industrial economy]]
WHY ARCHIVED: The second static fire before flight is a new data point not in prior archives. Combined with the May 12 → May 15 NET shift, this archive completes the pre-launch status picture. Post-flight: this archive will serve as the pre-flight baseline for comparison with actual results.
EXTRACTION HINT: This is a procedural status archive — extract only after the flight, when post-flight data can be compared to these pre-flight conditions.