Concurrent Agent Loop

Treats concurrent sessions as OS threads sharing a common event bus and memory address space. Every cycle includes execution, independent peer evaluation, friction tracking, self-assessment surveys, post-run metrics, and memory persistence.

When to Use This Pattern

Use when:

• Coordinating continuous improvement across multiple concurrent agent sessions.
• Evaluating and improving multiple skills, workflows, or templates in parallel.
• You need every cycle to generate measurable accuracy gains and persistent memory.

Do NOT use for:

• Single-session procedural tasks (use os-eval-runner directly).
• Signal-only coordination with no evaluation, survey, or memory steps.