From 5f5f74c01716c3c0dfed14d7a3eead5fe356096a Mon Sep 17 00:00:00 2001 From: tegwick Date: Tue, 21 Jul 2026 01:54:40 +0200 Subject: [PATCH] CUST-WP-0061-T05: retarget queue closures to WORK-RECORDS.md (generated) Convention change, not new code: closing an item now means setting its terminal status (status: closed/resolved/done + outcome where applicable) directly on the item's own yaml block in place, instead of deleting it and hand-writing a bullet in a separate "Completed"/ "Resolved decisions" log. WORK-RECORDS.md (CUST-WP-0061-T04, generated by fix-consistency's C-33) already lists every closed/resolved/done record with status/lane/source -- that supersedes the hand-maintained logs as the going-forward view. - AutopilotWorkQueue.md: closing note added; "## Completed" relabeled "(historical -- pre-canon, 2026-07-21)", frozen as-is, nothing migrated or deleted - DecisionQueue.md: closing note added -- its "## Resolved decisions" entries were already structured as in-place yaml blocks with status: resolved (ahead of AWQ's convention already), so this only clarifies the log is superseded going forward, no structural change - OfficeHourQueue.md: closing note added -- items already live under "## Queued items" with status: queued|prepared|done in place, no separate log ever existed here - OperatingRhythm.md: queue-hygiene checklist updated to describe in-place status transitions instead of "moved to the log"; added item 5 noting WORK-RECORDS.md needs no hand-maintenance Re-ran fix-consistency: WORK-RECORDS.md content unchanged (correctly idempotent -- these were prose-only edits, no yaml block content changed). Co-Authored-By: Claude Fable 5 --- AutopilotWorkQueue.md | 15 ++++++++++++++- DecisionQueue.md | 10 +++++++++- OfficeHourQueue.md | 7 +++++++ OperatingRhythm.md | 11 ++++++++--- 4 files changed, 38 insertions(+), 5 deletions(-) diff --git a/AutopilotWorkQueue.md b/AutopilotWorkQueue.md index 1980e6e..ca970de 100644 --- a/AutopilotWorkQueue.md +++ b/AutopilotWorkQueue.md @@ -2,6 +2,16 @@ > Status: live document — evergreen Green/Blue work any agent may pull when > idle. Keep ordered by leverage; never let it run empty (OperatingRhythm.md). +> +> **Closing an item (CUST-WP-0061-T05, 2026-07-21):** set `status: closed` +> and `outcome: promoted | declined | absorbed` directly on the item's own +> yaml block in place — don't delete it and hand-write a bullet below. +> `statehub fix-consistency` (C-32/C-33) registers the closure and +> regenerates `WORK-RECORDS.md`, which is the generated, always-current +> view of every closed item (id, status, lane, source) — that replaces the +> "## Completed" log below as the going-forward record. The entries already +> in "## Completed" are historical (pre-canon) and stay as prose; nothing +> there needs migrating. ## Queue @@ -44,7 +54,10 @@ Take the top item you can complete, mark it `in_progress` with your agent name, finish or return it with a note. Completed items move to the log below with a one-line outcome. -## Completed +## Completed (historical — pre-canon, 2026-07-21) + +> New closures go in the item's own block (`status: closed`) — see the +> note at the top of this file. This section is frozen history. - **AWQ-010** (2026-07-19, agt-claude-workstation): promoted to workplan **BINKY-WP-0005** (registered in hub). Integration package delivered: diff --git a/DecisionQueue.md b/DecisionQueue.md index 9eadd0b..39e6f65 100644 --- a/DecisionQueue.md +++ b/DecisionQueue.md @@ -2,7 +2,15 @@ > Status: live document — decisions awaiting the founder, as prepared > approval packages (`AutonomyPolicy.md`). Agents append; Bernd resolves. -> Resolved decisions move to the log below with outcome and date. +> +> **Resolving a decision (CUST-WP-0061-T05, 2026-07-21):** set +> `status: resolved` (plus `outcome`, `resolved_at`, `resolved_by`) directly +> on the item's own yaml block in place — don't move it to a separate log. +> `WORK-RECORDS.md` (generated by `statehub fix-consistency`) is the +> always-current view of every decision including resolved ones; that +> replaces the "## Resolved decisions" log below as the going-forward +> record. Existing log entries are historical (pre-canon) and stay as +> prose. ## Item template diff --git a/OfficeHourQueue.md b/OfficeHourQueue.md index abb756c..d5002a7 100644 --- a/OfficeHourQueue.md +++ b/OfficeHourQueue.md @@ -5,6 +5,13 @@ > ~two office-hour command days per month. Agents preload each day with a > runbook; the day is scarce strategic infrastructure — protect it from > low-leverage work. +> +> **Closing an item (CUST-WP-0061-T05, 2026-07-21):** set `status: done` +> directly on the item's own yaml block in place — it already stays under +> "## Queued items" as the historical record; no separate log to move it +> to. `WORK-RECORDS.md` (generated by `statehub fix-consistency`) is the +> always-current cross-cutting view of every engagement including done +> ones. ## Item template diff --git a/OperatingRhythm.md b/OperatingRhythm.md index 40347c6..b60bbfb 100644 --- a/OperatingRhythm.md +++ b/OperatingRhythm.md @@ -25,13 +25,18 @@ Rules: ## Queue hygiene (every agent session touching this repo) -1. `DecisionQueue.md` — resolved items moved to the log; nothing older than +1. `DecisionQueue.md` — resolved items get `status: resolved` set in place + (not moved to a separate log — CUST-WP-0061-T05); nothing older than 14 days without escalation (RISK-003 rule). 2. `OfficeHourQueue.md` — every queued item has prepared material before the - next command day; stale items pruned. + next command day; done items get `status: done` in place; stale items + pruned. 3. `AutopilotWorkQueue.md` — never empty; agents with idle capacity pull from - the top. + the top; closed items get `status: closed` in place (CUST-WP-0061-T05). 4. Workplan files match hub state (fix-consistency covers drift). +5. `WORK-RECORDS.md` (generated, all three queues above) stays current — + `statehub fix-consistency` regenerates it automatically (C-33); nothing + to hand-maintain. ## Bridge scheduler (workstation cron)