The UBKDS Standard
Purpose
UBKDS exists to provide a universal way to organize business knowledge so that:
- people can find what they need,
- organizations can govern what matters,
- and knowledge can transfer across roles, teams, and tools.
Core Principles
- Clarity over complexity
- If people can't apply it consistently, it's not a usable standard.
- Meaning must not depend on tools
- UBKDS must work across platforms.
- Governance is built in
- Structure should support ownership, review, and change.
- The system must be teachable
- A standard that can't be taught is not a standard.
Definitions (Canonical Terms)
- Standard
- A published set of definitions and rules intended to be used consistently across organizations.
- Canon / Canonical
- The authoritative set of definitions and rules as published on UBKDS.org.
- Classification
- The act of placing a knowledge item into a stable reference structure so its meaning is consistent and retrievable.
- Knowledge Item
- A discrete unit of business knowledge that can be owned, governed, referenced, and maintained (example types: policy, SOP, template, playbook, standard).
- Domain
- The subject area the knowledge item belongs to (what it is about).
- Sensitivity
- The access posture applied to the knowledge item (who can access it).
- Lifecycle
- The change posture applied to the knowledge item (what stage it is in).
- Stewardship Body
- The entity responsible for publishing and protecting the UBKDS canon, including versioning and governance rules.
The Three-Layer Model
UBKDS separates knowledge into three layers that must not be confused:
Domain Layer (Meaning)
The domain classification describes what the item is about. Domain should change rarely and only when the meaning truly changes.
Sensitivity Layer (Access)
Sensitivity describes who can access the item. Sensitivity must be implementable by groups by default. Individuals may be used when necessary or appropriate.
Lifecycle Layer (Change)
Lifecycle describes the item's current stage. Lifecycle creates a predictable path for drafting, publishing, reviewing, and retiring content.
Scope
UBKDS governs:
- the definition of the standard,
- canonical terms,
- the published structure,
- and the official version registry.
UBKDS does not govern:
- your internal tool choices,
- your internal implementation details,
- or your organization's proprietary content.
How to Adopt
Adoption is encouraged in a way that preserves meaning:
- Use the UBKDS structure.
- Reference the Canonical Registry.
- Do not claim compatibility with UBKDS unless your implementation respects the canon.