cleandataengineering.aiAgent Harness, drawn simply
You are here: Real flows › 15 · Two asks in one message

Agent Harness Tutorial · Real flows

Flow 15: Two asks in one message

Route: Agentic. 3 model calls · 3,381 ms · $0.00077.

Open: Entra IDEntraIDOpen: PostgreSQLPostgresstateOpen: DBOSDBOSwaitsOpen: APIM → modelAPIM→ modelOpen: Claims (MCP)ClaimsMCPTHE BOXES IT PASSEDWHAT HAPPENEDBEFORE THE MESSAGEOpen: Sign-in with Microsoft EntraSign-in with Microsoft Entrazoom in ›1Rohan signs in with MicrosoftEntra ID (code flow + PKCE); thetoken stays in the pageOpen: Page opens: load the conversationPage opens: load the conversationzoom in ›2GET /opening: the newestcheckpoint is resumed if under24 h old, else a newconversationTHE MESSAGERohan: "What's the status of claim CLM-010007, and I also have the repair estimate forCLM-010006 to send."Open: Front doorFront doorzoom in ›3body ≤ 8 KiB · token verified →PH-1001 · kill switch onOpen: Delivery ledgerDelivery ledgerzoom in ›4new row PH-1001:<delivery id>,in_flight, expires in 600 sOpen: Anything waiting?Anything waiting?zoom in ›5nothing pendingOpen: RouterRouterzoom in ›6two intents: Agentic (also runper clause) · two concerns owedOpen: Consent: what his words allowConsent: what his words allowzoom in ›7submit_document:CLM-010006TRIP 1Open: Context assemblyContext assemblyzoom in ›8Open: Pre-model checkPre-model checkzoom in ›9no_known_injection: passOpen: Model callModel callzoom in ›10790 ms · 672 in / 75 out · APIM:allow-list, rate limit, ContentSafety passOpen: Read the answerRead the answerzoom in ›11wants a toolOpen: Pre-tool checkPre-tool checkzoom in ›12passOpen: Tool callTool callzoom in ›13get_claim(CLM-010007) · 296 msOpen: Post-tool checkPost-tool checkzoom in ›14fenced ·no_instructions_in_result: passTRIP 2Open: Context assemblyContext assemblyzoom in ›15Open: Pre-model checkPre-model checkzoom in ›16no_known_injection: passOpen: Model callModel callzoom in ›17747 ms · 822 in / 87 out · APIM:allow-list, rate limit, ContentSafety passOpen: Read the answerRead the answerzoom in ›18wants a toolOpen: Pre-tool checkPre-tool checkzoom in ›19consent · passOpen: Tool callTool callzoom in ›20submit_document · 50 ms · keyrun_73de…:1:2Open: Post-tool checkPost-tool checkzoom in ›21fenced ·no_instructions_in_result: passTRIP 3Open: Context assemblyContext assemblyzoom in ›22Open: Pre-model checkPre-model checkzoom in ›23no_known_injection: passOpen: Model callModel callzoom in ›241,286 ms · 986 in / 263 out ·APIM: allow-list, rate limit,Content Safety passOpen: Read the answerRead the answerzoom in ›25words: both concerns answered,nothing owedOpen: Post-model checkPost-model checkzoom in ›267 reply rules passOpen: After-loop rulesAfter-loop ruleszoom in ›27no Tier-2 rule fires · promisegate: passOpen: Before-reply checkBefore-reply checkzoom in ›28no_promise_of_cover,no_pii_echo, money_in_rupees:passOpen: Save and settleSave and settlezoom in ›29checkpoint saved · ledger row →answeredReply: "Claim CLM-010007 – under assessment ... Repair estimate for claim CLM-010006 –successfully attached ..."
Left: the boxes this message really passed, in order; each opens its design page. Middle: the outside systems each box called, as dots on five lanes (Entra ID, PostgreSQL, DBOS, APIM in front of the model, the claims system over MCP); click a lane head to open it. Right: what happened. Grey boxes are checks, the dark box is the model, a crossed box is where something was blocked.
What it teachesEach ask is owed an answer. Had the model skipped one, the loop would have sent it back once with "Also raised and not yet dealt with".

Want every detail? The long version is in the Series: this flow with real spans and payloads.