LOUD Auto

Agents must first read AGENTS.md, the continuity protocol, and both continuation documents. These are mandatory working gates.

New sessions: start a PM with "Read /opt/projects/loud-auto/pm.md" (pm.md) or a developer with "Read /opt/projects/loud-auto/dev.md" (dev.md) plus the PM's assignment. Each role file sets the role and its required reading.

Local control, integration and orchestration platform. Architecture baseline 1.0 is finalised after two Claude reviews. Pi 1 and kitchen Pi 2 have user-confirmed audio; both were last verified wired for the physical timing baseline. The central audio lab supports large file uploads and independent destination selection without a lab login. Clock stability, physical multi-output timing and external interoperability remain qualification work.

• Architecture baseline 1.0 — adopted choices and execution gates
• Living architecture — product requirements and boundaries
• Technical design — stack, contracts, lifecycle and milestones
• Complete architecture v1.0 — finalised architecture in one file
• Review dispositions and second-review closure — findings and decisions
• Audio endpoint agent — route persistence, API and recovery
• LOUD Panel Android client — Kotlin/WebView shell, HONOR installation and kiosk milestones
• Device identity — MAC discovery, enrolled IDs and changing IPs
• Machines and equipment and first Pi inventory
• Pi preparation and network failover runbook
• Decisions and questions
• OREI AES67 compatibility check — manufacturer evidence and commercial endpoint shortlist
• Physical timing capture and offline analysis tools
• Experiments and evidence
• Planned server music player — playlists, independent virtual players and room-panel controls
• Future TV and distributed surround — ARC/eARC capture, HDMI output and split speaker channels
• Smart512 assessment
• Consolidated handover
• Technical continuation and project management continuation

Stable technical namespace: loudauto. Majel is a temporary conversational codename only. Historical reviews and submitted packets remain preserved under docs/reviews/; current design changes go into the living architecture and decision register.