Documentation / Participate
Shared glossary
A compact vocabulary for consistent discussions.
Purpose
The metaphor helps explain the model. It does not replace an organisation’s terminology or assign human roles based on bee biology.
Ecosystem / Shared purpose
The boundary of collaboration: objectives, participating domains, common policies and accountable governance. Start with a use case and a named sponsor.
Hive / Business domain
A domain with an accountable owner, its own meaning and priorities. It coordinates its Cells while respecting the ecosystem’s minimum rules.
Cell / Business subdomain
A focused subdomain inside a Hive. Stewardship and engineering work close to the data. A Cell can own several data products; the Cell is not itself a product.
Comb / Business grouping
An optional grouping of Cells within the same Hive. A Cell may belong to several Combs. This is a business and permission grouping, not an extra infrastructure layer.
Data product / An accountable offering
A purposeful offering with a named owner, versioned contract, known consumers, quality expectations and a lifecycle. Tables, APIs and dashboards can be delivery interfaces.
Farm / Execution environment
Where products are cultivated and operated: production, test or development environments. The Farm is an execution boundary, distinct from business ownership.
Accountability
- Governance forum: Sets the baseline, reviews cross-domain exceptions and resolves conflicts.
- Ecosystem manager: Coordinates implementation, scope, policy versions and improvement follow-up.
- Domain owner: Accountable for the domain and escalated approval decisions.
- Subdomain owner: Accountable for the subdomain and its approval decisions.
- Data product owner: Owns purpose, contract, versions, publication and consumer relationships.
- Operational steward: Maintains meaning, classification and quality; reviews requests.
- Coordinating steward: Coordinates stewardship and resolves issues across Cells.
- Data engineering: Builds and maintains reproducible data preparation and delivery.
- Technical custodian: Operates environments and implements authorised controls.
- Consumer: Uses data within agreed terms and provides feedback on fitness for purpose.
Scope and limitations
KDV adds an original operating interpretation. DAMA-DMBOK and DCAM material is not redistributed. References do not imply endorsement, affiliation, certification or an official mapping.
Continue reading
Original KDV Framework knowledge. Working community edition 0.1. CC BY 4.0. References retain their owners’ rights; no official assessment or certification is implied.