Folks and work
Persistent teammates, focused tasks, rooms, and handoffs.
Folks stay
A folk keeps its conversation, model, instructions, folder, memory, tools, and computer. Create another folk when the role, access, or project should differ.
- A coding folk attached to one repository
- A research folk with browser and document tools
- An operations folk with Gmail, Calendar, and Slack
- A local-model folk for private work
Tasks are runs
Use Task when the work should have a beginning and a result. Tasks are easier to track than mixing every request into the main thread. Scheduled runs create tasks automatically.
Rooms
Rooms let several folks and people share a brief. Use a room when specialists need the same context or should hand work to one another. A Leader folk can take the request, delegate focused tasks, and bring the pieces back.
Handoffs
A folk can ask another folk to handle a bounded subtask. The delegated run keeps its own activity and returns a result. Give each delegate a narrow outcome. Do not assign two folks ownership of the same files.
| Need | Use |
|---|---|
| Ongoing relationship and memory | Folk |
| One deliverable with a status | Task |
| Several participants sharing context | Room |
| A specialist on one branch | Handoff |
| Repeated work at a known time | Routine |