AI and Agents
- Why does an agent need a working layer around the model?
Answering a question is not the same as changing a colleague's files. Why agentic-organization separates the workstation client from organizational controls.
- Why can't one warning sentence secure an agent?
When an external document tries to direct an agent, the useful question is where each control acts and where it stops.
- Why can't a policy document stop an agent?
Reading a company policy and enforcing it at a tool call are different jobs. The reasoning behind agentic-organization's policy engine and its current limits.
- Buzz's event memory: When does an old conversation help?
Buzz puts conversations, reviews and Git events in one searchable workspace. That makes history easier to find, but does not turn every past claim into verified knowledge.
- OpenRig can start an agent team. Who trusts the workspace?
Starting an OpenRig team can also affect provider settings and workspace trust. A small coding trial needs an access boundary as well as a team definition.
- Cloudflare Agents and the handoff between agents
Cloudflare Agents SDK can host several persistent agents, but the handoff record, authority boundaries, and ownership of the work still need design.
- Buzz and the difference between a recorded decision and an authorized one
Buzz puts people, agents, and project events in one signed log. That record improves traceability, but it does not by itself enforce who can approve a production release.
- OpenRig can assign an agent a role. Who owns the result?
OpenRig gives coding agents stable team roles and a work queue. That is useful, but it does not replace review evidence, access boundaries or release ownership.
- Who owns the work when a Cloudflare agent goes offline?
Cloudflare Agents SDK and Think can keep an agent's state, but recovery, approvals, and ownership of business decisions still need careful design.
- Agent Identity in Buzz: Portability, Auditability, and Organizational Continuity
In Buzz, agents are team members. But who really owns a team member, what happens when one is replaced, and how is history preserved? Nostr's signed event log solves the critical problems companies face in agent governance.
- What Is an Agent: Organizational Boundaries, Responsibility, and Control
What's the difference between a tool and an agent? A tool performs a task; an agent makes decisions and carries responsibility. An organization without defined roles, policies, and accountability mechanisms for autonomous systems is running shadow AI.
- Discovery Phase: Creating an Inventory of Hidden AI Agents
How many AI agents work in your company, and no one knows? Start with observation, inquiry, and mapping. Methods for discovering institutionalized shadow AI and a simple inventory approach.