Agent, Subagent, and Human: Distributing Roles in Automation
Three levels of responsibility
- The agent — an end-to-end scenario: inputs, stages, tools, a verifiable artifact. Example: the CustDev agent from interviews to an opportunity map.
- The subagent — one function in an existing process: sort emails, compile minutes, find a quote, answer from the database.
- The human — decisions: priorities, sending, legal position, publication. The agent prepares the material, the human makes the decision.
Where the boundary is visible in the product
- The mail assistant sends nothing on its own: the final text and the recipients are confirmed by a human.
- The database consultant has read-only access: writing and modifying data is prohibited at the architecture level.
- The legal RAG navigator forms a package of materials for the lawyer, not a legal opinion.
- The local meeting scribe marks uncertain fragments for verification by the person responsible for the meeting.
Why the boundary is set before launch
Access rights, sources, permitted actions, and the confirmation point are defined before the subagent or agent is connected. This protects both the company and the result: the higher the autonomy and the consequences of a mistake, the stricter the permissions, the journaling and the human confirmation. Learn more in the security section.
How to choose the level
One useful function in a familiar process — a subagent. An end-to-end scenario with an artifact — an agent. Several roles in sequence — a combination like the Golden Trio, where the human checks every handoff.
Adapted from the article: agentseffect.com.