Which parts are deterministic and which are agentic?
Practice this questionWANT TO UNDERSTAND THE CONCEPT FIRST?Learn Which parts are deterministic and which are agentic?
| Responsibility | Approach | Why |
|---|---|---|
| Login, tenant/customer identity | Deterministic | Permissions cannot depend on a model |
| Policy ownership and active version resolution | Deterministic service lookup | Authoritative applicability must be verified |
| Exact claim status | Deterministic authorized tool | The backend is the source of truth |
| Premium/deductible calculations | Deterministic business rules | Exact numerical/business behavior |
| Policy clause retrieval | Controlled search service | Eligibility, versions, and budgets are explicit |
| Explain retrieved wording | LLM with source grounding | Useful language transformation |
| Interpret accident description | Structured model extraction | Handles varied natural language |
| Ask for missing fields/documents | Rules plus bounded agent wording | Rules know what is required; model communicates |
| Choose among safe information tools | Bounded agent/graph | Next information need may vary |
| Create/update draft | Deterministic record write from validated proposal | Draft lifecycle and concurrency need control |
| Determine required approval | Deterministic policy | Risk controls cannot be negotiated by prompt |
| Submit claim / modify policy | Authorized deterministic workflow | Exact consent, business invariants, idempotency |
| Claim denial or settlement | Authoritative rules and authorized human process | Consequential adjudication is outside casual agent authority |
| Draft email | LLM allowed | Language assistance |
| Send email | Approved recipients/content + deterministic sender | External effect and disclosure risk |
| Retention, deletion, auditing | Deterministic policies/services | Consistent data governance |
Agentic portion: interpreting wording, gathering missing information, and choosing among bounded read/search actions. Workflow portion: identity, required fields, approvals, transaction order, retries, and durable outcomes. LangGraph can coordinate the conversation; a durable business workflow coordinates a multi-day operational claim process if required. MCP is optional when several hosts reuse the tools.
Adapted from 13_AI.MD · “Which parts are deterministic and which are agentic?”. Code examples are study fragments. Difficulty and core labels are editorial estimates; version-specific behavior should be checked against your project.