# Capability

**Status** Draft · **Version** 0.1 · **Updated** 20 July 2026 · **Doc ID** META-CAPABILITY-01 · **Definition ID** OCOM-DEF-0008 · **URI** `ocom:Capability`

Canonical: https://ocom.uno/vocabulary/capability

> The OCOM Specification defines Capability as — A Capability is a governed description of an ability possessed or provided by an Object.

## Definition

A Capability is a governed description of an ability possessed or provided by an Object. Capabilities represent potential functionality rather than specific executions. A Capability may be provided by one or more Objects and may support one or more business objectives.

## Purpose

This document defines Capability within the OCOM Specification. Capability represents the ability of an Object to perform, provide, enable, or support one or more organizational functions. Capabilities provide a technology-independent mechanism for describing what an Object can do without prescribing how it is implemented.

## Business meaning

Capabilities allow organizations to model operational abilities independently of organizational structure, implementation technologies, or execution mechanisms. They provide a stable representation of organizational functionality while implementations evolve over time.

## Design principles

Every Capability shall:

- describe an ability
- remain implementation independent
- support governance
- support reuse
- support interoperability
- remain technology independent

## Core characteristics

- Identifier
- Name
- Purpose
- Description
- Provider
- Consumer
- Constraints
- Policies
- Dependencies
- Maturity Level
- Availability

## Relationship to other specifications

Capability interacts with:

- [`ocom:Object`](/vocabulary/object)
- [`ocom:Relationship`](/vocabulary/relationship)
- [`ocom:Contract`](/vocabulary/contract)
- [`ocom:Policy`](/vocabulary/policy)
- [`ocom:Constraint`](/vocabulary/constraint)
- `ocom:Workflow`
- `ocom:Agent`
- `ocom:Tool`
- `ocom:Evaluation`

Capabilities describe potential abilities rather than operational execution.

## Referenced by

- [`ocom:Object`](/vocabulary/object)
- [`ocom:Contract`](/vocabulary/contract)
- [`ocom:Policy`](/vocabulary/policy)
- [`ocom:Constraint`](/vocabulary/constraint)

## Independence — does not prescribe

- organizational structures
- software architectures
- service models
- implementation technologies

## Conformance

A compliant implementation shall ensure that every managed Capability:

- define Capabilities explicitly
- preserve Capability traceability
- support governance
- support evaluation
- remain technology independent

## Provenance

Governance records: —

| Version | Date | Change |
| --- | --- | --- |
| 0.1 | 20 July 2026 | Initial draft |

## Recommended citation

OCOM Specification. Capability. META-CAPABILITY-01 (OCOM-DEF-0008). Version 0.1. https://ocom.uno/vocabulary/capability

---

Machine representations — JSON: https://ocom.uno/vocabulary/capability.json · JSON-LD: https://ocom.uno/vocabulary/capability.jsonld · Markdown: https://ocom.uno/vocabulary/capability.md · Source: https://github.com/DenisHogberg/OCOM/blob/main/docs/Meta/Capability.md · History: https://github.com/DenisHogberg/OCOM/commits/main/docs/Meta/Capability.md

Generated as a deterministic projection of one canonical record.