# Constraint

**Status** Draft · **Version** 0.1 · **Updated** 20 July 2026 · **Doc ID** META-CONSTRAINT-01 · **Definition ID** OCOM-DEF-0011 · **URI** `ocom:Constraint`

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

> The OCOM Specification defines Constraint as — A Constraint is a governed condition that restricts or requires specific characteristics, states, or behaviors.

## Definition

A Constraint is a governed condition that restricts or requires specific characteristics, states, or behaviors. Constraints may apply to individual Objects, Relationships, Workflows, Contracts, Policies, or other managed elements. A Constraint defines *what must remain true* rather than *how it is enforced*.

## Purpose

This document defines Constraint within the OCOM Specification. A Constraint establishes conditions or limitations that govern the structure, behavior, or interactions of Objects. Constraints ensure consistency, integrity, and compliance throughout the OCOM ecosystem.

## Business meaning

Constraints protect operational integrity by ensuring that organizational rules and business requirements are consistently respected. They reduce ambiguity, prevent invalid operations, and improve interoperability across organizational systems.

## Design principles

Every Constraint shall:

- define explicit conditions
- be verifiable
- support governance
- preserve consistency
- support traceability
- remain technology independent

## Core characteristics

- Identifier
- Name
- Purpose
- Scope
- Description
- Severity
- Effective Period
- Exception Policy
- Related Policies
- Evaluation Criteria

## Relationship to other specifications

Constraint interacts with:

- [`ocom:Object`](/vocabulary/object)
- [`ocom:Policy`](/vocabulary/policy)
- [`ocom:Contract`](/vocabulary/contract)
- `ocom:Workflow`
- `ocom:Lifecycle`
- [`ocom:Capability`](/vocabulary/capability)
- `ocom:Evaluation`
- `ocom:Governance`

Constraints define operational limitations without prescribing implementation.

## Referenced by

- [`ocom:Object`](/vocabulary/object)
- [`ocom:Relationship`](/vocabulary/relationship)
- [`ocom:Capability`](/vocabulary/capability)
- [`ocom:Contract`](/vocabulary/contract)
- [`ocom:Policy`](/vocabulary/policy)

## Independence — does not prescribe

- validation engines
- rule languages
- workflow systems
- implementation technologies

## Conformance

A compliant implementation shall ensure that every managed Constraint:

- define Constraints explicitly
- support evaluation
- preserve governance
- maintain auditability
- remain technology independent

## Provenance

Governance records: —

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

## Recommended citation

OCOM Specification. Constraint. META-CONSTRAINT-01 (OCOM-DEF-0011). Version 0.1. https://ocom.uno/vocabulary/constraint

---

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

Generated as a deterministic projection of one canonical record.