Margaret Chen lives alone in a two-bedroom condo in Sacramento. She is seventy-three. Her husband died four years ago. Her daughter lives in Portland. On a Wednesday in April, Margaret reads a novel for an hour after breakfast, takes her morning medications, video-calls a student in Brisbane to teach a Japanese cooking class, makes lunch, naps, attends to a Medicare paperwork issue she did not know she had, and goes to bed at ten. By any reasonable measure, it is an uneventful day.
Behind that uneventful day, thirteen agents worked. The health concierge flagged a three-day blood pressure trend that warranted attention at her next appointment, queued the question for the physician, and adjusted her evening medication reminder by twenty minutes. The buying agent placed her weekly pharmacy order with a patient assistance program discount that took her metformin copay from forty-two dollars to zero. The home environment lowered the thermostat at 8:30 because last night’s sleep data suggested her evening routine should start earlier. The financial concierge caught a forty-seven-dollar duplicate charge from the pharmacy and queued the dispute. The earning concierge confirmed her four o’clock with the student in Brisbane, handled the time zone math, and processed the payment. The family coordination agent sent her daughter a weekly summary that did not mention the blood pressure trend (it does not surface day-to-day variability) and did not mention the Medicare issue (the legal advocate was already handling it).
Margaret managed none of this. She read a book, made lunch, taught a cooking class, and went to bed.
The thirteen concierge agents are the user-facing layer of the BlueMirror architecture. From the person’s point of view, they compose into a personal services firm. The decomposition is not a feature of the marketing. It is the architecture.
Why thirteen#
The number is a design decision, not a count of capabilities. We considered five (a coarse decomposition that mirrors common benefit categories: health, finance, home, family, social). We considered fifty (a fine-grained decomposition that gives each capability its own agent). Both fail for the same reason in opposite directions.
Five fails because every interaction crosses domain boundaries. The medication change is a health event that triggers a buying event (new prescription) that triggers a financial event (copay change) that triggers a nutrition event (sodium restriction) that triggers a family event (the daughter wants to know). With five agents, each agent has to reason across the boundary on every turn. The reasoning is expensive, the latency suffers, and the model of the person becomes diffuse. Coarse decomposition pushes coordination cost into every interaction.
Fifty fails because the person cannot hold fifty agents in her head. The cognitive overhead of “which agent am I talking to” is itself a barrier. The testing complexity multiplies. The coordination cost between agents that should be one agent (a “morning medication” agent and an “evening medication” agent) consumes engineering time that could be spent on capability. Fine-grained decomposition pushes coordination cost into the build.
Thirteen is the number that maps to the domains the person recognizes in her own life: health, money, buying, legal help, home upkeep, thinking and memory, caregiving support, social connection, food, earning, home environment, purpose, and family. Each of these is something Margaret would name if asked what fills her week. Each has its own autonomy profile, its own privacy tier, its own escalation defaults. The decomposition is structural rather than cosmetic: it follows the contour of how aging adults actually organize their lives.
The mapping is also editorially anchored. Each concierge agent corresponds to one or more series in BlueMirror.life, the publication that defined the solution space. The health concierge maps to BML Series 01 (medications, vitals, clinical care). The buying agent maps to BML Series 02 (procurement, financial decisions, the fiduciary inversion). The cognitive concierge maps to BML Series 04 and 05 (memory, dementia care). The alignment is not a coincidence. The thirteen agents are the architectural realization of the editorial decomposition.
The integration argument#
The grocery order changed when the medication changed. That is the architecture in one sentence.
Margaret’s physician adjusted her diuretic on a Tuesday morning. By Tuesday evening, three things had happened without anyone telling them to happen. The buying agent’s grocery list, scheduled for delivery Thursday, removed the canned soups and added the low-sodium versions. The nutrition concierge updated tomorrow’s meal plan, reducing one ingredient by half and substituting another entirely. The financial concierge recalculated the monthly grocery budget because the low-sodium versions cost about twelve percent more per item.
Three agents responded to a fourth agent’s event. None of them communicated through APIs in the integration sense. They share a memory model: a per-person context structure that every concierge agent reads and updates. When the health concierge wrote “sodium restriction reduced from 2,000mg/day to 1,500mg/day” into Margaret’s context, the buying agent and the nutrition concierge saw it on the next read.
This is the integration that no standalone application can replicate. Thirteen separate apps from thirteen separate vendors, each excellent at its own domain, cannot reach this coherence because no single app holds the full picture. The medication app does not know about the meal plan. The grocery app does not know about the medication. The budgeting app does not know about either. Even with the best APIs and the best intentions, the integration cost defeats the integration value. Each pair of vendors must agree on a schema. Each integration must be maintained as both vendors evolve. Each new domain doubles the integration surface. The wealthy solve this with a personal staff who hold the full picture in their heads and coordinate by walking down the hall. BlueMirror solves it with a shared memory architecture that every agent reads from and writes to.
The integration is not a feature of the architecture. It is the architecture.
What sits beneath the thirteen#
The user sees thirteen concierge agents. The system runs thirty-one infrastructure agents on a portfolio of thirty small language models. The user does not pick a model, configure an infrastructure agent, or know that any of this exists. She talks to her health concierge. The health concierge handles the rest.
The decomposition matters for the engineering. Each concierge composes from a defined set of infrastructure agents, each of which calls a defined set of SLMs. The health concierge composes from six infrastructure agents (Medication Manager, Symptom Monitor, Vital Signs Analyst, Exercise Monitor, Appointment Coordinator, Care Transition Manager) running on five SLMs (Medication Advisor at 150M parameters with under 75ms inference, Cognitive State Estimator at 200M parameters with under 75ms inference, Safety Filter at 100M parameters with under 25ms inference, Intent Classifier at 150M parameters with under 50ms inference, Response Generator at 400M parameters with under 100ms inference). The cognitive concierge composes from seven infrastructure agents and a different five-model SLM stack tuned for memory care. The buying agent composes from three infrastructure agents and a stack that emphasizes context routing and trust evaluation.
This compositional pattern is what allows thirteen concierge agents to share infrastructure without sharing concerns. The Cognitive State Estimator is one model. The health concierge calls it to assess whether the person is having a clear day before delivering complex medication instructions. The cognitive concierge calls it to decide how much language simplification to apply. The earning concierge calls it to determine whether to schedule active or asynchronous earning today. One model. Three concierge agents. The model does not need to know which concierge called it. The concierge agents do not need to know how the model works.
The orchestration layer (Series 02) is what decides which infrastructure agents and SLMs activate for which request. The integration surface (Series 03) is what decides what external systems can see and do. The memory layer (Series 05) is what decides what the system retains and how. The intelligence layer (Series 06) is what powers the SLMs themselves. From Margaret’s perspective, none of this exists. She talks to her concierge. The concierge handles the rest.
The concierge inventory#
Each concierge gets its own deep dive elsewhere in the series. The orientation below is the map.
The health concierge orchestrates medication management, symptom monitoring, vital signs trending, exercise tracking, appointment coordination, and care transition planning. It is the most complex single concierge: six infrastructure agents under a mixed autonomy profile that runs high for routine monitoring and low for care transitions. It does not replace the clinician. It fills the 364 days a year when no one is watching the trends. (BMT-01.02)
The buying agent demonstrates the structural inversion BlueMirror represents. Every recommendation Margaret has ever received came from someone selling something. The buying agent has zero seller bias. It optimizes for the buyer because the buyer is the only one paying for it. The Blue Pane membrane (Series 03) controls what vendor agents see during agent-to-agent negotiation. (BMT-01.03)
The financial concierge addresses the compound decision problem: every financial decision for an aging adult interacts with health, housing, and benefits decisions. When to claim Social Security depends on health trajectory. Whether to switch Medicare plans depends on medication changes. The financial concierge can model these interactions because it shares context with the agents that own the other domains. (BMT-01.04)
The legal advocate is the most restricted agent in the system. Its autonomy default is 0.25, the lowest of any concierge. The boundary between AI assistance and legal representation is regulatory, and the architecture must not cross it. The legal advocate prepares appeals, tracks deadlines, gathers documentation. It does not advise, represent, or decide. (BMT-01.05)
The home maintenance concierge transforms maintenance from reactive crisis to proactive prevention. The widower whose wife managed everything for forty years does not know the HVAC filter needs changing. He finds out when the system fails in August. The maintenance concierge knows the schedule, vets the contractors, manages the car alongside the house. It does not replace the annual inspection. (BMT-01.06)
The cognitive concierge is the most ethically complex agent. It serves people whose capacity to consent to being served is changing. Six memory care infrastructure agents, five of them edge-only because latency in cognitive support is a dignity metric. The dignity constraint governs every design decision: would a competent human companion handle this the same way? (BMT-01.07)
The caregiver concierge serves the person caring for the person. It detects burnout through communication pattern analysis, facilitates respite, manages the switchboard problem. The caregiver who is also aging is increasingly common: the seventy-five-year-old daughter caring for the ninety-five-year-old mother. The agent serves both. (BMT-01.08)
The social connection concierge detects isolation before crisis through behavioral signals like the six-day silence. It removes barriers to genuine connection. It does not manufacture connection, because manufactured connection corrodes faster than no connection. The five conditions for genuine connection (shared context, mutual vulnerability, reciprocity, temporal continuity, agency) cannot be engineered. The barriers can be. (BMT-01.09)
The nutrition concierge sits in a separate domain because nutrition spans health, buying, culture, preference, and social eating. The dietary restriction from health informs the meal plan. The meal plan drives procurement through buying. Cultural food preferences and cooking ability constrain what the meal plan can prescribe. One concierge holds these threads. (BMT-01.10)
The earning concierge sits between BGO (institutional deployment) and the open marketplace. It solves discovery, logistics, and cognitive protection. The transition from live teaching to recorded content to passive library income is managed by the system based on cognitive state, not by the person’s explicit decision. Earned autonomy applied to earning. (BMT-01.11)
The home environment concierge is distinct from home maintenance: maintenance manages the physical plant, environment manages the living conditions inside it. Ambient monitoring, safety adaptation, the house that learns the person’s patterns. The robotics integration path runs through this agent. The robot does not build its own personalization. It calls BlueMirror. (BMT-01.12)
The purpose and deployment concierge identifies that the person has knowledge, skills, or experience with deployment value and connects her to organizations that need it. Distinct from earning: purpose deployments may or may not generate income. The retired aerospace engineer whose propulsion knowledge is deployable to academic labs. The retired oncology nurse whose experience is deployable to nursing education programs. (BMT-01.13)
The family coordination concierge manages the family’s interaction with the person’s care. The person is not the switchboard. Privacy boundaries between family members: the daughter sees the weekly health summary but not the financial details. The son manages the home maintenance but does not see the cognitive scores. Consensus building across family members with different information, different priorities, and different proximity. (BMT-01.14)
The company of one#
The framing for partner architects, technical due diligence, and the people building the system: this architecture gives every user a personal services firm. Clinical concierge. Financial advisor. Nutritionist. Psychologist. Legal advocate. Logistical assistant. Earning manager. The wealthy have had this team for decades. The cost of that team for one person, sourced from the open market, runs $200,000 to $500,000 per year. BlueMirror provides the structural representation at $75 to $100 per month at launch, declining toward $20 per month over five years as the SLMs learn and marginal cost approaches zero.
This is not a claim that BlueMirror equals the family office. It is a claim about the structure of representation. The family office holds the full picture across health, money, home, family, and purpose. So does BlueMirror. The family office coordinates across domains without making the principal manage the coordination. So does BlueMirror. The family office is paid by the principal and works for the principal alone, with no commission from sellers or providers. So does BlueMirror.
The structural claim is the architecture. The economic claim, that this representation can be made available at a price the population can afford, is the subject of Series 10. The ethical claim, that the architecture is allowed to do what it does and refuses what it must refuse, is the subject of Series 04. The remainder of Series 01 takes each concierge agent in turn and shows the structure that makes the claim concrete, beginning with the health concierge.
Cross-References#
The Map Nobody Gave You (BML-02.SYN). The editorial framing of agent representation that the thirteen concierge agents structurally realize.
The Brain and the Hands (BMT-02.01). The H-layer/L-layer orchestration architecture that decides which infrastructure agents and SLMs activate for each concierge request.
The Human Agency Scale (BMT-04.01). The autonomy framework each concierge agent follows, including the per-domain autonomy defaults referenced throughout this article.
The Retention Flywheel (BMT-10.04). The economic argument behind the company-of-one framing, including the cost-curve analysis that underlies the $75-to-$20 pricing trajectory.
Technical Appendix BMT-01.01-A is available to partners and investors at partners.bluemirror.tech.