The Comprehensive Orthogonal Business Ontology (COBO)

Purpose: To provide a mutually exclusive, collectively exhaustive (MECE) map of every function within a standard technology company. This ontology serves as the “source code” for automating the enterprise.

1. Ontology Architecture

To ensure orthogonality (no overlap), we categorize functions by their Outcome and Object of Manipulation.

  • L1: Domain (The high-level “Swarm” or Department)
  • L2: Capability (A grouping of related conceptual abilities)
  • L3: Process (A sequence of actions to achieve a result)
  • L4: Atomic Action (The indivisible unit of work, automatable by an agent)

2. The 11 Domains (L1)

  1. Executive (The Brain): Strategy, Governance, resource allocation.
  2. Product (The Definition): Defining what to build based on market signal.
  3. Engineering (The Factory): Building the artifact defined by Product.
  4. Growth (The Engine): Acquiring capital and customers.
  5. Success (The Outcomes): Ensuring value delivery and expansion.
  6. Operations (The Backbone): Business orchestration and efficiency.
  7. Finance & Legal (The Ledger & Resource Allocation): Maintaining fiscal and juridical integrity.
  8. People & Culture (The Organism): Managing human and agentic capital.
  9. Data & Analytics (The Nervous System): Sensing, processing, and distributing intelligence.
  10. Security & Trust (The Immune System): Protecting integrity and ensuring safety.
  11. Partnerships (The Ecosystem): Expanding reach through alliances.

(Note: Infrastructure is now largely subsumed by Engineering (Platform) and Security/IT, but distinct L1 status is reserved for IaaS/PaaS companies where it is the product).

3. Deep Dive Hierarchies

1. Domain: Executive (The Brain)

Goal: Make high-quality decisions to maximize enterprise value.

  • 1.1 Strategy & Planning
    • 1.1.1 Market Analysis [Evo: Custom]: 1.1.1.1 Gather competitive intel, 1.1.1.2 Scenario Planning, 1.1.1.3 Macro-economic forecasting.
    • 1.1.2 Goal Setting [Evo: Custom]: 1.1.2.1 Define Objectives (OKRs), 1.1.2.2 Set KPI targets, 1.1.2.3 Strategic Pillar alignment.
    • 1.1.3 Resource Allocation [Evo: Custom]: 1.1.3.1 Capital efficiency modeling, 1.1.3.2 Portfolio management.
  • 1.2 Governance & Ethics
    • 1.2.1 Corporate Governance [Evo: Product]: 1.2.1.1 Board reporting, 1.2.1.2 Stakeholder management.
    • 1.2.2 Technology Ethics [Evo: Genesis]: 1.2.2.1 Responsible use guidelines, 1.2.2.2 Ethics review board (Human-in-the-loop).

2. Domain: Product (The Definition)

Goal: Translate market needs into technical specifications and designs.

  • 2.1 Product Strategy
    • 2.1.1 Roadmapping [Evo: Custom]: 2.1.1.1 Prioritize features (RICE/WSJF), 2.1.1.2 Release sequencing.
    • 2.1.2 Economics [Evo: Custom]: 2.1.2.1 Pricing capability analysis, 2.1.2.2 Packaging strategy.
  • 2.2 Discovery & Definition
    • 2.2.1 User Research [Evo: Custom]: 2.2.1.1 Conduct user interview, 2.2.1.2 Persona development.
    • 2.2.2 Specification [Evo: Custom]: 2.2.2.1 Write Requirements (PRD), 2.2.2.2 Acceptance criteria definition.
    • 2.2.3 Behavioral Definition [Evo: Genesis]: 2.2.3.1 Agentic capability assessment, 2.2.3.2 Automation boundary definition.
  • 2.3 Product Design
    • 2.3.1 User Experience (UX) [Evo: Custom]: 2.3.1.1 IA mapping, 2.3.1.2 User flow diagramming.
    • 2.3.2 Interaction Design [Evo: Custom]: 2.3.2.1 Natural language interface design, 2.3.2.2 Modality switching flows, 2.3.2.3 Ambiguity resolution patterns.

3. Domain: Engineering (The Factory)

