LESSON 158 / 215·2 min readAdvanced

Two complete request walkthroughs

Must knowConcept lesson

Words made simple

A few useful meanings before you read the explanation.

LLM: A model trained to work with language. It can write or summarize text, but its answer still needs checking against reliable information.
RAG: Find relevant information first, then give it to a model to help answer the question. The answer is only as reliable as the information and checks used.
Deterministic: Following steps or rules defined by code. The model does not decide which step should run next in a deterministic workflow.

More words from this lesson

Authorization: Checking what that identity is allowed to read or do. Being logged in does not grant access to every record.
Tenant: A customer or organization whose data must stay separate from other customers in a shared application.
Trace: A linked record of the steps in one request, including model calls, retrieval and tools. It helps locate delays or failures.

A. “Check claim C42.”

Node verifies the user and tenant.
A route or bounded classifier selects claim status.
The claim tool verifies customer ownership, reads canonical status, and returns a safe projection.
A template or LLM explains awaiting_documents using the returned required-document types.
The backend checks that the answer does not invent a payout or completion date.
The UI receives safe text and the verified status. The trace records lookup outcome and usage.

No RAG is required to read live status. If the user asks why a document is required, retrieve the applicable instructions separately and cite them.

B. “File a claim for yesterday's accident.”

Verify policy ownership and obtain the current product-specific intake rules.
Use extraction to propose date, location, description, and claim type; clarify missing or ambiguous values.
Upload and securely process supporting documents; preserve originals and field evidence.
Validate the draft with deterministic calendar/product/business rules.
Store an immutable draft version and render exact details for customer review.
Record approval against that draft's hash; corrections invalidate it.
Start a deduplicated submission operation. Revalidate current permissions and rules at commit time.
Claim service creates one canonical claim and records its receipt. Publish notifications through an outbox.
If a timeout leaves outcome unknown, reconcile by operation key before retrying.
Explain only the verified receipt/status. Review/adjudication remains in the authorized claims process.

PAUSE & RECALL