Midlife Signal Intake

Upstream of intake

The acquisition funnel that feeds this agent

Before a patient reaches the intake agent above, a lead flows through three Agentforce agents over Google A2A: Inbound Lead Generation → Qualification → then either Patient Intake → Care Router (qualified & ready) or Prospecting & Nurture (warming). Each hop enforces its own Agent Fabric policies. Run a scenario, then open the trace.

Validated-instrument scoring

The Assessment agent that grades intake severity

The Assessment agent administers a validated instrument (MRS, Greene, PHQ-9, ISI) over Google A2A and scores it deterministically — real cutoff math, no LLM. The score maps onto the intake severity the Care Router consumes, and every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Eligibility & benefit verification (EBV)

The Benefits agent that verifies coverage before care

The Benefits & Coverage Verification agent runs a deterministic synthetic EBV round-trip over Google A2A — plan status, in/out-of-network, deductible + amount met, coinsurance/copay, and an estimated visit cost + patient responsibility, each tracing to a (mock) payer/clearinghouse source. This is a labeled demo mock — not a live 270/271 or FHIR eligibility call. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Appointment scheduling (book / reschedule)

The Scheduling agent that books the recommended visit

The Appointment Scheduling agent books (or reschedules) the MSCP menopause-specialist visit the Care Router recommends over Google A2A, honoring the requested modality against a deterministic synthetic provider calendar and returning a confirmed slot with a synthetic ServiceAppointment id + source provenance, then handing the booking to the Engagement Agent for reminders. This is a labeled demo mock — not a real Salesforce Scheduler / ServiceAppointment write. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Care-plan instantiation & summary (live Claude)

The Care Plan agent — the second live-Claude agent

The Care Plan agent deterministically instantiates a menopause care plan from a defined template (goals, interventions, follow-up cadence) based on the Care Router pathway/severity + intake, then writes a non-prescriptive progress summary with live Anthropic Claude, falling back to a deterministic scripted summary (with a recorded reason) on a missing key or any SDK error — just like the Care Router. It is governed by the same model allow-list and never commits a clinical action without a clinician. The templates are illustrative synthetics, not a certified care-plan engine. Run a preset, then open the trace.

Preset scenarios

After-visit summary & clinician handoff (live Claude)

The Clinical Summary agent — the third live-Claude agent

The Clinical Summary agent composes the outputs the other agents already produced (intake, the Care Router pathway, and any care plan) into two artifacts — a patient after-visit summary and a clinician handoff. The context is assembled deterministically from only the facts that are present, so the summary can only assert what the upstream agents established — the grounding guarantee is real. The phrasing is written with live Anthropic Claude, falling back to a deterministic scripted composition (with a recorded reason) on a missing key or any SDK error — just like the Care Plan agent. It is governed by the same model allow-list and commits no clinical action. The artifacts are illustrative synthetics, not a certified clinical-documentation engine. Run a preset, then open the trace.

Preset scenarios

Whole-person care · social needs

The SDOH agent that screens social needs and drafts referrals

The SDOH Screening agent deterministically screens the patient with a validated instrument (the CMS AHC-HRSN core domains: housing, food, transportation, utilities, interpersonal safety), flags the positive social-need domains, escalates a positive interpersonal-safety screen to a human social worker, and drafts consent-gated community-resource referrals (211, food bank, housing/utility assistance, a domestic-violence hotline) — human-approval-gated, never an autonomous enrollment. The community-resource catalog is illustrative synthetic, not a live directory of real programs. SDOH is separate from clinical severity — it raises a care-coordination flag. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Patient education & health coaching (live Claude)

The Patient Education agent — the fourth live-Claude agent

The Patient Education agent deterministically selects education modules from a defined evidence-sourced catalog (bone health, cardiovascular risk, sleep hygiene, vasomotor self-management, mood/stress, nutrition, physical activity) based on the intake symptoms/severity + upstream Care Plan focus areas + detected care gaps, then writes a warm, motivational coaching message with live Anthropic Claude, falling back to a deterministic scripted message (with a recorded reason) on a missing key or any SDK error — just like the Care Plan agent. It is general education only (no diagnosis, dosing, or individualized medical advice), every module traces to a defined evidence source, and any coaching outreach is consent-gated and human-approval-gated. The modules + source labels are illustrative synthetics, not a certified patient-education engine. Run a preset, then open the trace.

