Repository navigation
Design architect: a scheduled per-repo design function with a central potential-projects register #1351
Description
Work (Drew, 2026-10-27)
The fleet has issue creators (find improvements, file them) but no
function that originates designs — coherent multi-step project
proposals grounded in each repo's own design material, the way the
daily idea engine works for cloud projects but repo-targeted.
Build repo-design-architect (every 6h, one repo per run, rotating):
- Reads the repo's design memory first (ROADMAP, planning/, docs/,
ARCHITECTURE, TODO, open epics) + the central register — no
duplicating an existing thread. - Produces at most ONE design per run: a design doc in the goal
workspace (files/designs/), a design issue in the repo
(labels:kind/design— coined for this — plus the standard fleet
set,source/design-architect), and a row in the central register
files/potential-projects.md(name, repo, one-line summary,
status, design issue + doc links). The register is the central
potential-projects list; the design issue is the item of record,
carrying the summary and links to issues/PRs/file paths. - Files implementation issues ONLY for phases it is sure of (≤3 per
design, concrete scope + acceptance), linked as sub-issues of the
design issue and enqueued; open questions stay in the design doc. - Designs needing a Drew decision carry
user/reviewwith the
decision in one line at the top.
Acceptance criteria
- Job live; first four runs cover all four repos (or record a
justified zero-design pass with what was checked). - Register exists with its first entries; every entry's design
issue and doc resolve. - No design duplicates an open epic/roadmap thread (spot-check
the first five against the register + roadmap).
Child of epic #1334. Filed by Muse (operator) 2026-10-27.
Activity
developing-today commentedon Oct 27, 2026
CODE-452
dezren39 commentedon Nov 2, 2026
🤖 Agent note · picked up
repo-worker-code), lane7b47536b-c162-444c-be8a-3a9538cc4cb5repo-health-code-pilot(fleet-monitor safety-net packet: issue carriedqueue/queuedwith no live task)dezren39 commentedon Nov 2, 2026
🤖 Agent note · triaged — ALREADY BUILT; jobs live, no packets enqueued (would duplicate them)
repo-worker-code), lane7b47536b-c162-444c-be8a-3a9538cc4cb5, task 1335repo-health-code-pilot(fleet-monitor safety-net packet, 2026-10-27)goals/keep-the-four-repos-healthy/crons/hourly/—repo-design-architect(12h rotating: opencode/openchamber/nix) andrepo-design-architect-code(4h, code-only; split 2026-10-27). Bothenabled: true, both reference the shared instructionhidden_files/repo-design-architect-instruction.md.hidden_files/design-architect-state.md) records 5 opencode + 4 openchamber + 4 nix designs through 2026-11-02; code state (design-architect-state-code.md) records 23+ passes with per-pass agent notes, register re-verification, and candidate assessments.files/potential-projects.mdcarries 30+ rows (statuses landed / in-progress / proposed) with design-issue + doc links.source/design-architectand sub-issue links.already_done.dezren39 commentedon Nov 2, 2026
Closing as delivered: the
repo-design-architectfunction is live (rotating 12h job + code-only 4h job, both enabled since 2026-10-27), all four repos covered, central registerfiles/potential-projects.mdpopulated, design docs infiles/designs/. Evidence in the triage note above (task 1335).