Agent Architecture and Orchestration

Agent Architecture and Orchestration

Loop Engineering — References

Loop engineering › References

76 of 77 in this book · 1 min read

Reviewed 2026-10-13. Separate conceptual motivation from implementation guarantees.

  • Loop Engineering — Addy Osmani. The practitioner framing of a system that finds, assigns, checks, and remembers work across agent runs. It is broader than the model/tool cycle inside one run.
  • Own the Outer Loop — Addy Osmani. Human judgment over the surrounding process and acceptance policy as execution becomes automated.
  • Schedule — Temporal. Named schedules, overlap policies, catchup windows, pausing, and backfill; these dispatch controls do not prove business completion.
  • Events that trigger workflows — GitHub. Event and scheduled workflow behavior, including constraints relevant to timely dispatch.
  • Effective harnesses for long-running agents — Anthropic. Persistent progress and verified incremental work as a concrete cross-session example.

The incident-triage controller in this capability is a proposed design combining durable work tracking and verification. It is not an implementation supplied by these sources.