Preset scenarios

Proactive care-gap closure

The Care Gap agent that closes preventive-care gaps

The Care Gap Closure agent grounds on the patient's Data 360 context and deterministically detects menopause-relevant preventive-care gaps (bone-density/DEXA, lipid panel, mammogram, HRT follow-up) against an explicit as-of date, then drafts consent- and quiet-hours-aware outreach — human-approval-gated, never auto-sent — and hands it to the Engagement Agent. Every gap references a defined clinical-measure catalog id. The measures + intervals are illustrative synthetics, not a certified guideline engine. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Remote patient monitoring & symptom-trend tracking

The agent that tracks longitudinal trends and routes them to a clinician

The Remote Patient Monitoring agent ingests longitudinal, self-reported and wearable/device readings (hot-flash frequency, sleep, mood, resting heart rate, weight) and deterministically detects each metric's trend (improving / stable / worsening) over the reading window, applying synthetic red-flag thresholds. Worsening or red-flag trends are routed to a human clinician for review — the agent never takes an autonomous clinical action. The metrics + thresholds are illustrative synthetics, not a certified remote-monitoring device. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Population health & risk stratification

The agent that stratifies a whole panel and prioritizes outreach

The Population Health agent reasons over a whole panel of patients at once, taking already-produced per-patient signals (intake severity, assessment band, care gaps, SDOH domains, medication adherence, monitored trend) and deterministically scoring each patient with a transparent, additive risk model into a risk tier (low / rising / high), then building a prioritized outreach worklist for a human care manager. Every tier is explainable by its contributing factors, the model uses no protected-class attributes, and a tier never triggers an autonomous care decision. The factors, weights, cutoffs, and patient references are illustrative synthetics, not a certified risk-stratification model. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Consent & preferences management

The authoritative consent ledger the other agents' consent gates defer to

The Consent & Preferences Management agent is the source of truth for consent — it holds, per patient, a consent ledger (scopes, each granted / withheld / revoked with a recorded basis and optional expiry) and communication preferences (allowed channels, quiet hours, preferred language, frequency cap), and answers one deterministic question: may this patient be contacted / have data used for this scope over this channel at this time? Every consent state traces to a recorded basis, a revocation or expiry is honored immediately, and a decision never overrides a scope. The scopes, sources, and preferences are illustrative synthetics, not a certified consent-management system. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Clinical trials & research matching

The agent that matches a patient to research studies — consent-gated, never auto-enrolled

The Clinical Trials agent matches a single patient against a synthetic study catalog using structured eligibility criteria (age band, symptom profile, comorbidities, geography, prior therapy), returns the matching studies ranked with per-criterion explanations, and drafts a consent-gated outreach. Every eligibility determination traces to a defined criterion, outreach is gated on the patient's research consent (it defers to the Consent & Preferences Management agent's research scope), and the agent never auto-enrolls — enrollment requires informed consent and a human. The study catalog, sponsors, and criteria are illustrative synthetics, not real studies or a certified eligibility engine. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Language access & health equity

The agent that ensures LEP patients understand their care — qualified interpreters, approved translations, no machine-translated consent

The Language Access agent determines a patient's preferred language (deferring to the Consent & Preferences Management agent's preferred-language preference), decides whether a qualified medical interpreter is needed and of which modality, checks whether needed materials are available in that language from an approved translated-materials catalog, and flags equity gaps. Clinical interpretation uses a qualified medical interpreter only (never a family / ad-hoc / machine interpreter), in-language materials trace to an approved source, and machine translation is never used for clinical consent. When no qualified interpreter is available it escalates to a human coordinator — never an unqualified fallback. The languages, interpreter availability, materials, and provenance are illustrative synthetics, not a certified language-access system. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

