Engineer’s
Corner.
Inside the build: the architecture, code, hardware and experiments behind Ash.
Archive updated November 1, 2026 · Dated reports retain their individual evidence cutoffs
Follow the project from its first dated record on September 16. Each report keeps demonstrated work, failed experiments and future designs visible. The original source book and raw evidence remain private.
One character.
Several working layers.
See how perception, state, behavior, voice and the public world fit together—and which connections still need to be built.
Explore the architecture →- 01Pi benchPerception → state → behavior
- 02Voice developmentListen → validate → reply → speak
- 03Browser worldAnimation, scenes and ambience
The build, week by week
Ash’s voice: identity, validation, and the remaining wait
What was deployed, which responses were prepared, what the model actually generated, and why a successful turn still felt slow.
Read the engineering report Engineering update / October 30, 2026Visual continuity needs an approval record
Approved references, still contact and an informational guide solved different production problems.
Read the engineering report Engineering report / October 25–29, 2026An execution failure without an established cause
Preserve the difference between readable files, earlier renders, owner actions and the later agent launch failure.
Read the engineering report Engineering report / October 24, 2026File integrity is only one recovery gate
The snapshot, retained exceptions and narrow dependency restore had measurable outcomes; application recovery remained open.
Read the engineering report Engineering report / October 21–24, 2026Readable motion needs more than clean geometry
Service contact, droid modeling and the DDS–Ash letter review exposed different kinds of failure.
Read the engineering report Engineering update / October 16, 2026When Account Recovery Interrupts Engineering
An unresolved OpenAI access disruption, its impact on RC-01 development, and the continuity lessons we are carrying forward.
Read the engineering report Engineering update / October 16, 2026From character design to readable motion
Gigi joins the Recon Chinchilla world while short, controlled animation studies test whether expressions remain clear in motion.
Read the engineering report Integration readiness / October 12, 2026What the next RC-01 checks need to establish
Approved paper criteria define the next checks. New qualification cases remain unrun, with hardware and powered testing on hold.
Read the engineering report Paper direction approved / Proposed details / October 12, 2026Physical Ash: measure before building
The stationary service-chassis direction is approved on paper. Exact design, compatibility and G0–G7 remain open; no hardware changes or powered testing are authorized.
Read the engineering report 01 / September 14–20, 2026The bench before the robot
The first dated project record begins September 16. This week established the physical bench and the records needed to tell an installed component from a working subsystem.
Read the engineering report 02 / September 21–27, 2026From pixels to a managed presence signal
Camera and accelerator bring-up exposed two separate cable problems. The larger software lesson was to turn a frame’s detections into one decision before updating presence state.
Read the engineering report 03 / September 28–October 4, 2026State, recovery and the first native audio contract
The architecture gained explicit state and behavior services. The most important correction was to stop treating recovered history as a new live event. Native audio then gained stable event identity without changing its accepted segmentation.
Read the engineering report 04 / October 5–11, 2026 · through October 10Voice, character and a public engineering surface
The current week joined a public website, a more convincing coffee animation, local voice trials and the approved Michael voice. It also produced clearer boundaries around what Ash knows and what is still only designed.
Read the engineering report Weekend / October 9–12, 2026Weekend Engineering Review October 9 to 11 2026
Voice selection, bounded demonstrations, failures and open validation gates.
Read the engineering report Weekend / October 9–12, 2026When Progress Stops
A historical pause, a subsequent owner release, and the validation still required.
Read the engineering report Weekend / October 9–12, 2026Controlled voice regression after freeze release
Proposed procedure — NOT RUN. Freeze released; live validation and acceptance remain open.
Read the engineering report Characters / October 12, 2026The Command Center cast
Approved appearances, reference assets and the production work still open.
Read the engineering report Animation and features / October 12, 2026Animation, features and open tests
The approved CODD website routine, isolated pilot evidence, DDS requirements and seasonal design intent.
Read the engineering report Documentation / October 12, 2026Weekend documentation and acceptance register
Public weekend addendum and acceptance register. The private Project Book continuation is complete as edition 1.14; operational validation remains open.
Read the engineering report