PHASE · 06

Safeguard and hand off¶

Alongside everything. What an agent can reach, where your Berd actually lives on disk, staying current with weekly releases, reporting a bug, and the one narrow bridge to Buzz for the day the work stops being yours alone.

Manage connections and extensions

Everything under the connections section of Settings is "a thing Berd can use on your behalf", and that is the reason to be slow here. A connection is an OAuth sign-in that gives an agent standing access to Slack, GitHub or Google Drive; an extension is a tool you configure by hand. They share one grid and have different rules. The outcome of this task is that you know which kind you are adding, who manages it, and what its status means before you act on it. Takes untimed · Moment apply
Know where your Berd lives, and back it up

A lost laptop is a lost cast, a lost method and a lost memory — and a laptop full of client material is an exposure whether or not it is lost. Almost everything Berd knows about you is a plain text file in a known place. The one thing that is not, the conversations themselves, is the gap this page names rather than papers over. The outcome is an inventory you can act on tonight. Takes untimed · Moment apply
Keep Berd current and report problems

Berd shipped three releases in five days in August and two more the following month. On macOS it updates itself; on other platforms you do. When something is wrong there are three documented ways to say so — only one of which, the GitHub issue, exists in the public build — and one thing not to do: open a pull request. The outcome of this task is a Berd that is current, a habit of reading what changed, and a bug report that lands where the team will read it. Takes untimed · Moment change
Hand work between Berd and Buzz

One route, a skill published in v0.6.3: a Berd agent reads a Buzz thread through the Buzz CLI, continues privately, and can send back one approved reply. Takes untimed · Moment apply