How Pause-Health.ai is actually built — Care Router policy, multi-agent fabric, Data 360 grounding, MCP tools. Public source code, public design choices.
Planned essayWhat 'grounding' actually means in a clinical agent
The federation pattern against Salesforce Health Cloud + JupyterHealth FHIR + DBDP biomarkers, why the agent doesn't move PHI, and how the prototype keeps the same shape as the production stack.
Planned essayWhy our Care Router uses a policy layer instead of a pure LLM
Six canonical pathways, deterministic risk-band heuristics, and the LLM as the recommendation engine on top of (not in place of) the policy.
Planned essayAgent Fabric — building a multi-agent trace inspector clinicians can read
OpenTelemetry-style spans for a clinical decision (intake -> identity -> grounding -> routing), and what an A2A protocol looks like at the boundary.
Planned essayMCP tools for menopause care — what we exposed and why
The find_menopause_providers and get_provider_details tools, why we expose them via Model Context Protocol, and how a clinical agent should use them safely.