HERMIT
Explorer → Entities → Capabilities → Role-based operators

Role-based operators

ID: cap-role-based-operators · Type: capability

Capability

Role-based operators

Hermit can grow from one focused operator into a multi-role organization when the work needs different lenses

Roles are explicit, file-backed operators with their own prompts, standards, inbox, and record.

At a glance

Audience
People shaping repeatable operational workflows
Owner
Hermit Website Lead
Status
active

Proof points

  • Each role has its own role.md, AGENTS.md, prompts, and agent operating files.
  • Bootstrap guidance starts with one sharp role and only splits when a genuinely different lens is needed.
  • The runtime can switch active chat roles instead of mixing incompatible responsibilities.

Details

Summary

Hermit does not force one generic assistant to handle every kind of decision. It can create distinct operators with different responsibilities and standards while keeping them in the same workspace.

Why It Matters

That makes judgment clearer. Planning, operations, research, and website work can stay separate when they should, instead of becoming one blurry prompt.

Demo Ideas

  • Show how a website role differs from a product or sales role.
  • Show when Hermit recommends creating another role instead of stretching the current one.