Maintain the channel canvas
Everyone · Set up the workspace
Steps at a glance
1. Decide what the canvas holds for this channel
Each channel has exactly one canvas — a shared document that sits alongside the conversation. One per channel is a constraint worth respecting: it forces the canvas to hold the thing everyone in the channel needs to see, not everything anyone wants to store.
For a project channel, the natural occupant is the anchor content: the scope statement, the current task list, the plan, the decisions taken so far.
2. Open the canvas
Open the canvas from within the channel. Where it opens from can vary between versions.
3. Seed it with the channel's anchor content
Put the scope statement in first. In a project channel, the scope statement is what stops both humans and agents drifting — and agents in the channel can read the canvas, so it functions as standing context rather than as a document nobody opens.
4. Keep it current as the project moves
Update the canvas when a decision changes the shape of the work: a scope boundary moves, a finding is confirmed, a deliverable is agreed. The conversation records how you got there; the canvas records where you are.
5. Prune it deliberately
Buzz accumulates context but does not govern it — there is no freshness scoring, no pruning, no quality signal. Over a long project that is a real problem: stale content in the canvas is read by agents as current truth.
Set yourself a rhythm — the end of each project phase is a natural one — to remove what is no longer true rather than appending to it. See Context accumulation is not control.
Verified against Buzz v0.5.20 · Updated 2 Sep 2026