The operator decided that HighFi is one of the two workspaces (with Otto) in the terminal layout a coming agent-organization skill will produce, with teams core infrastructure, product development and services under it, each possibly its own Herdr session, and a core CLAUDE.md referencing one per team. Existing Herdr sessions with good context ("HighFi Design Pen" w6:p1, "HighFi Build Frontend" w5:p1, the build lead, the lane agents of P-04) are to be kept and renamed into the structure, or retired or demoted where that is better. Nothing is applied yet and the skill is not built; this entry records the direction and how it would sit against HighFi's hard rules so the build lead and the o...
- Time
- 2026-10-07 03:09 WEST
- Where it was logged
context-log/2026-10-07_0408_dev-not-dev_workspace-and-team-structure.md
Session: Claude Code, fable, data-importer run 2026-10-07_0408
Location: dev-not-dev · ~/Desktop/Coding/Sandbox/HighFi/highfi-repo- Brought to main by
1abeb273caLanes as named Herdr panes, ship deploys from worktrees again, project check-in skill and reports (#49) (2026-10-07 05:40)The rows below that say "with it" describe this commit, which can carry other work from the same pull request.- Impact on decisions
Records it names:
- P-04 The roadmap is executed by a small team of lane agents orchestrated by the build lead accepted
- D-10 Human approval before commit and before PR creation accepted
- D-40 Approval sits next to the diff accepted
- D-85 A light Git flow (build phase - feat and fix branches off main, merged when done and deployed; develop returns at the MVP launch) and checkpoints that keep branches healthy accepted
- D-86 Every branch deploys the site to a semantic Vercel URL (personal account, OpenVentures, project highfi) accepted
- D-43 Agents write only in a HighFi worktree of the frontend clone accepted
- D-57 The prototype lives in Lenilson's repository as highfi-repo/frontend-prototype-v1 (moved 2 accepted
- D-09 Agents never act without scope accepted
- D-02 Local-first accepted
No decision record was created or changed with it.
- Scope expanded or reduced
Neither: no roadmap entry was added or removed with it.
- Plan clarity
No roadmap entry's clarity score changed with it.
- Milestones and metrics: roadmap entries moved
No roadmap entry's percentage moved with it.
- Superseded
Not superseded (status: active).