[JacobStephens2]

Summary

Glossary only, for the Spec in #237 (nightly Architect runs). It describes behaviour the Tickets #246 to #249 will build, as #235 did for #27.

 CONTEXT.md
   Base branch
+    an Architect run's command can name it, whatever is checked out
   Architect run
-    ... a Spec run on the Spec it published, or a Run on its standalone Ticket
+    ... a Spec run or a Run on the Architect plan it published
+    skipped when another Architect run on the repository is still running
+      on the machine, or an earlier Architect plan is still open
+    skipped is not a failure, and still sends the Run notification
   Architecture review
-    publishes the top recommendation as the plan
+    publishes the top recommendation as the Architect plan
+  Architect plan   (new)
+    the Spec, or standalone Ticket, an Architecture review published
+    labelled `architect-plan` by thirdshift; open until merged or closed
+    never retried by a later Architect run
+    Avoid: plan, plan doc

Evidence

• Before: CONTEXT.md calls it "the plan", lowercase and undefined, and says nothing about two Architect runs at once.
  After: Architect plan is a defined term, and Architect run says when it is skipped.

No code or generated file changes, so no test run applies.

Merge Danger

Door: two-way

A revert restores the old wording.

Blast Radius: docs

Until #246 to #249 land, the glossary describes base <branch>, the skipped outcome and the architect-plan label before thirdshift does them. Agents working on #27's remaining Ticket read this file.

🤖 Generated with Claude Code