So far in this series: the translation layer turns your software into structured actions, and permissions plus approvals decide what each agent may touch.
Part three ties it to how your team actually works: roles and business logic.
Roles are how you stop configuring agents one by one. A support role bundles search-records, draft-response, and escalate-ticket. A billing role bundles read-invoice and issue-refund-under-threshold. Define the role once, assign it to any agent — human, internal copilot, or third-party model — and the permission boundaries travel with it. Change the role, and every agent wearing it updates at once.
Business logic is the part most agent setups skip. Your company doesn't run on "create ticket." It runs on rules like: refund under $50 approves itself, over $50 needs a manager; enterprise tickets route to the senior queue; nothing ships until the order is paid. HIVE lets those rules live where the actions live. The agent doesn't have to learn your playbook from a prompt — the playbook is part of what the software exposes.
That's the full picture of how it works. Actions are the vocabulary. Permissions are the boundaries. Roles are the job descriptions. Business logic is the way the company already runs.
Put together, the agent stops improvising and starts operating the way you intended.
Which of your team's unwritten rules would you encode first?