Hub-and-satellites: Pi speakers handle voice ingress with local fallback. Home server runs orchestration, inference, memory, and portal. Chromebook PWA is the primary learning UI.
Pi Satellite (per child)
OpenWakeWord (custom wake)Vosk STT (child-tuned)Kokoro-82M TTST0/T1 local LLM fallbackLAN client to hub
Home Server (hub)
router-rs (Rust Tokio)orchestrator-go (32 agents)policy-go (Guardian)scheduler-go (SM-2 cron)memory-go (Second Brain)llama-server (C++, T2)Neo4j (graph)Postgres/SQLite (events)Obsidian vault syncNext.js portalOpenMAIC forkActix-web (parent portal)
Chromebook PWA
Next.js (SSR/CSR)WebSocket/WebRTCBevy WebAssembly simsOpenMAIC classroom UITouch-friendly child UX
WHY THIS SPLIT
Low latency + resilience on each child device. Heavy reasoning on stronger hardware. One shared family memory graph. One parent control plane. Matches Pi 5 capabilities, llama.cpp local-serving strengths, and practical separation between voice ingress and multi-agent orchestration.