Overview
scripts/board.py carries a hard-coded BOARD_FAMILY tuple listing five sibling boards in an ad-hoc order. It predates PyAutoCortex, so the Memory board's footer has no Cortex chip, and its chip order does not match the ruled organ order the rest of the family renders.
The canonical list already lives in PyAutoBrain/config/policy.yaml under board: boards: (brain, mind, cortex, memory, heart, hands, organism), and this renderer already imports the shared theme from PyAutoBrain/board/_theme.py via its theme() locator — the CI job here already checks PyAutoBrain out beside the repo.
Plan
- Replace
BOARD_FAMILY with the theme's new board_links(base, current) helper, keeping the base URL derivation this file already does (the snapshot owner).
- Keep the old tuple as a fallback for an older PyAutoBrain checkout without
board_links.
- Update the board tests to assert the footer carries Cortex and the canonical chip order.
Library-first / branch dependency: depends on PyAutoBrain#352 (feature/board-family-helper), which adds _theme.board_links. CI here may only go green once that PR has merged; until then the fallback path is what runs.
Detailed implementation plan
Affected Repositories
- PyAutoMemory (primary)
- PyAutoBrain (upstream helper — separate PR)
Branch Survey
| Repository |
Current Branch |
Dirty? |
| ./PyAutoMemory |
main |
clean |
Suggested branch: feature/memory-board-family-footer
Implementation Steps
scripts/board.py — replace the BOARD_FAMILY tuple + nav builder with a call to theme().board_links(base, BOARD_KEY), falling back to the legacy tuple when the helper is absent.
tests/test_board.py — assert the rendered <ul class="boards"> carries a Cortex chip and the canonical chip order.
Key Files
scripts/board.py — the board renderer
tests/test_board.py — the board's tests
Original Prompt
Click to expand starting prompt
See the matching PyAutoMind prompt under active/.
🤖 Generated with Claude Code
https://claude.ai/code/session_01GnXNPigN6qWxLZy2cqhDBX
Overview
scripts/board.pycarries a hard-codedBOARD_FAMILYtuple listing five sibling boards in an ad-hoc order. It predates PyAutoCortex, so the Memory board's footer has no Cortex chip, and its chip order does not match the ruled organ order the rest of the family renders.The canonical list already lives in
PyAutoBrain/config/policy.yamlunderboard: boards:(brain, mind, cortex, memory, heart, hands, organism), and this renderer already imports the shared theme fromPyAutoBrain/board/_theme.pyvia itstheme()locator — the CI job here already checks PyAutoBrain out beside the repo.Plan
BOARD_FAMILYwith the theme's newboard_links(base, current)helper, keeping the base URL derivation this file already does (the snapshot owner).board_links.Library-first / branch dependency: depends on PyAutoBrain#352 (
feature/board-family-helper), which adds_theme.board_links. CI here may only go green once that PR has merged; until then the fallback path is what runs.Detailed implementation plan
Affected Repositories
Branch Survey
Suggested branch:
feature/memory-board-family-footerImplementation Steps
scripts/board.py— replace theBOARD_FAMILYtuple + nav builder with a call totheme().board_links(base, BOARD_KEY), falling back to the legacy tuple when the helper is absent.tests/test_board.py— assert the rendered<ul class="boards">carries a Cortex chip and the canonical chip order.Key Files
scripts/board.py— the board renderertests/test_board.py— the board's testsOriginal Prompt
Click to expand starting prompt
See the matching PyAutoMind prompt under
active/.🤖 Generated with Claude Code
https://claude.ai/code/session_01GnXNPigN6qWxLZy2cqhDBX