HEDIS & quality reporting

The agent that rolls a panel of patients into HEDIS quality-measure compliance — never autonomously submitted

The HEDIS agent ingests already-produced per-patient signals across a panel and deterministically rolls them up into HEDIS quality-measure compliance — numerator, denominator, catalog-sourced exclusions, and compliance rate per measure — the artifact provider organizations owe payers under value-based-care contracts. Every measure must trace to the defined HEDIS measure catalog, every applied denominator exclusion must trace to a defined catalog exclusion on that measure, and every submission package requires human quality-team approval — the agent NEVER autonomously files to a payer / CMS / quality registry. The HEDIS measure catalog, denominator windows, numerator thresholds, and exclusion lists are illustrative synthetics, not NCQA-certified specifications. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Advance care planning (midlife touchpoint)

The agent that surfaces a patient's advance directives — never applies a change autonomously

The ACP agent uses perimenopause / menopause as a natural midlife touchpoint to surface which advance directives are on file (living will, DPOA-HC; POLST only for serious-illness), flag missing / stale / language-access gaps, and draft a consent-gated conversation prompt for the care team to deliver. Every directive on file must trace to the catalog + an approved source, every directive change is clinician + patient sign-off gated — the agent NEVER autonomously creates, updates, or overrides a directive — and for a limited-English-proficiency (LEP) patient the active prompt is withheld until a qualified-interpreter plan is documented (a safe answer, not a governance block). The directive catalog, source labels, and staleness threshold are illustrative synthetics, not a certified advance-directives registry. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Care team & case management

The agent that coordinates the multi-disciplinary team around a high-need patient — never a roster edit without the case manager

The care-team agent assembles the multi-disciplinary team around a single high-need menopause/midlife patient — PCP, MSCP, cardiology, endocrinology, bone-health, pelvic-floor PT, behavioral health — deterministically resolves which roles are needed from the patient's active clinical needs, assigns a case manager by a stable hash on the patient ref, and emits a shared team snapshot for the whole team. Every role must trace to the care-role catalog, every roster change is case-manager sign-off gated (no autonomous add/remove), and a legitimate team must include a PCP anchor. The care-role catalog, condition→role triggers, case-manager pool, and refs are illustrative synthetics, not a certified care-team schema. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Discharge & transitions of care

The agent that closes the loop back to primary care after a hospitalization — never a “recommended” follow-up, never an autonomous med change

The TOC agent runs the close-the-loop workflow after a hospitalization / ED / observation encounter — it reconciles the discharge medication list (added, removed, dose-changed, unchanged), books the follow-up (or hands off to the Appointment Scheduling agent — never a text recommendation), pulls the encounter-reason red-flag warning signs, emits the teach-back checklist, and assembles the PCP handoff summary. Every medication must trace to an approved source, every medication change is clinician-signoff gated (no autonomous changes), and the follow-up is a scheduled slot or an explicit awaiting-schedule handoff — the load-bearing 30-day- readmission guard against “recommended” follow-ups masquerading as complete. The encounter categories, red-flag catalog, follow-up window, approved-source labels, and teach-back items are illustrative synthetics, not a certified TOC system. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Grievance & appeals

The agent that classifies member complaints and coverage denials — never resolves them, never leaks PHI, never extends a regulatory deadline

The grievance-and-appeals agent runs the intake half of the regulated process — classifying a member complaint or coverage-denial appeal (grievance / billing / standard-appeal / expedited-appeal), routing it to the correct human queue (member-services / clinical-review / compliance), and stamping a regulatory deadline that traces to the case-type catalog + received date. It NEVER resolves, approves, or denies a case on its own; every case is queued for human review. The routing summary handed to the receiving queue is PHI-safe (structured only — no free-text PHI), so it can be delivered via lower-trust channels (Slack, email, ticketing) without leaking PHI. The case-type catalog, deadline windows, and queue mapping are illustrative synthetics, not Medicare Advantage Chapter 13 or a real appeal-adjudication engine. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Provider credentialing & directory

The agent that fixes the ghost network — no referral to an expired / sanctioned provider, no stale directory response returned as authoritative

