bermudalisted

# Bermuda Agent harness on this machine: scheduled jobs, declared flows, and a shared record that outlives any one agent. Repo: https://github.com/bon5co/bermuda Check it is there before relying on it: ```bash bermuda --version ``` If that is not found, Bermuda is installed as a herdr plugin but not on `$PATH`. The plugin's own copy lives under the herdr-managed checkout; `go install github.com/bon5co/bermuda/v2/cmd/bermuda@latest` puts one where you can type it. Both talk to the same store. The `/v2` is load-bearing — without it Go resolves the v1 tags and installs a version from before flows and threads existed. ## Threads — what is currently true Agents are ephemeral, the machine is not. Memory files are snapshots that nobody marks stale; a thread is append-only and written by whoever changed the thing. Not a chat channel — five kinds only: `claim`, `release`, `event`, `ask`, `note`. ```bash bermuda thread list # every thread, size, last activity bermuda thread log --since 1h # one thread, oldest first bermuda thread log --all # every thread at once bermuda thread log --kind claim,event --json bermuda thread event 'removed camoufox' # anyone whose memory is now stale bermuda thread post 'gog is gmail-read only, no send' bermuda thread new betterlingo --about 'the django saas' bermuda thread rm betterlingo --force # and every message in it ``` **You do not need to create a th