Relational Identifier (RID) Specification

Overview

UBKDS supports an optional Relational Identifier (RID) to link multiple authoritative artifacts that belong to the same knowledge set across different functional uses.

Purpose

The RID enables deterministic, machine-readable relationships between policies, procedures, training, metrics, and other artifacts without extending or altering the classification taxonomy.

RIDs exist to:

• Preserve meaning across systems
• Support reliable linking
• Enable automation and governance
• Prevent silent drift

Canonical Structure

The canonical RID format is:

###.#.XXXX

Components

###

UBKDS domain and sub-domain (meaning)

.#

Functional subcode (use)

.XXXX

Relational Identifier — a four-character alphanumeric code. Each character may be any letter (A–Z) or digit (0–9), providing up to 1,679,616 unique values per sub-domain. Valid values include 0003, 0A01, B10G, and ZZ99.

Default RID: 0000

The default RID is 0000. When artifacts within the same sub-domain share a natural functional relationship — but no explicit named knowledge set is required —0000 serves as the implicit shared identifier. No configuration is required to use the default.

Example — three artifacts in sub-domain 520 using the default RID

These artifacts are understood to be related by virtue of their shared sub-domain and default RID.

Named Knowledge Sets

When artifacts require an explicitly governed relationship — across sub-domains, or where more than one distinct knowledge set exists within a sub-domain — a non-default RID is assigned. Knowledge set identifiers must be unique within their scope.

Example — a named knowledge set using RID 0A01, spanning multiple sub-domains

All four artifacts live in different sub-domains yet share RID 0A01, indicating they are part of the same governed knowledge set.

Multiple RIDs per Artifact

An artifact may belong to more than one knowledge set and therefore carry more than one RID. When multiple RIDs are assigned, one must be designated the Primary RID.

The Primary RID determines which knowledge set governs this artifact's lifecycle. All other RIDs represent secondary membership and do not affect lifecycle behavior.

Primary Artifact and Lifecycle Coordination (Optional)

By default, each artifact manages its own lifecycle independently. However, when a knowledge set requires coordinated lifecycle management — such as ensuring a policy, its SOP, and its training module are reviewed and published together — one artifact within the set may be designated the Primary Artifact.

The Primary Artifact drives the lifecycle cadence for the entire knowledge set. When the Primary Artifact enters Revision or is Published, it signals the same transition for all artifacts sharing its Primary RID.

This is an optional governance model, not the default. It is intended for mature knowledge sets where tight lifecycle coordination adds clear operational value.

Optionality

• RID usage is optional
• Applied only when cross-artifact linkage is required
• Classification remains valid with or without an RID

Semantic Rules

• The RID identifies relationship, not order
• The RID carries no semantic meaning by itself
• The RID must never encode version, priority, or sequence

Canonical Rules

• RIDs are four-character alphanumeric codes (each character: A–Z or 0–9)
• The default RID is 0000
• RIDs are never sequential or time-based
• RIDs must not imply priority, order, or version
• An artifact may carry multiple RIDs; one must be designated Primary
• The Primary RID governs lifecycle coordination for that artifact
• A knowledge set may designate one artifact as its Primary Artifact to drive lifecycle for the entire set
• Lifecycle coordination via Primary Artifact is optional, not the default
• Knowledge set identifiers must be unique within their scope
• Classification codes never change due to RID usage

UBKDS codes classify knowledge. RIDs relate artifacts. The Primary RID can be used to coordinate their lifecycle.

Cross-References

• Canonical Domains
• Functional Subcodes
• Sensitivity Taxonomy
• Lifecycle Model
• Canonical Registry