Understanding Domain Agent Taxonomies: Industry → Process → Function

Early enterprise AI pilots often deployed a single, general-purpose AI agent to handle all use cases within a department. The appeal was obvious: one integration, one governance policy, one point of maintenance. In practice, these monolithic agents underperformed across the board. They lacked the deep contextual knowledge needed for specialized tasks, confused terminology between domains, and generated outputs that required extensive human review before being actionable.

The root cause is a fundamental tension between generality and accuracy. An agent optimized to handle everything well is, in practice, optimized to handle nothing excellently. For low-stakes queries this is acceptable. For enterprise decisions—procurement approvals, clinical recommendations, compliance filings—it is not.

The solution is a hierarchical taxonomy that structures agents at three levels of specificity. At the top, the Industry Layer defines the broad domain: Healthcare, Financial Services, Manufacturing, Legal. This layer shapes the agent's vocabulary, regulatory context, and the external data sources it can access. A Healthcare Industry Agent understands ICD-10 codes, HIPAA constraints, and clinical workflow conventions that are irrelevant to a Manufacturing Industry Agent.

The Process Layer sits below the Industry Layer and defines cross-functional workflows within that industry. In Healthcare, processes include Patient Onboarding, Care Coordination, Billing & Coding, and Compliance Reporting. Each Process Agent orchestrates a subset of the industry's Function Agents to complete a multi-step workflow, maintaining state across steps and handling exceptions at the process level.

The Function Layer contains atomic agents—each responsible for a single, well-defined task. In the healthcare example, the Care Coordination process might invoke a Gap Analysis Function Agent (identifies missing preventive care), an Outreach Function Agent (drafts patient communication), and an Scheduling Function Agent (creates calendar entries in the EHR). Each Function Agent is small, testable, and replaceable.

This atomicity is what enables reliable production deployments. If the Gap Analysis Agent's model is updated or its data source changes, only that agent needs to be tested and redeployed. The Process and Industry layers above it are unaffected. This isolation dramatically reduces the blast radius of changes and makes continuous improvement tractable at enterprise scale.

Complex enterprise workflows often span multiple industry taxonomies. A legal due diligence workflow for a cross-border acquisition might require agents from a Legal taxonomy (contract review, jurisdiction analysis), a Financial Services taxonomy (risk assessment, regulatory filing), and a Manufacturing taxonomy (supply chain compliance). Cross-taxonomy orchestration requires a meta-orchestrator that understands the dependencies between taxonomies and can resolve conflicts in terminology or data formats.

Successful implementations define explicit interface contracts between taxonomies—standardized data schemas that any agent in any taxonomy can produce and consume. These contracts are the connective tissue of the enterprise agentic system, enabling heterogeneous agents to collaborate without requiring each agent to understand the internals of every other.

The practical starting point for taxonomy design is process mining: analyzing existing human workflows to identify the atomic tasks that occur most frequently and carry the highest impact. These become the first Function Agents. Group them by the processes they serve, then by the industries those processes belong to, and you have the skeleton of your taxonomy.

Avoid the temptation to over-engineer the taxonomy before deployment. Start with three to five Function Agents in one Process, validate them in production, and expand based on measured impact. Taxonomies that grow organically from validated function agents are consistently more accurate and easier to maintain than those designed speculatively from the top down.