Instruction file imported from D13tr1ch/Infrastructure (
.github/instructions/orion-project.instructions.md). Copyright stays with the author.
Active Project: Orion Audio Analytics Platform
What Is Orion
Distributed audio analytics platform on a 3-node Raspberry Pi 5 cluster + 1 Windows control plane, connected via Tailscale mesh VPN. Captures 16-channel audio, routes via custom binary protocol (Orion Transport Protocol v1.0), runs Hailo-8 AI inference, stores results in SQLite.
Architecture Reference
Full reverse-engineered architecture: docs/orion-platform-architecture.md
Current State
- All containers stopped since March 14, 2026 (v1.5.6).
- CTRL01 (Navigation, Windows) is offline and being decommissioned.
- Platform is NOT running.
Active Migration: CTRL01 → MAL01 (Andromeda)
The CTRL01 routing/control plane code must be migrated to MAL01 (Andromeda). This eliminates the Windows dependency and consolidates routing onto the cluster.
What CTRL01 Does (from env vars and connection configs)
- Routes DATA/HEALTH/CONTROL traffic on ports 7200, 7201, 7202
- Provides Routing API on port 7210
- Acts as gateway between PAL01 (publisher) and ASL01 (analytics) / MAL01 (memory)
Migration Impact
- PAL01 publisher-connection currently points
HUB_HOST=100.108.146.123(CTRL01) → must change to MAL01 - ASL01 analytics-ingestion expects data from CTRL01 → must accept from MAL01
- MAL01 memory containers reference
CTRL01_ROUTING_API=http://100.108.146.123:7210→ must become local - All inter-node routing assumptions change
Cluster Access
- SSH:
orion@<tailscale_ip>(key-only, NOPASSWD sudo) - ASL01:
100.107.171.20| PAL01:100.65.57.70| MAL01:100.125.128.87 - Docker images were pruned on ASL01/MAL01 — container configs preserved in architecture doc
Team Assignments (Project Manager: Pat)
- Pat: Project planning, milestone tracking, delivery coordination
- Devin: CTRL01 code migration implementation, container updates, protocol work
- Angelica: Security review of migration (auth, API keys, network changes)
- Bob: Backup verification before migration, recovery plan
- Patricia: Dashboard/monitoring UI if needed
- Sage: Version bump and changelog for migration milestone
- Randy: Environment config updates (Docker compose, Tailscale ACLs, firewall rules)
Key Constraints
- No secrets in code — use TouchVault for local dev, Docker secrets for containers
- API keys currently baked into container env vars — must be secured during migration
- Socket permission bug between analytics-ingestion and analytics-engine (UID mismatch) — fix during migration
- Hailo-8 accelerator on ASL01 only — analytics must stay on ASL01