Checked August 2026
Loop engineering foundry
Design the system that keeps prompting the agent
Loop engineering moves the design problem above a single prompt. It specifies how an agent observes state, decides, acts, inspects the result, records evidence, recovers, verifies, and stops across repeated model calls.
Compare ReAct, plan-and-replan, evaluator-optimizer, capped retry, human approval, and checkpointed-worker patterns across research, coding, support, and structured-extraction scenarios. Inject a failure, lower a budget, or deny approval and inspect the exact terminal state instead of accepting a false claim of completion.
- Manipulate
- Pattern · scenario · failure · approval · budgets
- Observe
- State graph · ledger · calls · retries · checkpoints
- Terminal states
- Proven done · partial · awaiting approval · exhausted · failed closed
Verify six upcoming conference dates and create a sourced briefing.
Done conditionEvery date and location resolves to an official organizer page.
Required artifact: Conference evidence table.
Required artifact: Conference evidence table.
M 1 · T 0 · R 0Primary research
Inspect the mechanism at its source.
Project architecture and terminology were checked against official documentation on August 10, 2026. Research papers are linked to their original publication records.