Flagship initiative
GBOK overview
The GIBA Book of Knowledge (GBOK) is a structured, vendor-neutral body of professional knowledge for the digital built environment. It is presented here from a controlled working draft.
What GBOK is
- A structured body of professional knowledge, organised as a stable architecture.
- Vendor-neutral and standards-informed, expressed in careful institutional language.
- A flagship initiative presented through — but broader than — a single publication.
What GBOK is not
- It is not a consulting methodology, delivery framework or software manual.
- It is not an approved or published standard — Blueprint v1.2 is a draft for board review.
- It is not a certification, and passing knowledge of it is not a credential.
A five-tier hierarchy
GBOK is organised as five nested tiers, so knowledge can be located, governed and versioned precisely:
- GBOK — the whole body of knowledge.
- Knowledge Family — a major field (the founding family is the Digital Built Environment).
- Domain — a coherent area within a family (Domain 1: Digital Built Environment Foundations).
- Chapter — a governed unit of knowledge within a domain.
- Section — the smallest addressable unit within a chapter.
Four architecture layers
GBOK is developed across four deliberately separated architecture layers — Knowledge, Competency, Certification and Governance. These are never merged: knowledge is not competence, competence is not a certificate, and none of them is the governance that keeps the others accountable. The architecture page explains each layer.
Development status
The current controlled draft is Blueprint v1.2 (Draft for Board Review). The founding Digital Built Environment family and Domain 1 architecture are indicative, pending ratification. No edition of GBOK is published, and nothing here should be treated as final.
Governance and contribution
GBOK develops under a documented change-control discipline. Contribution and review processes will be published as they are formalised; this website presents the architecture without publishing internal drafts.