Production readiness
Readiness requires dated evidence from the actual services, accounts and hardware.
Acceptance
Test private access and unauthorized-request rejection, real iPhone recording and playback, laptop routing, fresh frames and disconnected-device behavior. Confirm stale sources are labeled honestly.
Use disposable fixtures to test consent, rejection, duplicate decisions, changed payloads and failures. Do not approve production actions merely to test the interface.
Known boundaries
The baseline has a documentation-integrity failure and unresolved Home Assistant hostname. It is not a certificate of complete connectivity.
Measure latency and transparent-screen readability in the actual environment. Quotas, sleep, permissions and network outages can interrupt service.
Implementation sources
Repository paths below describe the implementation. They do not certify a running deployment or a configured external account.
docs/HUD-DEVELOPMENT-VERIFICATION-2026-10-20.mdsrc/mushegh/brain/health.pysrc/mushegh/brain/hud_sources.py
Subsystem directory · HUD guide · Verification and known limits