First real project I've built, a multi-agent "personal executive AI" instead of one big assistant. Would love feedback.

This is the first project I’ve actually finished and felt comfortable enough to share, so go easy on me. That said, please poke holes in it. That’s half the reason I’m posting. I’ve been messing around with the idea of having multiple AI agents, but I didn’t really want the usual setup where a bunch of agents talk to each other and you’re never quite sure who did what. So I ended up building something closer to a small org chart. There’s one lead agent I call Master Control. Everything starts there. It decides who should handle the request, delegates it, and then reports the result back to me. The other agents don’t really “talk to me” directly, which has made the whole thing way easier to follow. Under that I have a few specialists for different things like research, coding, and general day-to-day stuff. I’ve tried pretty hard not to give every agent access to everything. If an agent doesn’t need a tool or a piece of data for its job, it doesn’t get it. The part I probably spent the most time thinking about was oversight. There’s a separate watcher/audit agent that can flag things independently. The lead agent can’t edit its findings, silence it, or override what it reports. The watcher reports to me separately. I also put hard approval gates in front of anything I’d consider difficult or impossible to undo. Spending money, sending something externally, deleting data, changing credentials, that kind of thing. The agents can prepare the action, but they can’t actually cross that line until I approve it. There’s also some persistent memory so I’m not starting from zero all the time. I’ve been using it for a few weeks now for normal stuff like research, drafting, and light ops. The thing I didn’t expect is that the biggest improvement hasn’t really been “more powerful AI.” It’s just calmer to use. I know that sounds weird, but knowing there’s a defined chain of command and that nothing irreversible happens without me approving it makes me much more comfortable letting the system do things on its own. And just to get this out of the way: I’m definitely not claiming I invented multi-agent systems. CrewAI, AutoGen, LangGraph, Google ADK, etc. already cover a lot of the orchestration side of this. I’m building mine on top of OpenClaw. What I wanted was a slightly different emphasis. Most of what I found treated governance as something you add once you’ve figured out the agents. I wanted to start with the governance and build the agents inside it. So the rules were basically: One agent is accountable for reporting back to me. Specialists only get the access they actually need. The auditor is independent of the agent it’s auditing. And irreversible actions always come back to the human. LangGraph’s human-in-the-loop checkpoints are probably the closest thing I found conceptually, but I wanted those controls to behave more like system policy than something I remembered to add to individual workflows. I’m also aiming this mostly at personal/solo use rather than enterprise automation or coding swarms, which seems to be where a lot of the examples live. Still early, and I’m sure there are holes I haven’t found yet. Happy to talk architecture, approval gates, the watcher setup, or anything that looks dumb from the outside. Built on an open agent framework. Nothing particularly exotic underneath it. For anyone who wants the actual breakdown instead of just vibes, here’s how it’s tiered: Tier 0, Lead Agent (Master Control): intakes every request, classifies it by objective/priority/risk, decides who handles it, and is the only one that reports back to me. It also enforces the approval gates. Tier 1, Specialist sub-agents (least-privilege, scoped per role): research/analysis does read-only lookups and drafting with no side effects, ops/comms handles scheduling and message drafting but can’t fire off a send on its own, and build/technical stays sandboxed to its own environment with no reach into other agents’ tools or data. Tier 2, Audit/Watcher (independent): cross-checks the other agents’ actions against policy and flags problems straight to me. It can’t be edited, delayed, or silenced by the Lead Agent. No task-execution role, oversight only. Tier 3, Owner (me): final sign-off on anything irreversible, and the only one who can approve remediation after the watcher flags something. Quick version of what needs my sign-off vs. what doesn’t: research, summarizing, and drafting run freely. Anything that leaves the system (sending externally), costs money, deletes data, or touches credentials stops and waits for me. No exceptions, and no agent can self-approve its way around that.