BMT-02.02 Executive Summary#
BlueMirror.tech | May 2026#
David Okonkwo is a systems architect at a Phoenix home health agency preparing to deploy BlueMirror into eighty households. He opens the infrastructure agent inventory expecting either a marketing list or an undifferentiated technical spec. What he finds is neither. The thirty-one infrastructure agents are organized by functional domain, each carrying a defined autonomy default and a deployment preference that reflects both the latency requirement and the privacy sensitivity of the data it handles.
The decomposition follows from the concierge architecture directly. Each of the thirteen user-facing concierge agents needs infrastructure support. Healthcare has eight distinct operational domains — medications, appointments, care transitions, symptoms, cognition, nutrition, exercise, and vital signs — because each has its own data model, its own external integration requirements, and its own escalation patterns. Collapsing them would force each agent to reason outside its domain. Splitting them further would create coordination overhead between components that belong together. The count of thirty-one is a result of domain logic applied consistently, not a design target.
Two attributes govern every infrastructure agent. The autonomy default runs from 0.25 to 0.75 on the Human Agency Scale, calibrated by the risk profile of the domain. The Vital Signs Analyst, which does observational trending, runs at 0.75. The Care Transition Manager, which involves irreversible multi-party commitments, runs at 0.25. The deployment preference reflects privacy and latency: agents handling the most sensitive data (cognitive state, emotional signals, voice) target Zone 1, the Local Pane in the person’s home. Agents requiring cross-domain reasoning or external system integration target Zone 2, the regional Community Pane. Neither attribute is configurable by a deploying agency. They are set by the architecture.
The healthcare domain fields eight agents. The Medication Manager, running at 0.75 autonomy, handles reminders, refills, adherence, and interaction checks without requiring approval for observational actions. The Appointment Coordinator, at 0.5 autonomy, queues cancellations for person approval because scheduling changes create downstream consequences for providers and family. The Care Transition Manager, at 0.25 autonomy, gathers information and builds plans but does not execute until approved, because care transitions involve irreversible decisions and multi-party coordination. The Symptom Monitor, Cognitive State Assessor, Nutrition Tracker, Exercise Monitor, and Vital Signs Analyst round out the group, each with a defined autonomy and a deployment target that reflects its data sensitivity.
Memory care agents address a specialized population whose technical requirements differ from general interaction agents. Six agents cover this domain. Five operate in Zone 1 only, because the behavioral signals they process — orientation, lucidity, sundowning patterns, repetitive questioning — are the most privacy-sensitive data the system handles. The sixth, the Communication Adapter, is Zone 2-eligible because its function (real-time language complexity adjustment) does not require Zone 1 residency. The Sundowning Support agent runs at 0.75 autonomy because a person showing sundowning signs at 4 p.m. cannot wait for human approval to receive a calming response. The high autonomy reflects the urgency, not a relaxation of the usual constraints.
Five external integration agents connect BlueMirror to systems outside the platform: pharmacy, provider, insurance, transportation, and emergency services. Four run at 0.25 to 0.5 autonomy, with the pattern matching the consequences of action. The Emergency Responder is the exception: 0.75 autonomy and the only agent permitted to break privacy boundaries in a life-threatening situation. When a fall is detected and the person does not respond to the verification prompt, the Emergency Responder shares location and medical information with the responding service. The prior consent given at setup is treated as authorization for this action. The narrow exception is defined with precision: not “the system thinks this is unwise” but “the person cannot consent because she is unconscious.”
Five Blue Pane membrane agents operate at the infrastructure level without user-facing interaction: Context Gate Controller, Trust Scorer, Negotiation Sandbox Manager, Manipulation Detector, and Audit Trail Logger. Their full treatment is in Series 03. They are introduced here because the agent inventory is incomplete without them.
For a deploying agency like David’s, the inventory produces a specific integration map. His care management software integrates with three of the eight healthcare agents and one family coordination agent. The other agents are not touched. The agency’s existing functionality is preserved. BlueMirror adds capability around it, not instead of it.
The full article, including the complete interaction maps and zone-by-zone deployment topology for all thirty-one agents, is at BlueMirror.tech.