Capabilities in the codebase

What the owner can do

He speaks to it. A desktop edge handles wake word, recognition, turn assembly and synthesis; a browser session on the iPhone sends a recorded utterance to the gateway and gets sentence audio back.

He delegates. A brief goes to the fleet through one interface, whether the agent answering is in this process or on another host. He runs tools directly, or he asks for bounded background work that defers outward steps into the approval queue.

He reviews. The HUD shows subsystem evidence, agent workspaces, dialogue, cameras and activity, and the approval workspace lets him accept or reject one pending action at a time.

Where the work goes

M.U.S.H.E.G.H. is the head. It plans, decomposes, decides what matters now, and sends out work that is already scoped and professionally explained. It manages the owner's day-to-day.

His own job is not development. Everything development goes to Bagadata: code, frontend, backend, database, engineering of every kind. Bagadata receives the scoped brief, expands it, runs the council, compiles a master plan, assigns the steps and follows them through.

Availability is evidence

A configured provider, roster entry or reachable HTTP endpoint is not proof that every operation works. The generated tool reference lists registered tools for documents, tasks, communication, connected apps, home automation, PC operations and coding workflows; each adapter still needs its own dependencies, account scopes and credentials.

Verify real voice, source timestamps, executor routing and external results on the actual deployment. A HUD screen contract is a declaration of a panel, not a claim of a live adapter behind it.