Forge Status

This file is the first thing to open before a build session. Keep it short and current.

Current state

• Project phase: 0 — repository/bootstrap
• Current milestone: M0 — Foundation
• Current course lesson: Lesson 00 — Orientation and repository contract
• Code state: starter scaffold only
• Last status update: 2026-09-10

Next action

Complete Lesson 00, then begin Lesson 01. Do not implement agent integrations yet.

Current milestone goal

Create a clean repository, establish the domain/application/infrastructure boundaries, make the Go core start, make the desktop shell start, and prove a minimal generated RPC round trip before adding product behavior.

Done in this starter

• [x] Product brief and scope
• [x] Canonical vocabulary
• [x] Architecture baseline
• [x] Domain and lifecycle design
• [x] UX/design plan
• [x] Master build plan
• [x] Learn-by-building course outline and lessons
• [x] Bun-managed VitePress documentation/course site
• [x] Architecture decision records for current major decisions
• [x] Research notes from comparable agent/orchestrator repositories
• [x] Reference library
• [x] Status, risk, decision, and learning-log templates
• [x] Minimal source tree scaffold
• [x] Previous concept documents preserved under docs/archive/

Not started

• [ ] Go module and executable implementation
• [ ] SQLite migration implementation
• [ ] Generated RPC toolchain
• [ ] Task domain implementation
• [ ] Operations coordinator
• [ ] Git/worktree services
• [ ] Fake agent
• [ ] Real agent adapter
• [ ] Desktop product UI

Open product decisions

The course deliberately postpones these until evidence is available:

• Whether failed required verification blocks human approval or only warns.
• Default worktree policy for very small human-authored Tasks.
• Exact Involvement Mode presets and escalation subscription sets.
• Exact first production agent after the fake adapter (Claude Code is the current working assumption).

See OPEN_DECISIONS.md.

Status update template

When you finish a lesson, edit the fields above and add a compact entry to LEARNING_LOG.md if you learned something that should influence later design.