[JacobStephens2]

Summary

The glossary for Weeding (#311): Architect runs started every few minutes, so that each follows the last as soon as its Architect plan is merged. Docs only; the code, the README and ADR 0009's Consequences follow in the spec.

 CONTEXT.md
 **Architect run**: skipped when
   another Architect run or a Pickup run is still running
   an earlier Architect plan is still open
+  an Architect idea is waiting for triage
+  the repository has a Ready issue (work a human shaped goes first)
-  skipped still sends the Run notification
+  skipped sends no Run notification
+**Weeding**                # the practice: no new command, ADR 0009 stands
 **Architecture review**
-  files the top recommendation labelled needs-triage
+  files it as an Architect idea, or names the open issue that covers it
+**Architect idea**         # architect-idea + needs-triage; any triage releases it
 **Run notification**
-  an Architect run's: ... or skipped

Evidence

• Before: a */5 crontab line running thirdshift architect emails on every skip, and after a no-Strong review it files another needs-triage idea on each pass that follows.
  After: the glossary defines the skips and the Architect idea that keep that line quiet and stop it at a plateau.

Merge Danger

Door: two-way

Blast Radius: glossary

Until the spec lands, CONTEXT.md describes behavior the code doesn't have yet: skipped Architect runs still send a notification, and nothing labels architect-idea.

Refs #311

🤖 Generated with Claude Code