Replace ESP32 with unified Raspberry Pi controller and update course README #4

Closed
opened 2026-10-20 09:58:43 +03:00 by rznz · 0 comments
Owner

Description

Replace the split ESP32 hardware peripheral and standalone Linux hub with a single Raspberry Pi running embedded Linux (GPIO peripheral I/O, scenario engine, and REST/WebSocket API), and update README.md with the course project proposal required for checkpoint 1.

Acceptance Criteria

  • README.md contains the course proposal sections (team members and Forgejo handles, topic, tasks, expected December 2026 outcome, and public repository link) targeting Raspberry Pi and Android (Java).
  • AGENTS.md and ARCHITECTURE.md describe the Raspberry Pi as the unified embedded Linux physical controller and scenario/API hub, with optional VPS sync.
  • System context and core data flow in ARCHITECTURE.md connect the Android app directly to the Raspberry Pi hub over local REST/WebSocket and remove the separate ESP32 network hop.
  • Skill workflow references (solve_workflow.md, schema.md) reflect Raspberry Pi hardware/service verification instead of ESP32 firmware compilation.
  • Task memory (outcome.md) records the architectural decision and regenerates docs/generated/ indexes cleanly.
## Description Replace the split ESP32 hardware peripheral and standalone Linux hub with a single Raspberry Pi running embedded Linux (GPIO peripheral I/O, scenario engine, and REST/WebSocket API), and update `README.md` with the course project proposal required for checkpoint 1. ## Acceptance Criteria - [ ] `README.md` contains the course proposal sections (team members and Forgejo handles, topic, tasks, expected December 2026 outcome, and public repository link) targeting Raspberry Pi and Android (Java). - [ ] `AGENTS.md` and `ARCHITECTURE.md` describe the Raspberry Pi as the unified embedded Linux physical controller and scenario/API hub, with optional VPS sync. - [ ] System context and core data flow in `ARCHITECTURE.md` connect the Android app directly to the Raspberry Pi hub over local REST/WebSocket and remove the separate ESP32 network hop. - [ ] Skill workflow references (`solve_workflow.md`, `schema.md`) reflect Raspberry Pi hardware/service verification instead of ESP32 firmware compilation. - [ ] Task memory (`outcome.md`) records the architectural decision and regenerates `docs/generated/` indexes cleanly.
rznz self-assigned this 2026-10-20 09:58:43 +03:00
rznz closed this issue 2026-10-20 10:06:09 +03:00
Sign in to join this conversation.
No description provided.