--- type: resource-overload coverage: 59 source: COMPLAINT_REGISTRY.jsonl via taxonomy.json _meta (2026-08-08) absorbs: [cpu-load, memory-load, disk-io-load, runaway-process, disk-cache-fatigue] --- # KB — resource-overload audience: AI coding agents first. Type-level patterns from complaint registry; individual resolved incidents append as `kb/.md` in later phase. ## Coverage 59 records. Largest machine-takeover cluster. Sub-counts from registry (207-row snapshot): `cpu-load` 36, `disk-io-load` 7, `memory-load` 5, `runaway-process` 5; remainder `disk-cache-fatigue` + concurrency saturation. One untyped record (C217) is overload-shaped but unmapped by category field. ## Recurring failure patterns 1. **Laptop as compute node** — harness/factory/cursor/codex seats run locally; load 9+ with multiple `confine-*` scopes; npm installs at 120–200% CPU. 2. **Kill visible agent, daemon respawns** — user lacks inventory/kill switch; scope survives process death. 3. **Admission queue saturation** — parallel dispatches without cgroup ceiling; fork storms from unbounded concurrency. 4. **Disk cache / IO thrash** — build artifacts + browser caches on same disk as desktop; iowait freezes UI before CPU maxes. 5. **Misdiagnosis by process name** — `pkill` hits wrong tree or owner session; fix is cgroup-scoped stop (`deckctl agents stop`). ## Fix vectors that worked - Route headless compute to buildbox (`seat-remote`, `e2e-remote`, admission queue). - `deckctl agents list` → stop hot scope by run/seat id. - Execution-plane insulation: local spawn deny exit 97; laptop terminal only. ## Related skill `od-overload`