os-improvement-looplisted

# 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. --- ## Key Invariants - **No-Rollback Rule**: Never manually roll back changes during a cycle unless `evaluate.py` registers an explicit accuracy regression. - **Eval Gate Mandatory**: Every modification must pass the independent evaluation gate (`evaluate.py` exit code 0). No manual bypasses. - **NEVER STOP Discipline**: Do not abort a running loop due to minor/moderate errors. Complete the loop close checklist and log unresolved issues as Map Debt. - **Outer Loop Ownership**: The outer loop owns session lifecycle. Inner loop tasks (`os-eval-runner`) must not prematurely close a session without running Stage 4 (memory promotion and survey collection). --- ## Stage Pointers & Reference Protocols The execution details are split across modular references: - [Stage 0: Setup