Quick answer
Git compliance usually proves how code changed: branch protection, pull requests, signed commits, reviews, CI checks, deployment records, and repository audit logs.
Compliance Glossary proves how regulated terms are governed in Confluence: approved definitions, human review, version history, page-scan findings, and CSV evidence export.
Where Git evidence ends and Confluence terminology starts
| Evidence layer | Best source | What it proves |
|---|---|---|
| Code change history | Git / GitHub / GitLab / Bitbucket | Who changed code, when, through which branch, pull request, review, and CI process. |
| Release and deployment record | CI/CD and release tooling | Which approved artifact shipped, which checks passed, and which environment received it. |
| Policy and requirement meaning | Confluence | What terms such as control, incident, CAPA, deviation, validation, model, provider, or deployer mean in the organization. |
| Terminology approval evidence | Compliance Glossary | Which definitions are approved, who reviewed them, when they changed, and where pages still use unapproved wording. |
Search intents this page answers
git compliance
The user is looking for auditable repository controls. The terminology layer should not replace Git controls; it should complement them.
GitHub compliance audit trail
The user likely needs repository events, access controls, and review logs. Confluence adds the approved definitions used in the linked documentation.
GitOps compliance
The user wants compliance evidence from code-driven operations. Glossary governance keeps policy and control vocabulary stable around that evidence.
compliance as code
The user wants controls expressed in versioned systems. Terminology governance keeps the human-readable control language consistent.
signed commits compliance
The user is focused on identity and integrity. Glossary governance answers a different audit question: what did the controlled words mean at the time?
Git audit evidence
The user needs a clean evidence packet. Confluence glossary exports can sit beside Git logs, PR records, and CI reports.
Practical workflow before a native Git integration exists
- Keep Git as the code-change source. Use branch protection, reviews, signed commits where required, CI checks, and repository audit logs.
- Keep Confluence as the explanation source. Store SOPs, controls, risk notes, release criteria, validation notes, and audit narratives in Confluence.
- Govern terminology in Confluence. Approve terms such as incident, material change, validation, control owner, deployer, provider, CAPA, deviation, and risk owner.
- Scan Confluence pages for drift. Find outdated synonyms and unapproved wording before audit review.
- Export evidence separately. Attach Git evidence for code changes and Compliance Glossary CSV exports for terminology governance.
What Compliance Glossary can do today
Approved term records
Control definitions, synonyms, categories, status, and change reasons inside Confluence.
Four-eyes review
Require independent review before a definition becomes approved.
Page scanner
Detect undefined, deprecated, or unapproved terminology in Confluence pages.
Version history
Show what changed in a definition, when, and under which review history.
Requirements mapping
Map approved terms to frameworks such as SOC 2, ISO 27001, FDA, DORA, NIS2, and EU AI Act.
CSV evidence export
Export definitions, status, approval metadata, and version evidence for audit packets.
Related pages
Compliance for Confluence
The canonical page for Confluence compliance, audit evidence, and controlled terminology.
Security whitepaper
Forge architecture, data boundary, app permissions, and procurement disclosures.
Terminology management guide
How controlled vocabulary supports governance, quality, and audit evidence.
Govern the terms around your Git-controlled work.
Use Git for code-change evidence. Use Compliance Glossary in Confluence for approved terminology, review history, scanner findings, and CSV evidence export.