One founder, one 8 GB laptop. The work is split across departments — each one a named agent that owns its area, holds its own tools, and reports back. This map is read straight from the machine, so it cannot drift from what actually exists.
Department map
Node size is headcount · click a department to open its agents
Departments
| Department | Head | Agents | Budget line |
|---|
A skill is a workflow you talk to. An agent is a worker that runs on its own and reports back. When a skill has an agent, the agent is launched.
The same facts, drawn as pictures. Every number here is counted from the database — nothing is estimated.
Who runs the skills
skills that the org chart assigns, by how solid the ownership is
Agents per department
Head plus members, biggest first
Tools each agent holds
More tools means a wider job
Which agent reaches which service
A filled square means that agent can use that service
Ask out loud which agent does a job. It answers only from your real agent list — if nothing fits, it says so instead of inventing one. Runs on your free NVIDIA API.
Tap the microphone and ask a question
—
—
Outside services wired into the system, and the agent that owns each one.
| Service | Used for | Owner |
|---|
Skills with no agent to run them. These are shown on purpose — a map that hides its own holes is marketing, not engineering.