feat(96a): architect-bot user + directory + run script scaffold #99

New issue

Closed

opened 2026-04-01 08:39:45 +00:00 by dev-bot · 0 comments

dev-bot commented

2026-04-01 08:39:45 +00:00

Collaborator

Parent

Part of #96 — architect agent.

What to do

Set up the architect agent infrastructure (no formula logic yet):

Create Forgejo user architect-bot via API (or via disinto hire-an-agent architect-bot architect if #84 has landed)
Generate a token for architect-bot, add FORGE_ARCHITECT_TOKEN to .env.example
Create directory architect/ with:
- architect-run.sh — cron wrapper following the same pattern as planner/planner-run.sh:
  - Guards: cron lock, memory check
  - Source lib/env.sh, lib/formula-session.sh
  - Override FORGE_TOKEN with FORGE_ARCHITECT_TOKEN
  - Load formula from formulas/run-architect.toml
  - Build context: VISION.md, AGENTS.md, prerequisite tree from ops repo
  - Call agent_run or run_formula_and_monitor
- AGENTS.md — role description: "Strategic decomposition of vision issues into development sprints. Proposes sprints via PRs on the ops repo, converses with human through PR comments, files sub-issues after design forks are resolved."
Create state/.architect-active (disabled by default — empty file not created, just document it)
Create stub formulas/run-architect.toml with name, description, version, model=opus, and empty steps (filled in by follow-up issues)
Create sprints/ directory in ops repo with a .gitkeep
Update root AGENTS.md — add architect row to agent table
Add cron entry suggestion in comments (every 6 hours)

Affected files

architect/architect-run.sh (new)
architect/AGENTS.md (new)
formulas/run-architect.toml (new — stub)
AGENTS.md (update — add row)
.env.example (update — add FORGE_ARCHITECT_TOKEN)

Acceptance criteria

architect-bot user exists on Forgejo
architect/architect-run.sh runs without error (exits cleanly with stub formula)
formulas/run-architect.toml exists with correct metadata
ops/sprints/ directory exists
AGENTS.md has architect row
CI green

Dependencies

None — first step.

## Parent Part of #96 — architect agent. ## What to do Set up the architect agent infrastructure (no formula logic yet): 1. Create Forgejo user `architect-bot` via API (or via `disinto hire-an-agent architect-bot architect` if #84 has landed) 2. Generate a token for architect-bot, add `FORGE_ARCHITECT_TOKEN` to `.env.example` 3. Create directory `architect/` with: - `architect-run.sh` — cron wrapper following the same pattern as `planner/planner-run.sh`: - Guards: cron lock, memory check - Source lib/env.sh, lib/formula-session.sh - Override FORGE_TOKEN with FORGE_ARCHITECT_TOKEN - Load formula from `formulas/run-architect.toml` - Build context: VISION.md, AGENTS.md, prerequisite tree from ops repo - Call `agent_run` or `run_formula_and_monitor` - `AGENTS.md` — role description: "Strategic decomposition of vision issues into development sprints. Proposes sprints via PRs on the ops repo, converses with human through PR comments, files sub-issues after design forks are resolved." 4. Create `state/.architect-active` (disabled by default — empty file not created, just document it) 5. Create stub `formulas/run-architect.toml` with name, description, version, model=opus, and empty steps (filled in by follow-up issues) 6. Create `sprints/` directory in ops repo with a `.gitkeep` 7. Update root `AGENTS.md` — add architect row to agent table 8. Add cron entry suggestion in comments (every 6 hours) ## Affected files - `architect/architect-run.sh` (new) - `architect/AGENTS.md` (new) - `formulas/run-architect.toml` (new — stub) - `AGENTS.md` (update — add row) - `.env.example` (update — add FORGE_ARCHITECT_TOKEN) ## Acceptance criteria - [ ] architect-bot user exists on Forgejo - [ ] `architect/architect-run.sh` runs without error (exits cleanly with stub formula) - [ ] `formulas/run-architect.toml` exists with correct metadata - [ ] `ops/sprints/` directory exists - [ ] AGENTS.md has architect row - [ ] CI green ## Dependencies None — first step.