Who owns an agent's rules? Security: the forbids that apply everywhere. Platform: the defaults for each pattern. App team: the narrow permits for their own agent. That's one split. What's yours?

One refund tool, three callers: an assistant acting for a frontline rep, the same assistant acting for a supervisor, and a nightly job. An allow-list by tool name treats them identically. Yes to all three, or no to all three. domesystems.ai/mcp-gateway

Most agent governance stops at the endpoints: gateway for tools, a router for models. We're launching Dome this morning: one system for the code an agent ships, the tools it calls, and the model it reasons through. domesystems.ai/updates/dome-…