From 11e7e74ccbede07cb6204fb09c48abfc226083a5 Mon Sep 17 00:00:00 2001 From: John Tennant Date: Tue, 8 Sep 2026 16:53:29 -0400 Subject: [PATCH] docs: clarify branch channel reuse Signed-off-by: John Tennant --- docs/experiments/channel-backed-tasks.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/experiments/channel-backed-tasks.md b/docs/experiments/channel-backed-tasks.md index 4dc3e7d4ea..9b91b0330c 100644 --- a/docs/experiments/channel-backed-tasks.md +++ b/docs/experiments/channel-backed-tasks.md @@ -11,7 +11,8 @@ Conversation → local task + new channel → implementation branch → pull req - The task's mutable data lives in the channel canvas. - No native Buzz task is created. - The task has zero or one implementation branch. -- Each implementation branch belongs to one task channel. +- Each implementation branch has one home channel. Creating a branch from an appropriate task channel binds it to that channel instead of creating another one. +- A branch created without an appropriate current channel gets a new channel. Rebinding an established branch is for correcting mistakes, not routine restructuring. - The branch, pull request, CI, and review use the task's channel. ## Canvas data model