Two complete request walkthroughs

A. “Check claim C42.”

1. Node verifies the user and tenant.
2. A route or bounded classifier selects claim status.
3. The claim tool verifies customer ownership, reads canonical status, and returns a safe projection.
4. A template or LLM explains awaiting_documents using the returned required-document types.
5. The backend checks that the answer does not invent a payout or completion date.
6. 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.”

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