Tools and standards that belong to you.

Many GitCover projects are patent implementations and are released under free licenses. The sources are primarily hosted on our own Gitea servers (git.gitcover.org/OSS), mirrored on Codeberg (codeberg.org/org/gitcover-commons) and on GitHub (github.com/gitcover-commons). They are based on the IP and licensing strategy for GitCover (Apache 2.0, CC0/CC-BY, etc.), with the goal of remaining completely free of license costs and ensuring open development.

GitCover Core — license: Apache 2.0; status: in preparation · Alpha from September 2026; repo: https://git.gitcover.org/OSS/core; repo_label: → Sources on Gitea: Git-native framework for compliance management. Provides the fundamental data structures, validators and audit trail components. Core idea: every record, every process receives a time-ordered UUIDv7 plus a GCPN-compliant, deterministic path.
GoBD Modules — license: Apache 2.0; status: concept · Beta Q4/2026; repo: https://git.gitcover.org/GCC/gobd; repo_label: → Sources on Gitea: Immutable journals, automatic audit logs and tax audit exports. Extends GitCover Core with GoBD-specific tools (immutability, traceability, completeness pursuant to § 146 AO).
OSCAL Toolchain — license: Apache 2.0; status: concept · Beta Q4/2026; repo: https://git.gitcover.org/GCC/oscal; repo_label: → Sources on Gitea: Parsers, converters (OSCAL ↔ JSON/XML/YAML) and dashboards. BSI IT-Grundschutz++ modules and GDPR PII management (Art. 30 GDPR). Goal: machine-readable compliance requirements, verifiable by external auditors.
GCUCB · GitCover Unified Context Bus — license: CC0; status: research concept · BSFZ research module 2026–2028; repo: https://git.gitcover.org/GCC/gcucb; repo_label: → Research documentation on Gitea: Shared-memory-based context bus with V7GUID addressing as the central data hub between AI agents, compliance validators (OPA/OSCAL) and audit systems. Eliminates repeated serialization/deserialization ("semantic re-parsing") through typed direct access to Git-versioned schemas (NativeAOT/codegen). Three research questions: Can the V7GUID bus measurably reduce IPC overhead in AI compliance workflows? Can zero-copy accessor code be generated automatically from Git schemas? Does a typed context bus improve the quality of LLM outputs?
V7GUID · Version 7 Git Universal Identifier — license: CC0; status: specification · Draft; repo: https://git.gitcover.org/GCC/v7guid; repo_label: → Specification (IETF track): Universally unique, time-ordered identifiers with built-in business context hierarchy (Entity → Department → Category → SubCategory → ProcessType → Instance). Extends RFC 9562 (UUIDv7) with compliance-relevant structures. Time epoch model real · tenant · person (OSS schema v7guid-epoch-mode-1.0): The RFC prefix (timestamp + version + variant) remains the normative root interface, the suffix carries the classification (registry/keyword search) — this also allows historical person times (pre-1970, e.g. birth dates) to be represented sortably and in compliance with the RFC format; time values before the epoch are a defined error (no sign wrap). Standard division: RFC 9562 standardizes the structure (bit layout/version/variant), GCBoK standardizes the semantics (time epoch, classification).
GCEP · GitCover Exchange Protocol — license: CC0; status: specification · Draft; repo: https://git.gitcover.org/GCC/gcep; repo_label: → Specification (IETF track): Protocol for the secure exchange of signed compliance records between Git repositories. Enables federated audit trails without a central trust authority.