The five adversaries converge on a single structural insight: the architecture is not the moat. GR00T N1 will commoditize the nav stack. Open-source communities will replicate the dual-rate VLM pattern. A skeptical CTO will correctly identify the efficiency paradox in the current 2B-params-for-2-tokens design. Regulators will reclassify home camera AI as surveillance. None of these attacks are wrong on the facts. What they all miss is the distinction between the plumbing and the water.

The household semantic map — built incrementally across 18+ months of navigation, annotated with room labels from VLM scene classification, indexed by SLAM pose, enriched with temporal patterns of human occupancy — is Annie's actual competitive position. This map cannot be cloned, downloaded, or commoditized. It is the spatial memory of one specific household, accumulated through embodied presence. When GR00T N1 ships a $399 developer kit with a better nav stack, Annie adopts the better nav stack and retains the map. The open-source community publishing SmolVLM nav tutorials accelerates Annie's component upgrades for free. The architecture is the carrier; the map is the cargo.

The CTO's challenges expose two genuine gaps that are not resolved by the moat argument. First, the WiFi dependency: when the router drops, Tier 1 (Titan LLM) and Tier 2 (Panda VLM) both halt, leaving only the Pi's reactive ESTOP layer. There is no local fallback planner for goal-directed navigation. Activating the idle Hailo-8 AI HAT+ (26 TOPS, YOLOv8n @ 430 FPS) partially closes this fragility — on-robot obstacle detection becomes WiFi-independent, so a 2.4 GHz jam no longer blinds the safety layer. But semantic reasoning still halts, so the naive WiFi attack from the insider-threat card degrades gracefully rather than fails catastrophically, and a dual-band sophisticated attacker remains an open gap (cross-ref Lens 04 on constraint fragility). Second, the evaluation vacuum: ATE, VLM obstacle accuracy, and navigation success rate are planned metrics but not yet running.

The regulatory risk is the least tractable in the short term and the most tractable architecturally. Local-first processing is the strongest available defense against surveillance classification: camera frames never leave the home network, and the JSONL audit trail already present in the Context Engine can log every motor command with timestamps. The EU AI Act high-risk pathway is painful for small developers but survivable for a self-hosted personal deployment where the "user" and the "deployer" are the same household. The real regulatory risk is not the current rules — it is the 2027 amendment cycle, which will likely respond to incidents involving commercial home robots by tightening requirements that catch hobbyist deployments in the dragnet. The counter is to document consent architecture now, before the rules are written, so that Annie's privacy-by-design posture is a matter of record.