--- name: robco-phase6-backlog description: "BLOCKED — a gated end-of-queue task batch whose spec document can no longer be located. Kept for the owner's standing instruction about how deferred batches are to be handled." metadata: node_type: memory type: project originSessionId: 0b7c5f41-bb34-4ab4-93be-fdb363f5eb40 --- # ⛔ BLOCKED — the spec cannot be found Owner (2026-06-27) pasted a multi-task implementation batch and asked for it to be held until the end of the queue. The full verbatim spec was recorded in a separate document, and **that path no longer resolves — the directory it referred to does not exist.** The summary that used to live in this file was a paraphrase, not the spec. **Therefore: this batch cannot be actioned. Do not attempt to reconstruct it from memory, and do not invent its contents.** The only valid next step is to locate the original spec document (or ask the owner to re-supply it). Until then there is nothing to run. *Correction 2026-07-20: removed the paraphrased task list and the folded-in secondary menu. Both described work whose authoritative spec is missing, and a paraphrase of a lost spec is worse than no spec — it reads as actionable when it isn't. Live queue state is `QUEUE.md`.* ## ⭐ The standing instruction — verbatim, and it outlives this batch Owner (2026-06-27): *"fold them all together, add this with them, save all of this until after all queued tasks. don't start immediately after, remind me instead."* This is how he wants **deferred work handled in general**, not just this batch. Three separate instructions, all load-bearing: - **Fold, don't fragment** — related deferred items get consolidated into one batch rather than scattered. - **It waits for the queue to fully drain** — a held batch does not get slipped in early. - **When the queue drains, REMIND AND WAIT. Do not auto-start.** **Note the interaction with [[dispatch-autonomy-preference]]:** that file says do not ask permission to keep the chain turning. This is not a contradiction — it is the named exception. Auto-advance applies to *the queue*; an explicitly gated batch sitting behind the queue is a new direction, and new directions still require his go-ahead. Reminding him here is not rubber-stamping the machine. ## One other preference recorded here For this batch the owner **pre-authorized a version bump at Dispatch's discretion**, overriding the normal rule of always asking first. That authorization was scoped to this batch only and does not generalize. See [[robco-audit-program]].