Simplify Brain dashboard to agents and workflows

.github/workflows/brain_board.yml

@@ -1,35 +1,15 @@
 name: Brain Board
 
-# Publishes the Brain's operational board — the organism's morning door — to
-# this repo's GitHub Pages URL: the page (index.html), its badge.json (the
-# cross-board headline contract the umbrella router consumes), the raw
-# board.json, and the markdown twin board.md.
-#
-# The board replaces the interactive /wake_up skill: everything that skill
-# assembled by driving doors in sequence (overnight scheduled-run sweep, the
-# Heart's readiness headline, version-stamp consistency, the community scan,
-# resume context from the Mind, the upkeep doors) is collected here on a
-# schedule and rendered with one-tap copy-for-Claude payloads. The renderer is
-# board/_board.py; its vocabulary is config/policy.yaml `board:`.
-#
-# Unlike the Mind dashboard (self-healed into the repo, because its state IS
-# the repo), nothing here is committed: the board's data is time-varying, so
-# it is served from the Pages artifact only — a daily refresh makes no commit
-# noise and can never drift against a repo copy.
-#
-# Cadence: 05:30 UTC daily — after the 02:00 nightly release driver and the
-# Heart's 05:00 heart-health refresh (which rewrites the badge this board
-# reads), before the human's morning. GitHub cron jitters 0–3 h under load,
-# so the page stamps its own generation time and every consumer should trust
-# that stamp over the schedule. workflow_dispatch is the manual refresh
-# (also what a human taps when the board says it is stale).
+# Publishes the agents/workflows directory, overnight exceptions and maintenance.
+# Generated artifacts are served from Pages; owning organs retain their evidence.
+# The daily refresh and manual dispatch collect current read-only inputs.
 
 on:
   schedule:
     - cron: "30 5 * * *"
   workflow_dispatch:
-  # A dev-box publish (`pyauto-brain board publish`, usually morning.sh's
-  # last step) pushes state/devbox_board.json to main — republish so the
+  # A dev-box publish (`pyauto-brain board publish`, an explicit local
+  # action) pushes state/devbox_board.json to main — republish so the
   # board shows this morning's local observations a minute later.
   #
   # And whenever the page's own code changes. Merging a renderer or theme

AGENTS.md

@@ -126,8 +126,8 @@ nothing has set it up — this block is what does.
 Users invoke verbs or natural language; Brain stays implicit. `/docs` and
 `/research` fix a dev work type; `/prm` merges and closes out a task; `/brain`
 is a raw passthrough. Canonical bodies are `skills/<verb>/<verb>.md`, discovered
-through thin `SKILL.md` wrappers. The morning surface is `board/`; local sync
-uses `bin/morning.sh`. `/wake_up` is the fallback when the board is unavailable.
+through thin `SKILL.md` wrappers. The agents/workflows directory is `board/`; it routes unspecified tasks and
+retains compact overnight and maintenance surfaces.
 
 Answer first, briefly; link instead of pasting. Expand plans awaiting approval,
 decision surfaces, failures/blockers and requested explanations enough to judge.

AUTONOMY.md

@@ -150,7 +150,7 @@ exception to the release cap above — not a weakening of it.
   scheme derives it, `YYYY.M.D.1`); the interactive ask is unchanged for
   manual releases.
 - The human's role on this path: the kill switch, responding to pages
-  (any stop/red/anomaly notifies), and reviewing the `/wake_up` digest of what
+  (any stop/red/anomaly notifies), and reviewing the Brain board digest of what
   shipped.
 
 Revoking the grant is one act (unset `NIGHTLY_RELEASES`) and needs no

README.md

@@ -13,13 +13,9 @@ delegates everything else: it holds no state (the Mind's job), runs no health
 checks (the Heart's), and never releases anything itself (the Hands').
 
 See the **[PyAutoBrain Dashboard](https://pyautolabs.github.io/PyAutoBrain/)**
-for the organism's morning and general starting point: what ran overnight, the
-Heart's readiness headline, who in the community is waiting on a reply, what
-to resume, and the upkeep doors — each actionable row with a one-tap 📋
-copyable agent command. Regenerated each morning; the local sync/clean leg is
-one terminal command, `bash bin/morning.sh` — or schedule it overnight on the
-dev box with `bash bin/morning_timer.sh install`, so the board is already
-fresh when you wake.
+for agents and workflows, a starting point for unspecified tasks, overnight
+exceptions and maintenance. Brain interprets intent and coordinates work;
+operational evidence stays with its owning organ.
 
 ## How PyAutoBrain works
 

agents/conductors/community/AGENTS.md

@@ -15,7 +15,7 @@
 Grown from demonstrated need: user-filed issues were handled ad-hoc (paste the
 GitHub link into an agent chat), the `start_dev_for_user` skill already owned
 the downstream dev entry, and the founding prompt asked for both a dedicated
-listening/communicating agent and a `/wake_up` summary of what the community
+listening/communicating agent and an Ears board summary of what the community
 is waiting on. Founding prompt:
 PyAutoMind `active/community_communication_agent_listen_and_respond.md`
 (issue PyAutoBrain#119).

agents/conductors/release/nightly.sh

@@ -104,7 +104,7 @@ log() { printf '== nightly: %s\n' "$*"; }
 
 # notify <emoji> <text> — one Slack message per terminal outcome (design §6).
 # A missing webhook is a loud warning, never a crash: the run's own log +
-# wake_up-digest watchdog still cover it.
+# overnight-status watchdog still cover it.
 notify() {
   local emoji="$1" text="$2"
   printf '%s %s\n' "$emoji" "$text"

bin/overnight_status.sh

@@ -79,7 +79,7 @@ if [ "$fails" -eq 0 ] && [ "$blocked" -eq 0 ]; then
     echo "Overnight: all scheduled jobs green."
 fi
 # Separate `if`s, not `[ … ] && echo`: a false test as the script's last command
-# would make it exit non-zero and read as a tool failure to /wake_up.
+# would make it exit non-zero and read as a tool failure to the Brain board.
 if [ "$fails" -gt 0 ]; then
     echo "Overnight: $fails job(s) not green — see above."
 fi

bin/pyauto-brain

@@ -111,7 +111,7 @@ AGENT_ORDER=("${CONDUCTOR_ORDER[@]}" "${FACULTY_ORDER[@]}")
 # CONDUCTOR/FACULTY orders so the generated cross-organ command-surface block
 # (install.sh --write-agents-surface) is untouched.
 AGENT_SCRIPT[board]="$BRAIN_HOME/board/board.sh"
-AGENT_DESC[board]="The operational board — render the morning surface (overnight runs, readiness, community, resume, upkeep) as md/html/json/badge; published to Pages by brain_board.yml"
+AGENT_DESC[board]="Agents and workflows, overnight exceptions and maintenance; render md/html/json/badge for Pages"
 SURFACE_ORDER=(board)
 
 cmd_help() {

bin/version_drift.sh

@@ -45,7 +45,7 @@ echo
 
 # repo:path — the coupled release-train stamps (libraries only). The Brain
 # board renders this same check on Pages (board/_board.py reads the list from
-# config/policy.yaml `board: version_stamps`) — keep the two lists in step
+# the release contract) — keep this utility independent of the Brain page
 # until this script reads that block too. The
 # charge-transfer (CTI) calibration stack is intentionally excluded: it is
 # not on the coupled train and carries its own version line. Workspaces