Evidence before expansion
A stage advances through passing tests, not visual spectacle or calendar pressure.
SYSTEM TRACEPreparing this route
Preserving identity and page context while the next view is assembled.
Preserving identity and page context while the next view is assembled.
Evidence-gated roadmap
Governed memory is now an implemented synthetic workstream, not only the next idea. The current order is governed-conversation qualification in G8, consolidated synthetic acceptance in G9, then the remaining deployment/recovery and participant conditions. The preserved local/cloud demo and its internet, voice and vision gates stay separate.
Current phase: synthetic memory · G8/G9 open · head presence laterMS-00 established the controlled Thor programme, source authority, 102 effective requirements, 16 milestones, 30 tracked risks, and explicit evidence labels.
The 128 GB-class Thor kit is operational. MS-01 and MS-02 carry an explicit pristine-state deviation and an open recovery gate; MS-03 passed for standalone XVF/Pebble AEC and C920 fixtures.
The exact Qwen3-Omni NVFP4 reference received a conditional pass and was then retired from active conversation. MS-06 passed its declared Core/provider text-governance scope. ConversationLedger now owns the spoken lifecycle, while a derived open-session memory index remains separate from Qwen's bounded working set.
The September 11 local/cloud recovery freeze is preserved on engineering main. Both supplied Spanish sessions exercised conversation, explicit live/history vision, research and clean shutdown. Follow-up reliability, freshness and latency gates remain open.
The separate memory branch implements durable PostgreSQL records, current rights, reviewed English/Spanish input and restart workflows. The latest operator-reported backend result is 903/903 required methods, zero skips. G8/G9, deployment security, participants and physical embodiment remain separately gated.
22 September / J-016
Seeed Studio components and our Bambu Lab A1 are now in the workshop. The current target is to complete the Hindsight integration checks this week and start the hardware process in the week of 28 September. Head assembly, powered movement and a future body keep their separate test and safety requirements.
Read J-016Development phases
There is no percentage-complete score. Each stage advances when the relevant evidence exists.
MS-00 established the controlled Thor programme, source authority, 102 effective requirements, 16 milestones, 30 tracked risks, and explicit evidence labels.
Keep the controlled baseline and traceability coherent
The 128 GB-class Thor kit is operational. MS-01 and MS-02 carry an explicit pristine-state deviation and an open recovery gate; MS-03 passed for standalone XVF/Pebble AEC and C920 fixtures.
Close recovery evidence without overstating the conditional passes
The exact Qwen3-Omni NVFP4 reference received a conditional pass and was then retired from active conversation. MS-06 passed its declared Core/provider text-governance scope. ConversationLedger now owns the spoken lifecycle, while a derived open-session memory index remains separate from Qwen's bounded working set.
Preserve Core authority while each replacement runtime is qualified
The September 11 local/cloud recovery freeze is preserved on engineering main. Both supplied Spanish sessions exercised conversation, explicit live/history vision, research and clean shutdown. Follow-up reliability, freshness and latency gates remain open.
Pass bilingual duplex, latency-tail, lifecycle, visual grounding, freshness and resource gates
The separate memory branch implements durable PostgreSQL records, current rights, reviewed English/Spanish input and restart workflows. The latest operator-reported backend result is 903/903 required methods, zero skips. G8/G9, deployment security, participants and physical embodiment remain separately gated.
Qualify G8/G9; close deployment/recovery and participant gates before Alpha claims
A stage advances through passing tests, not visual spectacle or calendar pressure.
Future hardware connects through bounded commands and local safety control.
Advanced platforms should be accessed through laboratories, partners, or a funded use case.