garbage-collectionlisted

# Garbage Collection Garbage collection in a harness context means periodic checks that fight entropy — the slow drift that neither real-time hooks nor PR gates catch. Documentation goes stale, conventions erode, dead code accumulates, dependencies fall behind. This is Boeckeler's third harness component: agents that run periodically to find inconsistencies and violations, actively fighting decay. ## Anatomy of a GC Rule Every GC rule in HARNESS.md has five fields: - **What it checks** — the specific entropy being detected - **Frequency** — `daily`, `weekly`, or `manual` - **Enforcement** — `deterministic` or `agent` - **Tool** — what runs the check - **Auto-fix** — `true` (GC agent fixes it) or `false` (create an issue instead) ## Choosing Frequency | Frequency | Use for | | --- | --- | | daily | Fast checks with high entropy rate (style drift in active codebases) | | weekly | Most GC rules — documentation, dependencies, dead code | | manual | Exploratory checks not yet calibrated for automation | Start with weekly for most rules. Only move to daily if the entropy rate justifies the cost. ## The Auto-Fix Decision Auto-fix is safe when the fix is deterministic, local, verifiable, and reversible. It is not safe when the fix requires judgement, has ripple effects, cannot be verified, or is destructive. For the full safety rubric and detailed examples, consult `references/gc-catalogue.md`. **When auto-fix is true**: The `harness-gc` agent applies the fix directly (