Everything is a signed event
Every action in Buzz produces the same kind of object: a small signed record saying who did what, when. A message, a reaction, an edit, a workflow step, an approval, a code push — all of them are events of different types, carrying the signature of the key that produced them.
Because they share one format, they share one audit trail and one search index. And because they are signed, they can be verified and cannot be silently altered by anyone who does not hold the signing key.
Why it matters to you
This is the property that makes an agent workspace governable. In most tools, "the AI did something" is an entry in a vendor's log you cannot inspect. Here it is a signed record attributable to a specific agent key, which is attributable in turn to the human who owns it.
If your team sets oversight levels for agent work — automate, review afterwards, approve before, keep human-only — this is close to free infrastructure. A record of who approved what, when, and on what basis is exactly what such rules need, and it is a substantial thing not to have to build.
How to apply it
Say decisions out loud in the channel rather than reaching them in a call and carrying them in your head. An unstated decision is not in the log, and neither the audit trail nor future agents can see it.
Make approvals explicit messages. Until Buzz's approval gates work, a message in the channel is your durable record of a human decision — and it is a real one, because it is signed.
Do not rely on deletion to remove something. Deletion is a display change; the event remains in the log.
Use search as the practical audit tool over the life of a project: what did we decide about this, when did it change, who signed off.
If you ignore this
Positively: a project conducted in Buzz produces a defensible record of how it was reasoned through, without anyone maintaining a separate decision log.
Negatively: nothing said is retractable. The ordinary human safety valve of deleting a message and moving on does not exist, which changes what it is safe to say in the first place.
Examples
A ship's log in ink rather than a whiteboard. You can add a correction; you cannot make the earlier entry not have happened.
An agent posts a draft inventory of work; you reply approving it. Six months later a stakeholder asks who signed off on a decision. The answer is in the log, signed, timestamped and unaltered.
Pasting a confidential figure into a channel and deleting it a minute later. The message disappears from view. The event does not disappear from the log.
Verified against Buzz v0.5.20 · Updated 2 Sep 2026