A claims process has strict, audited steps, with one model call inside it. Which orchestration fits?
Why C is the answer
AWS Step Functions with the model call as one step
Audited, fixed sequences call for deterministic orchestration. Use an agent only where the path is not known in advance.
In detail
- Strict, audited steps call for a defined workflow.
- The model is one step in it.
- Each step's execution is recorded.
Use case
An illustrative scenario, not a real incident.
An insurer must show each claim followed set steps. Step Functions fixes the order, and one state calls the model.
See it in different ways
sequenceDiagram participant S as Step Functions participant M as Foundation model participant H as Reviewer S->>M: Draft a decision M-->>S: Draft S->>H: Request approval and wait H-->>S: Approve or reject S->>S: Continue the workflow
stateDiagram-v2 [*] --> Prepare Prepare --> ModelCall ModelCall --> Decide Decide --> ModelCall: retry, within the limit Decide --> HumanReview: high value Decide --> Finish: approved HumanReview --> Finish Finish --> [*]
flowchart TD
Q{"Are the steps fixed?"}
Q -->|"Yes"| A0["Step Functions"]
Q -->|"No"| A1["An agent"]Key point: Fixed, audited flows need deterministic orchestration.
Why the other options are wrong
- A. A long prompt describing the whole process
- A prompt cannot enforce steps.
- B. A free-running agent that plans each claim
- A free-running agent cannot guarantee the order.
- D. A cron job on an EC2 instance
- A cron job has no audited state.