The credentialing agent sits alongside the data substrate and gates every referral / scheduling attempt at the network boundary. It verifies each credential (state license, DEA, board cert, sanctions clearance, NPI) against approved sources (state-medical-board, DEA-registry, ABMS-board, OIG-LEIE-sanctions, NPI-registry), computes the No-Surprises-Act freshness flag (90-day accuracy window), and emits gate flags (canReferPatient / canBookAppointment / canReturnInDirectoryResponse) the Referral Management, Appointment Scheduling, and Transitions of Care agents can consult before handing off. Sanctioned status has highest precedence — a sanctioned provider never slips through, even when other credentials look complete. The catalog, verification sources, NSA window, and directory schema are illustrative synthetics, not NCQA / CAQH credentialing or a live state-medical-board / OIG-LEIE feed. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Quality-measure attribution

The other half of the HEDIS story — who gets the credit / accountability for the rate

The attribution agent pairs with the HEDIS & Quality Reporting agent: HEDIS computes the rates, this agent decides whose panel each patient counts on. It attributes every patient to a provider / clinic / VBC contract under a defined methodology from the catalog (plurality-of-visits, PCP-of-record, prospective Medicare Advantage, contract-defined window), honors the contract's exclusion terms (age band, network status, exclusion codes) so the scorecard isn't polluted with excluded patients, and applies a documented tie-break chain (most-recent-visit-wins then provider-ref-lexical-ascending) when the primary metric ties — no coin-flip, no gameable non-determinism. Rolls up per-provider counts so downstream HEDIS scoring lands on the right denominator. The methodology catalog, contract catalog, tie-break rules, and refs are illustrative synthetics, not CMS Shared Savings / ACO REACH / NCQA attribution. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Complex Care Management (CCM) · reimbursable time-tracking

The agent that assembles the CPT 99490 / 99491 / 99487 / 99489 billing package — never autonomously submits to CMS

The CCM agent runs the reimbursable time-tracking piece of care management for a Medicare-eligible high-need patient — it confirms CCM eligibility (≥ 2 catalog-sourced chronic conditions, Medicare age, coverage flag, consent), tracks per-activity monthly minutes against a defined activity catalog, maps the total to the CPT ladder (99490 → 99491 → 99487 → 99489), and assembles a billing package for human quality-team review. It NEVER autonomously submits a CMS claim, and every logged minute traces to a catalog activity + sums to the reported total (the guard against phantom-minute inflation, the classic CCM audit finding). The chronic-condition catalog, CCM activity catalog, CPT thresholds, and Medicare flags are illustrative synthetics, not CMS Chapter 12 CCM billing. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Claims Adjudication Assistant · first-pass payer-side

The agent that clean-pays, pends, or drafts a denial with a specific reason code — never autonomously finalizes a denial

The claims-adjudication agent applies payer-specific catalog edits (NCCI-PTP unbundling, LCD/NCD coverage, benefit limits, prior-auth linkage, duplicates, network, timely-filing) to each submitted claim, classifies as clean-pay / pend / deny-drafted with a specific catalog reason code, and routes anything non-clean to a human. The agent NEVER autonomously finalizes a denial — every denial is DRAFTED for adjudicator cosign, because denial letters are legally consequential under CMS / ERISA / state insurance code. The edit catalog, reason-code catalog, and benefit rules are illustrative synthetics, not CMS X12 837 / NCCI PTP / LCD/NCD or real payer benefit configuration. Every run is governed by the Agent Fabric. Run a preset, then open the trace.

Preset scenarios

Formulary & Drug Utilization Review · first-pass payer-side

The agent that preferred-approves, pends for step-therapy / quantity / interaction / non-formulary, and never autonomously overrides an exception

