- LEGAL_ENTITY.v7g.json: OSS reframed as normative root (kind: normative_root, parent: null, legalForm removed). Maintainer block added pointing to GCC (GitCover Commons gUG) as the legal entity maintaining the root. GCC's real company repos live on git.gitcover.de (not public .org). - others.json: tenant key -> root; legal_form null; maintained_by -> GCC. - README.md / README.en.md / dictionaries/README.md: "OSS-Tenant" -> "OSS (normative Root)" throughout; OSS clarified as no-parent normative root maintained by GCC, not a legal entity. - Spec (GITCOVER_PROTOCOL) and GCP.Questionnaire ADR-003 references updated in their respective working trees. Co-Authored-By: Claude <noreply@anthropic.com>
OSS/TOP — Central Normative V7GUID Registry (GitCover)
This repository (git.gitcover.org/OSS/TOP, local /mnt/brx5/work/OSS/TOP/) is
the central, normative single-source-of-truth (SSoT) home for V7GUID
dictionaries that apply across all GitCover tenant repos following the
GitCover / GCBoK concepts. It is coordinated with GCC (all GitCover modules
share the same meaning).
OSS is not a “tenant” in the usual sense — it is the normative root of the GitCover hierarchy (no parent), hosted as the Gitea org
OSSongit.gitcover.org. OSS holds all functional elements (tools/modules/features) and the central registries; the root is maintained by GCC (GitCover Commons gUG). GCC’s real, non-public company repos live ongit.gitcover.de.
🌐 Languages: Deutsch (default, authoritative) · English (translated). Gitea serves the variant matching your UI language (bottom-right “Select Language”); the default fallback is the German file (
README.md).
Contents
TOP/
└── .gitcover/
├── LEGAL_ENTITY.v7g.json # OSS normative-root identity (maintained by GCC)
├── others.json # root / endpoint / dictionary descriptor
└── dictionaries/
├── README.md # dictionary convention (de primary + en translated)
├── kinds.json # normative Kind enum (V7GUID bits 114–121, Layout v2)
└── status_flags.json # lifecycle bitmask (bits 106–113, Layout v2)
kind + status (Layout v2)
kinds.json classifies the art (kind) of a unit of work / activity — a
general, tenant-agnostic classification (undertaking, research chapter, work
package, routine, workflow, case processing, administration, companion effort,
IP administration, governance duties, primary employment, grant application,
routine software, project continuation, contract research, own work). It is
not tied to any one tenant’s filings; jurisdiction-specific notes
(e.g. German tax law FZulG/BSFZ) are kept in the optional jurisdiction_de
field and do not change the normative primary meaning.
status_flags.json defines the 8 combinable lifecycle flags (planned /
approved / developed / validated / released / accepted / archived / reserved)
as an O(1) bitmask filter directly from the GUID (e.g. status & 0x07 == 0x07
≡ planned+approved+developed).
Both dictionaries are bilingual (label_de primary / label_en
translated).
- Spec:
GITCOVER_PROTOCOL/specs/v7guid/33_kind.md,…/34_status.md - Spec-ADR:
GITCOVER_PROTOCOL/specs/v7guid/ADR-002_layout_v2_kind.md - Driver:
REPOS/AFJD/Tagebuch-Prompt.md
Git
- Object format: SHA256 (
git init --object-format=sha256). - Remote:
git-gcf@git.gitcover.org:OSS/TOP.git. Public mirror:codeberg.org/org/gitcover-commons.
Consolidation (follow-up slice)
The L1–L6 dictionaries currently remain in the CFP tenant
(REPOS/CFP/TOP/.gitcover/dictionaries/). Their migration into this OSS
normative root is a follow-up slice; until then CFP is the source for L1–L6
and OSS is the source for the new kind and status fields.