QUEUE.md: one task table; CURRENT and DEFERRED point at it

Jason could not find what is next without reading the prose plans. QUEUE.md is one row per piece with owner, issue, state, gate and brief location. CURRENT.md becomes the narrative log; DEFERRED.md keeps only gaps. Co-Authored-By: Claude Fable 5.1 <[email protected]>
2026-09-12 19:33:59 -05:00
parent 355b4308c3
commit 7c8e530add
3 changed files with 63 additions and 9 deletions
@@ -1,6 +1,11 @@
-# CURRENT — single source of "what happens next"
+# CURRENT — narrative log of the work in flight

-This file always names exactly one next action. Any "continue" / "next" /
+The task list is `docs/plans/QUEUE.md`: one table, one row per piece, with
+owner, state and gate. Read that first; it says what is next for you. This
+file holds the narrative behind the rows and the completed log, and it does
+not always name one action any more. If the two disagree, QUEUE.md wins.
+
+This file historically named exactly one next action. Any "continue" / "next" /
 "proceed" message means: execute the action below, fully (implement → test →
 verify against its acceptance criteria → commit → push → close the issue →
 update this file to the next action). No ambiguity, no re-planning.