The formulary agent evaluates a proposed medication against the payer's catalog rules (tier, step-therapy, quantity limits, drug-drug interactions), classifies as preferred-approved / pend with a specific catalog reason code, and routes pends to a clinician (or pharmacist for interactions). The agent NEVER autonomously overrides a formulary exception — every non-preferred decision is DRAFTED for clinician cosign, because formulary exceptions require a prescriber's documented rationale under Medicare Advantage Chapter 6 + Part D. Menopause-relevant because HRT tier placement varies significantly by plan (transdermal estradiol is often Tier 2 or non-formulary despite being clinically preferred for CVD-risk profiles). The drug catalog, rule catalog, step-therapy chains, and interaction pairs are illustrative synthetics, not Medi-Span / RxNorm / a real payer formulary. Every run is governed by the Agent Fabric.

Preset scenarios

Fraud, Waste & Abuse Detection · pattern-based SIU screening

The agent that flags suspicious patterns — never denies a claim, never freezes payment, never scores on protected-class factors

The FWA agent screens claims against catalog-defined patterns (unbundling, upcoding, duplicate billing, quantity outliers, impossible-day billing, phantom services), classifies each hit by severity, and routes to the SIU for HUMAN review. It NEVER autonomously denies a claim, opens an investigation, or freezes payment — those are formal acts under Section 1557 / state insurance code / due process. The engine may NOT score on protected-class attributes (a well-documented compliance failure in real payer FWA systems). Distinct from Claims Adjudication (which AUTO-denies mechanical edits with a reason code): FWA is about suspicious patterns that need investigation. The pattern catalog, peer baselines, and severity thresholds are illustrative synthetics, not SAS / LexisNexis / a real payer SIU rule set. Every run is governed by the Agent Fabric.

Preset scenarios

Clinical Trial Payments & Stipends · IRB-schedule payment engine

The agent that pays per-visit stipends against IRB-approved schedules — never deviates without coordinator cosign, never pays without consent

The trial-payments agent pairs with Clinical Trials Matching. For each participant visit it looks up the IRB-approved compensation schedule (trial + visit type + IRB approval ref), verifies research-payment informed consent is on file (45 CFR 46 requirement), computes the stipend + travel reimbursement, and routes non-standard payments (missed visit, out-of-range travel, extra procedure) to the study coordinator for cosign. The agent NEVER autonomously deviates from an IRB-approved schedule and NEVER pays a non-consented participant. The trial catalog, IRB schedules, visit types, rules, and travel rates are illustrative synthetics, not IRBNet / WCG IRB / Advarra IRB or a real sponsor's payment protocol. Every run is governed by the Agent Fabric.

Preset scenarios

Utilization Review · MCG/InterQual analog · pre-service medical necessity

The agent that screens a proposed procedure or admission against catalog criteria — never autonomously denies, every SLA traces to catalog

The utilization-review agent runs the pre-service medical-necessity screen for a proposed procedure or inpatient admission against the catalog criteria set for that service type, classifies as approves-meets-criteria / pend-for-clinical-review / require-peer-to-peer / blocked-non-covered, and routes non-approved cases to a clinical reviewer or peer-to-peer with a catalog-sourced SLA deadline (standard 72h, urgent 24h, concurrent-review 24h). Distinct from Prior Authorization (assembly) and Claims Adjudication (post-service edits). The agent NEVER autonomously denies — every non-approved decision is DRAFTED for clinician cosign (Medicare Advantage / state UR-agent codes require notice + due-process rights). The service-type catalog, criteria sets, rules, reason codes, and SLA windows are illustrative synthetics, not MCG (Milliman Care Guidelines / Indicia), InterQual, or a real payer's UR rule set. Every run is governed by the Agent Fabric.

Preset scenarios

Provider Contracting & VBC Terms · commercial plane · no PHI

The agent that classifies provider-network contracts and computes VBC benchmarks — never autonomously commits a term change

