The six specialist agent roles: research, reasoning, design, document, patent, manufacturing
Camelia is HIIE's lead AI orchestrator (your director and copilot), but the actual specialist work is handled by exactly six sub-agent roles she can delegate to. Knowing what each one is for helps you understand who does what when you describe a build.
The six roles
There are exactly six specialist sub-agent roles, and the list is fixed and enforced in code:
- research — concise, web-informed briefs
- reasoning — step-by-step structured analysis with trade-offs
- design — hardware/product design notes (dimensions, materials, components, cost)
- document — clean, finished markdown documents
- patent — structured claims and summaries, flagging what needs human/legal review
- manufacturing — sourcing/BOM-oriented markdown plans
Camelia herself is not one of these roles. She is the director who decides which specialist to hand a task to, then assembles the results.
Where the list comes from
This enum is enforced in the spawn_subagent tool schema and in the flow-step schema, so the same six roles power both Camelia's ad-hoc delegation and multi-step flows. The visual node editor's role dropdown also offers exactly these six.
A note on labels you might see
The node-editor palette shows some cosmetic labels (for example a "PCB Engineer" or "Validation" tile) that are convenience names mapping onto the real roles — "PCB Engineer" maps to design and "Validation" maps to reasoning. These are display conveniences, not separate agents. Under the hood, only the six roles above exist.
If you want a specific kind of output, it helps to think in terms of these six roles: research and reasoning to investigate, design and manufacturing for the physical product, document for deliverables, and patent for IP-flavored analysis.