CUST-WP-0061-T05: retarget queue closures to WORK-RECORDS.md (generated)
All checks were successful
Work Records / validate (push) Successful in 22s

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 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-07-21 01:54:40 +02:00
parent c523e0fe44
commit 5f5f74c017
4 changed files with 38 additions and 5 deletions

View file

@ -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