Goal: Build, maintain, and evolve the technical artifacts.

  • 3.1 Architecture & Strategy
    • 3.1.1 System Design [Evo: Custom]: 3.1.1.1 Create RFC, 3.1.1.2 Domain modeling.
    • 3.1.2 Tech Health [Evo: Product]: 3.1.2.1 Debt backlog mgmt, 3.1.2.2 Dependency governance.
  • 3.2 Platform & DevOps
    • 3.2.1 Developer Experience [Evo: Custom]: 3.2.1.1 Toolchain maintenance, 3.2.1.2 Environment provisioning.
    • 3.2.2 Infrastructure as Code [Evo: Commodity]: 3.2.2.1 Cluster management, 3.2.2.2 Network configuration.
    • 3.2.3 Reliability (SRE) [Evo: Product]: 3.2.3.1 Incident response, 3.2.3.2 SLO/SLI management.
  • 3.3 Applied Intelligence
    • 3.3.1 Model Operations [Evo: Genesis]: 3.3.1.1 Tuning pipeline execution, 3.3.1.2 Vector index management.
    • 3.3.2 Context Engineering [Evo: Genesis]: 3.3.2.1 System instruction design, 3.3.2.2 Retrieval architecture, 3.3.2.3 Tool definition.
  • 3.4 Application Development
    • 3.4.1 Feature Build [Evo: Custom]: 3.4.1.1 API implementation, 3.4.1.2 UI component build.
    • 3.4.2 Quality Assurance [Evo: Product]: 3.4.2.1 E2E test automation, 3.4.2.2 Regression testing.

4. Domain: Growth (The Engine)

Goal: Convert attention into revenue.

  • 4.1 Revenue Operations (RevOps)
    • 4.1.1 Funnel Ops [Evo: Product]: 4.1.1.1 CRM architecture, 4.1.1.2 Lead scoring logic.
    • 4.1.2 Enablement [Evo: Product]: 4.1.2.1 Playbook creation, 4.1.2.2 Revenue intelligence config.
  • 4.2 Marketing
    • 4.2.1 Product Marketing [Evo: Custom]: 4.2.1.1 Positioning & Messaging, 4.2.1.2 Launch orchestration.
    • 4.2.2 Demand Gen [Evo: Product]: 4.2.2.1 Paid campaign mgmt, 4.2.2.2 Organic/SEO optimization.
  • 4.3 Sales
    • 4.3.1 Sales Execution [Evo: Product]: 4.3.1.1 Discovery (Qualification), 4.3.1.2 Proposal/Closing.
    • 4.3.2 Development (SDR) [Evo: Product]: 4.3.2.1 Outbound sequencing, 4.3.2.2 Inbound triage.

5. Domain: Success (The Outcomes)

Goal: Maximize CLTV, NRR, and Customer Advocacy.

  • 5.1 Value Realization
    • 5.1.1 Implementation [Evo: Product]: 5.1.1.1 Technical onboarding, 5.1.1.2 Data migration.
    • 5.1.2 Solutions [Evo: Custom]: 5.1.2.1 Workflow optimization, 5.1.2.2 Custom integration.
  • 5.2 Customer Success
    • 5.2.1 Lifecycle Mgmt [Evo: Product]: 5.2.1.1 Success planning, 5.2.1.2 QBR delivery.
    • 5.2.2 Support [Evo: Commodity]: 5.2.2.1 Incident resolution, 5.2.2.2 Self-service curation.
    • 5.2.3 Account Growth [Evo: Product]: 5.2.3.1 Renewal processing, 5.2.3.2 Expansion identification.

6. Domain: Operations (The Backbone)

Goal: Orchestrate business efficiency and procurement.

  • 6.1 Business Operations
    • 6.1.1 Corporate Strategy [Evo: Custom]: 6.1.1.1 OKR orchestration, 6.1.1.2 Board reporting.
    • 6.1.2 Program Management [Evo: Product]: 6.1.2.1 Cross-functional coordination, 6.1.2.2 Change management.
  • 6.2 Workplace & Procurement
    • 6.2.1 Procurement [Evo: Commodity]: 6.2.1.1 Vendor selection, 6.2.1.2 Contract negotiation.
    • 6.2.2 Environment [Evo: Product]: 6.2.2.1 Physical/Digital workspace mgmt, 6.2.2.2 Asset distribution.
    • 6.2.3 Travel & Expense [Evo: Commodity]: 6.2.3.1 Policy enforcement, 6.2.3.2 Event logistics.

7. Domain: Finance & Legal (The Ledger)

