SUPPORTING KNOWLEDGE · 0018

What survives the trip to Buzz¶

The day a piece of work goes multiplayer, "move it to Buzz" turns out not to be one move. A Berd workspace is several kinds of object, and each travels differently — some as files, some as rebuilds, one not at all. Knowing the manifest before you pack is the difference between an afternoon's move and quietly losing things.

In Berd	Does it travel?	How, and what changes
The conversation	No	Post the conclusion to the channel. The session itself never travels; the reasoning stays on your laptop unless you write it up.
An agent	As a rebuild	Export it as a card, file or ZIP and set it up again in Buzz. It arrives without an identity or channel membership — and gains both there: its own key, a signed record, memory held on the relay.
A skill	Via the harness	A skill belongs to the harness, not to either app. Install it globally where the harness runs; a project-scoped skill is invisible to a Buzz agent, and the failure is silent.
An automation	As a rebuild, carefully	Recreate it as a workflow. Buzz's workflow editor is good; its engine is not yet dependable for schedules or approval steps. Check that the work happened, not that the run finished.
Files and artefacts	Yes	Upload them to the channel, or put the standing version in the canvas.
What Berd knows about you	No	Hints and memory live in your own config, not in the agent's file. The channel builds shared context of its own instead — from what is said in it.

Outlook — the products are growing together, without a date

In August 2026 Block told the press its focus is Buzz and that it plans to bring the best of Berd's single-player experience into it. Two weeks later, on Block's own On The Block, Berd was described as a product with a roadmap of its own, where it is the harness that fades into the background, not the app. Both statements are first-party; treat the tension as unresolved. The visible bridge-building is on the Buzz side, and no shipped release moves a Berd session into a Buzz room. Do not defer a move that has a reason today for a merge that has no date. Last checked: Berd v0.6.4, Buzz v0.5.23, 2026-09-19.

Why it matters to you¶

Three rows of the table surprise people, all in the same direction: things assumed to come along do not. The reasoning trail stays behind unless you post it. A skill that worked all month vanishes without an error message, because it lived in the project folder. And the rebuilt agent starts without the preferences Berd had accumulated about you.

The gains are just as concrete: the rebuilt agent signs its own actions, colleagues can add it to their teams, and everything it does becomes part of a record a client can be shown.

How to apply it¶

Decide where the work lives before you start it — the rule is on Buzz or Berd, and moving later means rebuilding.

When a move is right, move at a boundary. Finish the thought in Berd, then carry the manifest across in one sitting: post the conclusion, upload the files, import the agent from its ZIP, reinstall its skills globally, rebuild the automation last and watch its first run.

If work might go multiplayer, install the skills it depends on globally from day one — see Write a skill and decide where it lives. It costs nothing in Berd and removes the silent failure later.

If you ignore this¶

The move looks complete — channel made, files posted, agent rebuilt — and three weeks later a colleague asks why a decision was taken, and the answer exists only in a chat history on your laptop. Or the rebuilt agent underperforms for a month before anyone notices that its skills never made the trip.

Examples¶

AnalogyConcreteNon-example

Moving house. Furniture travels in the van (files), appliances have to be rewired for the new building (agents, automations), and the years you lived there do not come along at all (the conversation). Nobody blames the van.

An engagement goes multiplayer. You post the scope note, upload the workbook, import your review agent from ZIP — it gets its own key and joins the channel. Next day it cannot find its checklist skill: the skill was project-scoped. One global install fixes it.

Searching Buzz for something you remember discussing "early in the project". You discussed it in Berd. The channel's record starts on moving day; nothing before it exists to the workspace.

Do it: Hand work between Berd and Buzz · Share, import and keep your agents

Last checked: Berd v0.6.4, 2026-09-19 — compiled from this corpus's source readings of 2026-09-11 (Berd v0.6.4, Buzz v0.5.23); the handoff route is read from source, not yet tested end to end.

Reference¶

Buzz or Berd — the decision rule, the word mapping, client material
Taking work private — the same trip in the other direction, on the Buzz Guide
block/berd — skills/buzz-handoff/SKILL.md — the one shipped route between the products
Workflows: what they can and cannot do today — why rebuilt automations need watching

Verified: Berd v0.6.4 · 2026-09-19