GCBoK - The Normative Reference Work for Git-native Compliance
GitCover is not a tool for compliance enthusiasts. It is infrastructure for everyone who wants to get compliance done - as cheap, as secure, as demonstrable as possible.
The GitCover Body of Knowledge (GCBoK) is a normative reference work that canonises terms, concepts and architectural principles for Git-native Compliance. It is comparable to PMBOK (Project Management), SWEBOK (Software Engineering) and DMBOK (Data Management) - but with its own conceptual framework.
Positioning
| Characteristic | Value |
|---|---|
| Type | Body of Knowledge (BoK) - normative |
| Pattern | ISO/IEC 24773 (BoK structure as the basis for certification schemes) |
| Sponsor | GitCover Commons gUG (GCC) - non-profit |
| License | Targeted: CC BY-SA 4.0 |
| Versioning | Git (git.gitcover.org) - Git-native self-referential |
| URL | gcbok.org (Production) |
Overview of Chapters (Axes 1–14)
| Art. | Title (DE) | Title (EN) | Core Question |
|---|---|---|---|
| 01 | Grundlagen: Git-native Compliance Paradigma | Fundamentals: Git-native Compliance Paradigm | What is the fundamental architectural paradigm? |
| 02 | Konzepte: V7GUID, Beleg-Ketten, Cryptographic Evidence | Concepts: V7GUID, Evidence Chains, Cryptographic Evidence | How do the conceptual building blocks work? |
| 03 | Komponenten: Der GitCover Stack (GCDMS, GCPN, GCUCB, GCEP, GCSync, GCAL) | Components: The GitCover Stack | How is the technical stack structured? |
| 04 | Techniken: OSCAL, OPA, GPG, uuidV7, Gitea als IdP | Techniques: OSCAL, OPA, GPG, uuidV7, Gitea as IdP | Which techniques does GitCover use? |
| 05 | Vorgehensweisen: Onboarding, Audit-Readiness, GoBD, Jahresabschluss, NIS2, Risikoanalyse, KI-Integration | Procedures: Onboarding, Audit-Readiness, GoBD, Annual Accounts, NIS2, Risk Analysis, AI Integration | How does one proceed in practice? |
| 06 | Vorlagen: OSCAL-Katalog, OPA-Policy, V7GUID-Schema, DMS-Container | Templates: OSCAL Catalog, OPA Policy, V7GUID Schema, DMS Container | Which templates are available? |
| 07 | Governance: Satzung, Community Rules, Änderungsverfahren, Versionierung | Governance: Statutes, Community Rules, Amendment Procedures, Versioning | How is the project governed? |
| 08 | Schutzrechte: Patentanmeldefamilie und Gebrauchsmuster | IP Rights: Patent Family and Utility Models | Which IP rights exist? |
| 09 | Forschungsvorhaben: BSFZ-anerkanntes F&E-Vorhaben GitCover.IdP | Research Projects: BSFZ-recognised R&D Project GitCover.IdP | How is the research project structured? |
| 10 | Roadmap: Drei Phasen bis 2027 und Positionierung | Roadmap: Three Phases until 2027 and Positioning | How does the project develop? |
| 11 | Herausgeber und Träger: GitCover Commons gUG (GCC) | Publisher and Sponsor: GitCover Commons gUG (GCC) | Who is behind the GCBoK? |
| 12 | Quellen & Community | Sources & Community | Where can sources and community be found? |
| 13 | Namespace vs. V7GUID-Identität: Warum GitCover kein Identitätsmedium ist | Namespace vs. V7GUID Identity: Why GitCover is not an Identity Medium | How does GitCover differ from identity media? |
| 14 | Zertifizierung: Zertifizierungsschema und ISO/IEC 24773-Konformität (geplant) | Certification: Certification Scheme and ISO/IEC 24773 Conformance (Planned) | How is certification envisaged on the basis of the GCBoK? |
Context
The GCBoK main work is structured into 14 axes (chapters), which form the normative reference work for Git-native compliance. Each axis is a standalone document with the language variants de, en, es, fr and vi (German is authoritative; es/fr run with a DE fallback, the translation follows).
Status: All 14 chapters are created (de/en/es/fr/vi; German authoritative) — Chapter 14 is provisional (Phase 3 planning).