Tree · Kandev · doc-inline · balanced

Choose the smallest coordination boundary

Keep a conversation in one session when context is shared; use a task or workspace boundary when ownership, history, or repository scope must separate.

Choose the smallest coordination boundary A decision tree branches from one coordination question into same-session messaging, an inherited task subtask, an isolated new workspace, or one task with multiple repositories. DECIDE Where should it live? context · ownership · data LOCAL Same session share context · message TASK Task subtask parent_id=self · inherited SCOPE New workspace isolated repo + data REPOS One task, many repos shared outcome · separate worktrees BOUNDARY SIZE Session → task → workspace choose the smallest boundary that preserves clarity FOCAL DECISION