Skip to content

feat: use functional task labels in organ banners #513

Description

@Jammy2211

Overview

Replace generic grey banner labels with each organ's function. Preserve logos, software names, taglines and styling. Move Broca immediately after Nerves in the shared dashboard navigation.

Plan

  • Use the approved functional labels in every shared organ banner.
  • Move Broca after Nerves while preserving other navigation ordering.
  • Verify banner appearance and consumer regeneration requirements.
  • Tier: judge — merge mode: human /prm.
Detailed implementation plan

Affected Repositories

  • PyAutoBrain (primary; library workflow)

Branch Survey

Repository Current Branch Dirty?
organs/PyAutoBrain main clean

Suggested branch: feature/organ-banner-task-labels.
No worktree created: Brain is claimed by board-one-click-update (#504).

Implementation Steps

  1. Add functional labels to board/_theme.py::ORGANS; use them in hero while accepting the legacy kind argument.
  2. In config/policy.yaml → board.boards, move Broca immediately after Nerves; retain all other entries' relative order.
  3. Update docs/board-navigation.md with the label contract.
  4. Verify all approved labels; compare hero output to confirm only grey label text changes; inspect mobile and desktop rendering. Check navigation order.
  5. Identify consumer regeneration/publication requirements and report actual deployment evidence separately from source completion.

Approved labels: Brain: Orchestration; Mind: Planning; Cortex: Science; Memory: Knowledge; Eyes: Visualization; Ears: Community; Heart: Tests; Hands: Releases; Pulse: Profiling; Insight: Inference; DNA: Environments; Nerves: Configuration; Broca: Assistants; Gut: Cleanup; Scientist: Overview.

Approval and gates

The human approved the corrected plan with “continue” on 2026-10-08. Heart entry verdict was STALE. The repository claim remains a hard conflict; queue until resolved. Do not modify the existing task or its worktree without authorization.

Original Prompt

Starting prompt and user correction

Organ banner task labels

Consequence: judge

Original request

For the dashboards, I want to update the banner images at the top, but I only want to update thw words in grey and not the logo, software name or words underneath. I like that each word describes what task it does (e.g. Insight -> Inference), Ears -> Community, the only problem is I dont want words like "Board", "Dasdboard", and I dont want it to just be "Dashboard" like it is on many (e.g. Cortex). The word should be what the organ does (So for Cortex -> Science).

Scope and proposed plan

@PyAutoBrain owns the shared HTML banner in board/_theme.py::hero. Change only its grey kind label to an organ-specific functional label. Preserve SVG marks, wordmarks, taglines, colours and layout. Existing renderer calls remain compatible. Move Broca immediately after Nerves in the shared dashboard navigation, using config/policy.yaml → board.boards; preserve other entries' relative order.

Approved labels: Brain: Orchestration; Mind: Planning; Cortex: Science; Memory: Knowledge; Eyes: Visualization; Ears: Community; Heart: Tests; Hands: Releases; Pulse: Profiling; Insight: Inference; DNA: Environments; Nerves: Configuration; Broca: Assistants; Gut: Cleanup; Scientist: Overview.

User correction (verbatim):

Broca should be Assistants and also move it after Nerves, Heart should be Tests

Add a functional label to the existing organ metadata and use it for the banner label, retaining the legacy kind argument for consumer compatibility. Update the banner contract in docs/board-navigation.md. Verify representative hero output differs only in the label and visually inspect long labels at mobile and desktop sizes. Identify consumer regeneration/publication requirements before claiming live deployment.

Branch proposed: feature/organ-banner-task-labels. Library workflow for the shared Brain implementation. Tier: judge; merge mode: human /prm.

Planning state

No source edited. User approved the corrected plan and label mapping with “continue” on 2026-10-08. Brain is currently claimed by board-one-click-update (PyAutoBrain issue #504); worktree_check_conflict reports a hard conflict. Do not create a competing implementation worktree until the claim is resolved. Heart entry verdict: STALE (release STALE; monitoring RED); planning permitted by start_dev.

Activity

  1. Jammy2211 commented on Oct 8, 2026

    @Jammy2211
    ContributorAuthor

    Implementation is ready in PR #514 at 79e3a55. All 1,252 Brain tests passed; tenant firewall and browser checks passed. Direct comparison of all 15 banners confirms only the grey label changes; logos, software names, taglines and CSS remain unchanged. Broca now follows Nerves in navigation.

    The human authorized parking #504, merging and publication, and explicitly acknowledged the exact Heart YELLOW warning set. Waiting for GitHub checks, then regenerate and verify all 15 public dashboards before close-out.

  2. Jammy2211 commented on Oct 8, 2026

    @Jammy2211
    ContributorAuthor

    Shipped and live in PR #514 (merge e20e0b0).

    All 15 published dashboards were checked directly: approved grey labels are present, logos/software names/taglines are unchanged, and shared navigation places Broca after Nerves. Ears completed the final deployment successfully: https://github.com/PyAutoLabs/PyAutoEars/actions/runs/37835473692

    Validation: 1,252 local tests passed; Python 3.12 and 3.13 CI jobs and docs build passed; tenant firewall passed; browser label-fit checks at five widths passed. The human acknowledged the exact Heart YELLOW warning set and authorized merge/publication. No scientific workspace API changes.

    Task #504 remains parked with its worktree and uncommitted prototype preserved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions