From 11b1f62eac8df170203562d1f73c493253ad4542 Mon Sep 17 00:00:00 2001 From: Jammy2211 Date: Thu, 3 Sep 2026 10:32:37 -0400 Subject: [PATCH] mind: dashboard refresh on batches/**; the dev batch stays collected-once, reviewed-once (#341) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The dashboard now carries the batch status box, so a push that opens, collects or reviews a batch makes the page stale: `dashboard_refresh.yml` triggers on `batches/**` (the Cortex workflow already does). `batches/AGENTS.md` records that the dev rule is unchanged — one sitting, button on `collected:` — and that the rolling board is the Cortex's. Pairs with PyAutoLabs/PyAutoBrain PR https://github.com/PyAutoLabs/PyAutoBrain/pull/342 and PyAutoLabs/PyAutoCortex#7; merges last. Cites PyAutoLabs/PyAutoBrain#341. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01SgtS7NhqeziqgxKfSiMzRL --- .github/workflows/dashboard_refresh.yml | 7 +++++-- batches/AGENTS.md | 9 +++++++++ 2 files changed, 14 insertions(+), 2 deletions(-) diff --git a/.github/workflows/dashboard_refresh.yml b/.github/workflows/dashboard_refresh.yml index 18bc9b0b9..f791de757 100644 --- a/.github/workflows/dashboard_refresh.yml +++ b/.github/workflows/dashboard_refresh.yml @@ -2,8 +2,9 @@ name: Dashboard Refresh # Keeps the generated task page (`dashboard.md`, linked from the README) in # step with the Mind it describes. The page is rendered by PyAutoBrain's intake -# conductor from `draft/`, `active/` and the registry files, so any push that -# files, issues, parks or ships a task makes it stale. +# conductor from `draft/`, `active/`, `batches/` and the registry files, so any +# push that files, issues, parks or ships a task — or opens, collects or +# reviews a batch, which the page's status box shows — makes it stale. # # It went stale before this workflow existed: between its first commit and # 2026-08-11 the page was regenerated by hand 4 times while 33 commits touched @@ -31,6 +32,7 @@ on: paths: - "draft/**" - "active/**" + - "batches/**" - "active.md" - "parked.md" - "planned.md" @@ -45,6 +47,7 @@ on: paths: - "draft/**" - "active/**" + - "batches/**" - "active.md" - "parked.md" - "planned.md" diff --git a/batches/AGENTS.md b/batches/AGENTS.md index 583b1fcd6..ae9d200c9 100644 --- a/batches/AGENTS.md +++ b/batches/AGENTS.md @@ -9,6 +9,15 @@ It auto-merges (`scripts/ledger_merge.py` — `batches/` is a ledger dir), becau an unattended system that cannot record its own history unattended will not record it. +**Collected once, reviewed once.** A dev batch is dispatched as one shift and +reviewed as one sitting: one `- review:` line, one review file. The dashboard's +batch status box is the live view of the open slot — every member with what it +is doing — and it offers the button to the review packet once `collected:` is +stamped, because there is nothing to review before that. A science batch is a +rolling board instead, ruled on more than once and closing only when nothing is +left on the board (`PyAutoCortex/batches/AGENTS.md`, "A rolling board, not a +dispatch"); that difference is the Cortex's, not a change here. + ## Schema ```markdown