Week 0x25

I find coding agents really like to focus on “seams”, and they tended toward building a generic “provider plugin” API when filling the hole left by Letta. But I wanted a monolith, so directed their focus on building from ACP inward.

That backfired; I found that ACP structures and semantics have woven deep into the architecture of the agent runtime. So I’ve now focused on an actual seam: the protocol between the server and the edge client (which I call an armature). I branded the protocol BearWire because having a name makes it easier to communicate about. This was BearWire week.

Also some fun work on portability, which is a new objective. Being able to export and import a bear is a great way to stay thoughtful about responsibility lines. It already highlighted that models assume a privacy principle that works against bear memory getting to know the user.