Skip to content

Domains

Purpose

Domains organize the organization's data and knowledge according to meaningful areas of business, technology, operations, and organizational activity.

A domain provides context for concepts, datasets, metrics, systems, processes, documents, and other assets that share a common area of responsibility or subject matter.

Domains are not isolated data silos. They use the common organizational ontology and may relate to concepts and assets in other domains.

Initial Domains

Social Media

Data and knowledge relating to the organization's presence and activity across external social media platforms.

Initial platforms include:

  • X
  • LinkedIn
  • Instagram
  • Facebook
  • TikTok

Initial scope includes:

  • Social accounts
  • Published content
  • Audience metrics
  • Content performance
  • Engagement
  • Reach and impressions
  • Platform activity
  • Campaign related measurements
  • Cross platform metrics and KPIs

Social Media is the initial implementation domain and will be used to validate the core ontology.

Observability

Data relating to the operational health and behavior of the organization's technical systems.

Initial scope includes:

  • Metrics
  • Logs
  • Traces
  • Services
  • Infrastructure
  • Requests
  • Errors
  • Latency
  • Availability
  • Alerts
  • Incidents

Potential sources include OpenTelemetry, Prometheus, Loki, and Jaeger.

Finance

Data relating to the organization's financial activities and performance.

Potential scope includes:

  • Revenue
  • Expenses
  • Invoices
  • Payments
  • Accounts
  • Budgets
  • Financial transactions
  • Financial reporting
  • Forecasting

People

Data relating to people within and interacting with the organization.

Potential scope includes:

  • Employees
  • Contractors
  • Roles
  • Organizational structure
  • Recruitment
  • Employee lifecycle
  • Responsibilities
  • Skills

Projects

Data relating to projects and coordinated organizational initiatives.

Potential scope includes:

  • Projects
  • Milestones
  • Tasks
  • Deliverables
  • Resources
  • Project performance
  • Project risks
  • Project documentation

Products

Data relating to products and services developed, maintained, or delivered by the organization.

Potential scope includes:

  • Products
  • Product components
  • Features
  • Releases
  • Customers
  • Usage
  • Product performance
  • Product documentation

Sales and Marketing

Data relating to customer acquisition, commercial activity, marketing activity, and business development.

Potential scope includes:

  • Leads
  • Opportunities
  • Prospects
  • Campaigns
  • Customers
  • Proposals
  • Sales activities
  • Marketing activities
  • Conversion
  • Revenue attribution

Organizational Operations

Data relating to the organization's internal processes and day to day operations.

Potential scope includes:

  • Processes
  • Activities
  • Procedures
  • Controls
  • Responsibilities
  • Service levels
  • Operational performance
  • Organizational workflows

Knowledge

Data and information representing organizational knowledge and institutional memory.

Potential scope includes:

  • Documents
  • Policies
  • Procedures
  • Meeting records
  • Decisions
  • Contracts
  • Proposals
  • Guidelines
  • Lessons learned
  • Institutional knowledge

Domain Boundaries

Domains provide context rather than ownership of the underlying ontology.

For example, Person is a core concept and may appear in:

People
Projects
Finance
Sales and Marketing
Organizational Operations
Knowledge

The concept remains the same even when its domain context changes.

Similarly, Metric may appear across:

Social Media
Observability
Finance
Projects
Products

The definition of the core concept remains common while individual metrics are domain specific.

Cross Domain Relationships

Organizational data is expected to cross domain boundaries.

For example:

Social Media
    ↓
Marketing Metrics
    ↓
Marketing KPI
    ↓
Organization

Observability
    ↓
System Metrics
    ↓
Operational KPI
    ↓
Product

Finance
    ↓
Revenue Metrics
    ↓
Financial KPI
    ↓
Product

Projects
    ↓
Project Metrics
    ↓
Project KPI
    ↓
Organization

These connections are a fundamental reason for maintaining a common organizational model.

Domain Evolution

Domains are expected to evolve.

A concept initially introduced within one domain may be promoted to the core ontology when it becomes broadly applicable.

Conversely, concepts that prove to be highly domain specific should remain within their domain.

The distinction between core and domain concepts is therefore based on semantic scope, not implementation convenience.

Domain Status

Domain Status Priority
Social Media Active Initial
Observability Planned High
Finance Planned High
People Planned Medium
Projects Planned Medium
Products Planned High
Sales and Marketing Planned High
Organizational Operations Planned Medium
Knowledge Planned High

This list is intentionally non exhaustive and will evolve with the organization's data and knowledge needs.