A notebook of decisions, mistakes, and small wins from the people building Behio. No press releases. First entries land soon.
An honest look at the architectural ceilings of the plugin-store model and why our AI layer needed a database it owned end to end.
Why we treat the AI as a coworker with scoped tools and an audit log, not as a chat box bolted on top of an admin.
What the Model Context Protocol actually is, why we built our AI tools around it, and what it means for shops that already use Claude or in-house models.
The waiting list also gets the journal in the inbox before anywhere else. One mail per real post, never more.