os-improvement-looplisted

Pattern 5: Concurrent Event-Driven Multi-Agent Loop. Coordinates multiple Claude sessions as OS threads sharing a common event bus and memory address space. Every loop cycle is a full improvement cycle: execute, eval against benchmark (KEEP/DISCARD), emit friction events during work, close with post_run_metrics, agent self-assessment survey saved to retrospectives, memory persistence, and Triple-Loop Retrospective trigger if friction threshold crossed. Four coordination topologies: turn-signal, fan-out, request-reply, triple-loop (Pattern D).
richfrem/agent-plugins-skills · ★ 3 · AI & Automation · score 65

Install: claude install-skill richfrem/agent-plugins-skills

# Concurrent Agent Loop > Pattern 5 in the agent-loops taxonomy. Treats concurrent Claude sessions as OS threads > sharing a filesystem address space. The kernel event bus coordinates signals. Every cycle > includes real work, eval against benchmark, friction tracking, agent self-assessment survey, > post-run metrics, and memory persistence. The OS learns from every run. --- ## Triple-Loop Architecture There are **two distinct Triple-Loop orchestration cycles** operating at different scopes. Do not conflate them. ``` ┌─────────────────────────────────────────────────────────┐ │ TRIPLE-LOOP ARCHITECT — OS Self-Improvement (this skill) │ │ │ │ os-improvement-loop evaluates and improves the OS │ │ workflows, protocols, agent coordination patterns, │ │ and this SKILL.md itself. │ │ │ │ Target: the OS machinery — ledgers, surveys, kernel, │ │ event bus, loop protocol. │ │ Eval gate: ORCHESTRATOR + PEER_AGENT run eval_runner.py │ │ on the OS skill being patched. │ │ Self-improvement: ORCHESTRATOR updates this SKILL.md │ │ when a confirmed protocol fix is found. │ └────────────────────┬────────────────────────────────────┘ │ spawns / governs ┌────────────────────▼────────────────────────────────────┐ │ TRIPLE-LOO