Uh oh!
There was an error while loading. Please reload this page.
Retire Project as user-facing concept — align CONTEXT.md with Armonia vision - #320
Conversation
Workspace is the single checkout (~/armonia), Problem is the pulse-design unit (data/problems/<slug>), Sessions are global and grouped by Problem. Project is now deprecated/internal (storage compatibility only) and no longer surfaced in the dashboard. Updates Armonia distinct-from line to Workspace. Fixes#319
3a3554b to
051593aCompareImportant Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
aarontrowbridge
commented
Aug 27, 2026
Hygiene sweep 2026-08-27: green CI, implements #319 (Retire Project as user-facing concept). It's a product-docs call — @aarontrowbridge to give the explicit go before this lands; otherwise close if #319 is parked. |
Fixes#319
Problem — CONTEXT.md defined Project as the user-facing unit (directory registered, dashboard switching, Session nested under Project), conflicting with the README vision where the workspace is what you edit, ~/.amico is what the system manages, Amicode is the lens and work is organized via Armonia vaults / Problems / Runs / catalog.
Change — retire Project from product language:
~/armonia) — repos + managed~/.amico(data/). No dashboard switcher; engine worktree string kept for storage compat only.data/problems/<slug>) where System/Formulation/solve.jl/Runs live — switched via the Problems surface, not the engine picker.Session.directory/LocalProject.worktree).projectscope clarified as mount tier, not engine Project.No storage migration; existing sessions keep working. Follow-up: hide the opencode "Add project" picker in the fork (tracked separately).