Goal: Maintain accessible liquid capital and defend against liability.

  • 7.1 Finance
    • 7.1.1 FP&A [Evo: Product]: 7.1.1.1 Financial modeling, 7.1.1.2 BVA (Budget vs Actuals) analysis.
    • 7.1.2 Accounting [Evo: Commodity]: 7.1.2.1 Audit prep, 7.1.2.2 Tax filing, 7.1.2.3 AR/AP.
    • 7.1.3 Treasury [Evo: Commodity]: 7.1.3.1 Cash management, 7.1.3.2 Capital markets relations.
  • 7.2 Legal
    • 7.2.1 Commercial [Evo: Product]: 7.2.1.1 MSA redaction, 7.2.1.2 Deal desk approval.
    • 7.2.2 Corporate [Evo: Commodity]: 7.2.2.1 Cap table mgmt, 7.2.2.2 IP/Patent filing.

8. Domain: Data & Analytics (The Nervous System)

Goal: Sense, process, and distribute high-fidelity intelligence.

  • 8.1 Data Platform
    • 8.1.1 Data Engineering [Evo: Product]: 8.1.1.1 Pipeline construction, 8.1.1.2 Schema modeling.
    • 8.1.2 Governance [Evo: Product]: 8.1.2.1 Data cataloging, 8.1.2.2 Quality assurance.
  • 8.2 Intelligence
    • 8.2.1 Business Intelligence [Evo: Product]: 8.2.1.1 Dashboard visualization, 8.2.1.2 Metric definition.
    • 8.2.2 Advanced Analytics [Evo: Custom]: 8.2.2.1 Predictive modeling, 8.2.2.2 Causal inference.

9. Domain: Security & Trust (The Immune System)

Goal: Protect integrity, privacy, and ensure safety.

  • 9.1 Security Operations
    • 9.1.1 Product Security [Evo: Custom]: 9.1.1.1 Code review, 9.1.1.2 Vulnerability management.
    • 9.1.2 Infrastructure Security [Evo: Product]: 9.1.2.1 Threat monitoring, 9.1.2.2 Identity governance.
  • 9.2 Trust & Assurance
    • 9.2.1 Compliance [Evo: Product]: 9.2.1.1 Certification audit (SOC2), 9.2.1.2 Regulatory alignment.
    • 9.2.2 Safety [Evo: Custom]: 9.2.2.1 Abuse detection, 9.2.2.2 Moderation policy enforcement.

10. Domain: Partnerships (The Ecosystem)

Goal: Leverage external leverage for distribution and capability.

  • 10.1 Ecosystem
    • 10.1.1 Tech Partnerships [Evo: Custom]: 10.1.1.1 Integration certification, 10.1.1.2 Joint solutioning.
    • 10.1.2 Channel [Evo: Product]: 10.1.2.1 Reseller enablement, 10.1.2.2 Partner portal mgmt.
    • 10.1.3 Developer Relations [Evo: Custom]: 10.1.3.1 External advocacy, 10.1.3.2 Documentation.

11. Domain: People & Culture (The Organism)

Goal: Attract, develop, and retain high-performing capital.

  • 11.1 Talent Lifecycle
    • 11.1.1 Acquisition [Evo: Product]: 11.1.1.1 Sourcing, 11.1.1.2 Assessment coordination.
    • 11.1.2 Development (L&D) [Evo: Custom]: 11.1.2.1 Competency mapping, 11.1.2.2 Leadership coaching.
  • 11.2 Culture & Comms
    • 11.2.1 Internal Comms [Evo: Custom]: 11.2.1.1 Organizational alignment (All-hands), 11.2.1.2 Knowledge distribution.
    • 11.2.2 Engagement [Evo: Custom]: 11.2.2.1 Recognition programs, 11.2.2.2 Ritual facilitation.

4. The Functional Interface Map

How the domains speak to each other (The “API” of the company).

From DomainTo DomainArtifact Transferred (The “Payload”)
ExecutiveProductStrategic Pillars, Budget Constraints
ProductEngineeringPRD (Spec), Design Assets, Priorities
EngineeringGrowthRelease Note, Commercially Ready Product
GrowthSalesMQL (Marketing Qualified Lead)
SalesSuccessSigned Contract, Handover Notes
SuccessProductUser Feedback, Feature Requests, Bug Reports
OperationsAllPaychecks, Legal Protection, Policy

5. Usage in Automation

To automate a company, traverse this ontology:

  1. Select a Node (e.g., 8.1.2 Governance).
  2. Define the Agent (e.g., “Data Steward Agent”).
  3. Map Inputs (e.g., Unclassified Table Schema).
  4. Map Outputs (e.g., Classified Metadata Tag).
  5. Codify Process (e.g., The prompts and tool chains to execute 8.1.2.1).