Bare-metal StackChan,
back on the bench.
24 kHz PCM16 full-duplex audio is the current bring-up gate. The web console reports what the connected firmware can prove; it does not advertise unfinished capabilities.
Engineering revival in progress. Not cleared for unsupervised use.
Current implementation boundary
Show evidence before making promises.
Safety must be demonstrated
Guardian gating and authenticated records are part of the revival, but device indicators and policy behavior still need hardware-in-the-loop validation.
Bench connectivity first
The current CoreS3 target uses Wi-Fi during bring-up. Cellular behavior is not part of the validated StackChan path.
Reported, not assumed
The dashboard shows device status, sessions, turns, and captures only when the connected firmware and API report them.
Native StackChan path
The active revival target is bare-metal ESP-IDF on M5Stack CoreS3. The archived Arduino implementation is reference material only.
Revival sequence
Account gate, hardware gate, audio gate.
Sign in and affirm
Continue through ZergAI, then complete the separate parent or legal-guardian checkpoint.
Bring it up on the bench
Verify power, serial recovery, camera, servo limits, and audio transport with the wired management path.
Prove the audio gate
Measure simultaneous microphone capture and speaker playback before enabling conversational use.
The bring-up boundary
- · Keep the unit powered from a supervised bench supply during revival work.
- · Validate camera and microphone indicators against observed hardware behavior.
- · Treat sessions and captures as reported evidence, not proof that all activity was recorded.
- · Exercise servo limits and the physical stop path before fitting the mechanism.
- · Roll back to a known-good image whenever a stage violates its acceptance gate.
Questions you might have
Good questions.
Is this ready for a child to use?
No. The current build is a revival and validation target. Keep it supervised on the bench until the published safety and hardware gates pass.
What is the current hardware target?
M5Stack CoreS3 with the StackChan base, built with ESP-IDF. The legacy Arduino tree is not the active implementation.
What does full duplex mean here?
Microphone capture and speaker playback must run at the same time without starving the network, display, camera, or servo tasks.
What should I do if a check fails?
Stop the stage, save the logs and measurements, return to the last known-good firmware, and diagnose one peripheral at a time.
Ready to help validate it?
Sign in through ZergAI, complete the adult checkpoint, and inspect the device evidence.