The provider-contracting agent runs on the commercial plane (no PHI) alongside the Pipeline Management and Account Management agents. For each provider-network contract it classifies the payment model (FFS, capitation, shared-savings, bundled-payment, MA-VBC, commercial-VBC), computes the quality-gate + spend-benchmark drift for a caller- provided reporting period against a catalog methodology, and classifies as in-good-standing / benchmark-drift-review / draft-term-change / blocked-non-catalog-contract. The agent NEVER autonomously commits a contract-term change — every draft is DRAFTED for account-owner cosign (state insurance code / provider-contract law / CMS Medicare Advantage require a human owner sign-off). The contract-type catalog, methodology catalog, rules, and reason codes are illustrative synthetics, not Salesforce Health Cloud Provider Network Management, Optum Contract Manager, or a real payer's contract-lifecycle system. Every run is governed by the Agent Fabric.

Preset scenarios

Care Coordination Handoff · cross-setting SBAR (Joint Commission NPSG-2)

The agent that assembles the SBAR handoff for any cross-setting patient transition — never routes to an uncredentialed clinician, never discloses PHI without consent

The handoff agent handles any cross-setting patient transition (hospital → SNF, SNF → home, home → hospice, ED → PCP, PCP → specialist, PCP → behavioral health). For each transition it assembles the Joint-Commission-NPSG-2 SBAR (situation, background, assessment, recommendation), verifies the receiving clinician's credentialing status, and confirms transfer consent for transitions that share PHI with a new setting. Distinct from Transitions of Care (post-discharge hospital→home + med reconciliation) and Referral Management (outbound specialist referral). The agent NEVER autonomously accepts on behalf of the receiving clinician; every accepted handoff is DRAFTED for the receiving clinician's cosign. The care-setting catalog, transition-type catalog, SBAR rule set, and reason codes are illustrative synthetics, not Epic Care Everywhere, Cerner CareAware, or a real health system's handoff protocol. Every run is governed by the Agent Fabric.

Preset scenarios

Adverse Event Reporting · FDA MedWatch / VAERS analog

The agent that classifies drug ADRs / vaccine reactions / device malfunctions and drafts MedWatch or VAERS — never autonomously files to the FDA

The adverse-event agent runs a pharmacovigilance / device-safety reporting pipeline. For each reported event (drug ADR, vaccine reaction, device malfunction, medication error, therapeutic failure) it computes the 21-CFR-314.80 seriousness tier (non-serious / serious / life-threatening / death) from caller-provided outcome flags, verifies reporter identity attestation, and classifies as draft-medwatch (3500 / 3500A) / draft-vaers / blocked-non-catalog-event / blocked-reporter-unverified. All drafts route to a regulatory-team queue for cosign. The agent NEVER autonomously files to the FDA (21 CFR 314.80 mandatory reporting has sponsor / manufacturer / clinician liability), and NEVER drafts on an unverified reporter (FDA reporting requires an attested reporter). The event-type catalog, seriousness tiers, rules, and reason codes are illustrative synthetics, not FDA MedWatch, VAERS, EudraVigilance, or a real sponsor's pharmacovigilance database. Every run is governed by the Agent Fabric.

Preset scenarios

Data-Sharing / TEFCA Interoperability · HIPAA §164.506 + 45 CFR 171

The agent that classifies cross-org PHI exchanges (TEFCA / Carequality / CommonWell) — never releases non-TPO PHI without consent, never releases to an unverified participant

The data-sharing agent handles cross-organization PHI exchanges over TEFCA QHIN / Carequality / CommonWell / Direct Secure Messaging. For each request it classifies the exchange purpose (treatment / payment / operations / patient-request / public-health / research), verifies the counterparty is a Trusted Exchange Framework participant, applies the patient's data-sharing consent scopes from the Consent agent, and classifies as release-authorized / pend-purpose-verification / blocked-non-catalog-purpose / blocked-participant-unverified / blocked-consent-required-non-tpo. The agent NEVER autonomously releases PHI for a non-TPO purpose without an active consent scope (HIPAA §164.506 boundary — TPO doesn't need consent, everything else does) and NEVER releases to an unverified counterparty (45 CFR 171 / TEFCA Common Agreement). The exchange-network catalog, exchange-purpose catalog, rules, and reason codes are illustrative synthetics, not an actual TEFCA QHIN implementation, the Carequality Interoperability Framework, or a certified ONC data-sharing gateway. Every run is governed by the Agent Fabric.

Preset scenarios