RONANRX
RonanRx · System Wireframes

Agentic Intake Flow, v0.2

agentic specialists · deterministic plumbing · tiered output
The loop

1. The care loop, one thread one record

A patient texts in once and never leaves the thread. Every leg writes to one longitudinal record (the dark hub), and that closed loop is the moat. Stations are colored by what is real software, synthetic, or a disclosed human concierge step (Plan B walkthrough).

One patient recordevery leg writes herePatient entrywebsite CTATransportLinq, guardedIntakescripted, then AIDoctor approvalfail-closed gateE-prescribehand-key BestRxCompound + ship503A fulfillmentDeliveredmanual markFollow-up + triagerules engineREAL softwareSYNTHETIC, guardedCONCIERGE, human seamthe agentic intake v0.2 plan is the AI version of the Intake station
Flow

2. End to end (synchronous reply)

A patient burst is coalesced at the edge, routed deterministically, answered by agentic specialists, assembled, guarded, and sent as one reply.

Patient1..N SMS burst01Edge batcherHMAC, coalesce02Turn pointer/sms/turn, no PHI03Coordinatordeterministic route04Specialistsagentic fan-out05Stitchassemble directive06Send guardtier-aware07SMS replyone message08the dashed return: each reply can begin the next turn, a fresh batch
Fan-out

3. Agentic specialist fan-out

The deterministic coordinator never sees PHI. It fans out to five agentic specialists, each an LLM reasoning over deterministic tools.

Coordinatordeterministic, no PHIIntake9 fieldsBAADoctor routingcontext.dev, NPPESVial-photolabel OCRBAAOrderSureScriptsBAAReminderconsent-gatedeach specialist: LLM reasoning + multi-step tool-calling over deterministic toolsTier-3 containment: no approve_prescription, charge_card, set_triage_color, auto-doctor-select
Planes

4. Three planes, one PHI invariant

Routing is PHI-free, specialists carry PHI under BAA + ZDR, and the outbound surface is tiered with the guard as the final word.

ROUTING PLANEPHI-free pointerchat_id, message_ids, capability, idempotency key. Schema rejects free text.SPECIALIST PLANEPHI on BAA + ZDRAgentic specialists + deterministic tools. In-VPC, no third-party egress, no provider-side PHI logging.OUTBOUND PLANEtiered, guard is the final wordRegulated: template-locked, byte-exact. Benign: guarded prose (classifier + LLM-judge), behind G4.
Async

5. Async researcher pipe

A parallel pipe, not in the sync path: a data event drives research, a doctor signs off, then the CLI guard sends.

Data eventlab, biometricAI Researcher~12M papersFindingcitedQA reviewresearch qualityCLI guardpp-linqPatient SMSon approvalASYNC PIPEhours to days, parallel: NOT in the synchronous reply pathQA sign-off (research quality) is required before any patient-facing SMS
Tools

6. The deterministic tool plane

Agentic specialists orchestrate three operator CLIs: linq-pp-cli (send guard, capability, webhooks, consent), context.dev (doctor discovery), and llamaparse (research ETL). Each is a tool, not an agent.

Agentic specialistsorchestrate det. toolslinq-pp-clisend-guard, capability, webhooksconsent, flag-for-humancontext-dev-pp-clidoctor-discovername + city only, no patient idNPPESprovider verifypublic, no BAAllamaparse-pp-cliPDF to markdown corpusfeeds rrx-n50 research ETLeach CLI ships agent-context (schema v4) + a which resolver, so agents bootstrap off the contract, not --help. context.dev + llamaparse default to third-party egress, so both are G1-gated.
Guard

7. The send guard, fail-closed

Every send passes a fail-closed AND-gate. The first four checks already exist in linq-pp-cli send-preflight; the tier classifier and template re-render are the P2-c/P2-d amendment.

chat_idpresentinboundevidence/consentopt_outclearphi_payloadpointer-onlytierclassify rendered+P2-drendertemplate + Cat-2+P2-cSENDone replyTHE SEND GUARD, FAIL-CLOSEDchecks 1-4 already exist in linq-pp-cli send-preflight; tier + render are the P2-c/P2-d amendmentany check fails -> template-lock or flag_for_human. one hashed manifest feeds both the edge JS guard and the pp-linq CLI binary.
Research

8. Research ETL, PDF to cited finding

Papers are parsed by llamaparse into markdown, chunked and embedded (the gap P5-a fills), retrieved by the researcher, signed off by a doctor, and delivered through the same guard.

Corpus source~12M papersllamaparsePDF to markdownMarkdown + indexprovenance, resumeChunk + embedthe gap, P5-aGAPVector indexretrieval storeResearchercited findingQA reviewresearch qualityCLI guard to SMSon approvalRESEARCH ETL, async and off the sync pathstep zero: source the corpus (no papers on disk yet). papers-only is BAA-exempt; patient data is BAA-gated.