roastpilot-plan

Program repository for RoastPilot — agreed plans, decision records, cross-repo epics, and UI prototypes for the deterministic coffee-roasting agent rebuild.

Layout

Path	What
00-repository-structure.md	Repository structure decision record (D1–D4), milestones, verified ground truth
roastpilot-agent-orchestration-plan.md	Authoritative architecture plan: controller, state machine, safety policy, advisor (its repo-structure section is superseded — banner inside)
roastpilot-agent/	Agent harness component plan (M1, D5–D9, epics E1–E12), UI prompt pack, Figma Make prototypes + frozen screenshots
roastpilot-cloud/	Cloud data plane component plan (M2 / Loop A, D10–D13, epics C1–C7)
cloud-sync-plan.md	LA-1/LA-2 cloud sync product contract and ordered delivery plan (D220); home epics E15/C9
coffee-roaster-mcp/	Small Loop A contract change spec (FC override source marker)
coffee-first-crack-detection/	No-change note + Loop B backlog appendix
archive/	Superseded draft-era documents (kept for history; see its README)

Related repositories

• coffee-roaster-mcp — hardware/session MCP boundary (exists, PyPI + MCP Registry)
• roastpilot-agent — deterministic agent harness + device SPA (M1)
• roastpilot-cloud — roast sharing, tasting feedback, reference summaries (M2)
• coffee-first-crack-detection — ML pipeline (exists, Hugging Face)

Epic management

Single-repo epics (E1–E12, C1–C7) live as spec files + issues in their home repositories. The two cross-repo epics — LA-1 (roast sync & sharing) and LA-2 (reference feedback loop) — are tracked here: spec files in this repo, epic tracking issues with cross-repo task lists, and one user-level GitHub Project ("RoastPilot") as the cross-repo view.

The LA-1/LA-2 spec is cloud-sync-plan.md; its home epics are E15 (Agent) and C9 (Cloud).