# Compliance Glossary for Confluence: complete public guide Last verified against production v6 on 2026-09-26. ## How do teams freeze and trace Confluence evidence? URL: https://compliance-glossary.teamkit.dev/ Compliance Glossary freezes approved meanings, exact Confluence revisions, hashes, usages, findings, coverage, and governed trace links in a fixed evidence baseline. Teams can verify the package, search indexed evidence, calculate change impact, follow provenance in both directions, export a verifiable archive, and prepare external reissue handoffs. ## About DailyMind LTD URL: https://compliance-glossary.teamkit.dev/about DailyMind LTD (HE 439959) — Cyprus-based EU vendor behind Compliance Glossary for Confluence. Terminology governance for AI Act, GDPR, NIS2, DORA teams. ## Assistive Editing or AI-Generated Content? Article 50 Decision Guide URL: https://compliance-glossary.teamkit.dev/ai-act-article-50-assistive-editing-decision-guide A practical Article 50 decision guide for document AI teams assessing assistive editing, semantic alteration, summarizers, translators, and drafting tools. ## Article 50 for Document AI Teams URL: https://compliance-glossary.teamkit.dev/ai-act-article-50-document-ai A practical Article 50 hub for document AI teams: inventory, applicability assessment, and provider vs deployer duty ownership. ## EU AI Act Article 50 Inventory for Document AI Teams URL: https://compliance-glossary.teamkit.dev/ai-act-article-50-inventory-document-ai Build an Article 50 inventory for document AI: systems, roles, triggers, exceptions, marking controls, contracts, and evidence links. ## AI Act Article 50 Provider vs Deployer Duties for SaaS Teams URL: https://compliance-glossary.teamkit.dev/ai-act-article-50-provider-deployer-duties Map Article 50 provider and deployer duties for SaaS document AI: marking, disclosure, customer publication, contracts, and evidence ownership. ## AI Act 2026 CEO Calendar After the AI Omnibus URL: https://compliance-glossary.teamkit.dev/ai-act-aug-2026-ceo-deadline What still matters for CEOs in 2026 after the AI Omnibus: Article 50 transparency, GPAI enforcement, and high-risk planning for 2027/2028. ## AI Act Enforcement 2026: Why the CFO Signs Off on "High-Risk AI System" Definitions URL: https://compliance-glossary.teamkit.dev/ai-act-cfo-2026-enforcement EU AI Act 2026 CFO risk after AI Omnibus: Article 50, GPAI enforcement, Article 99 fines, and high-risk planning for 2027/2028. ## AI Act / DORA Controlled Definitions Checklist URL: https://compliance-glossary.teamkit.dev/ai-act-dora-controlled-definitions-checklist A 9-step checklist for turning AI Act and DORA Article 3 definitions into a controlled glossary with ownership and audit evidence. ## How can legal teams govern AI Act terminology? URL: https://compliance-glossary.teamkit.dev/ai-act-glossary-for-legal-teams Legal teams can use Compliance Glossary to control AI Act terms in Confluence, not to make legal determinations. Start from the current EUR-Lex text. Install the EU AI Act pack as drafts. Assign owners, complete four-eyes review, scan pages for misuse, and freeze the reviewed state. Add evidence links where required. Counsel still decides scope, role, classification, obligations, and acceptable wording. ## The EUR 140,000 AI Act Fine That Ends the Startup URL: https://compliance-glossary.teamkit.dev/ai-act-startup-existential-fine AI Act Article 99(6): a EUR 2M-revenue AI startup faces a EUR 140,000 Tier 1 cap. For a pre-revenue founder, that is the company. ## EU AI Act Terminology Governance — Article 3 Definitions URL: https://compliance-glossary.teamkit.dev/ai-act-terminology-governance EU AI Act Article 3 defines 68 terms. Build terminology governance in Confluence for Article 50, GPAI, and high-risk readiness after the AI Omnibus. ## EU AI Act Glossary for Confluence URL: https://compliance-glossary.teamkit.dev/ai-act EU AI Act Article 3: 68 legal definitions. Article 50 and GPAI enforcement still matter in 2026; high-risk dates need AI Omnibus caveats. ## AI-assisted curation: planned, optional, and human-governed URL: https://compliance-glossary.teamkit.dev/ai-assisted-curation A transparent description of the planned, optional AI-assisted curation capability for Compliance Glossary for Confluence. ## How to Build an AI Policy Glossary in Confluence URL: https://compliance-glossary.teamkit.dev/ai-policy-glossary-confluence-legal Build an AI policy glossary in Confluence with approved terms, source clauses, owners, scanner checks, review history, and exportable evidence. ## AI Securities Class Actions: CEO Naming Risk URL: https://compliance-glossary.teamkit.dev/ai-securities-class-action-ceo Review sourced data on AI-related securities class actions, CEO and CFO naming risk, disclosure failures, and governance evidence. ## AI Use-Case Inventory Terms for Legal Intake URL: https://compliance-glossary.teamkit.dev/ai-use-case-inventory-legal-intake-glossary Govern AI-system, use-case, intended-purpose, provider, deployer, risk, and evidence terms for legal intake inside Confluence. ## AI Vendor Due Diligence Glossary for Legal and Procurement URL: https://compliance-glossary.teamkit.dev/ai-vendor-due-diligence-glossary Align legal, procurement, privacy, and security teams on controlled AI vendor due-diligence terms, sources, reviews, and evidence. ## AI Washing CEO Criminal Liability: Raz, Saniger, and 20 Years URL: https://compliance-glossary.teamkit.dev/ai-washing-ceo-criminal-liability SEC and DOJ AI-washing source check for CEOs: Joonko/Raz, Nate/Saniger, charging status, requested relief, and governance evidence limits. ## AI Washing SEC Enforcement: CFO Disclosure Controls URL: https://compliance-glossary.teamkit.dev/ai-washing-cfo-disclosure AI washing disclosure risk for CFOs: SEC/DOJ Saniger, SEC Raz, Cornerstone 2025 AI securities filings, SOX 302/906 limits, and source-checked controls. ## ALCOA+ Principles for Terminology Management URL: https://compliance-glossary.teamkit.dev/alcoa-plus Apply ALCOA+ principles to controlled terminology in Confluence with attribution, approval history, change reasons, page scans, and CSV evidence. ## EU Annex 11 Terminology for Confluence URL: https://compliance-glossary.teamkit.dev/annex-11-terminology EudraLex Annex 11 terminology for Confluence: computerised system validation terms, audit trails, approvals, and compliance scanning for EU GMP teams. ## App Limitations URL: https://compliance-glossary.teamkit.dev/app-limitations Transparent documentation of system limits, platform constraints, and compliance scope for Compliance Glossary for Confluence. ## AppFox Approvals signs off pages; Compliance Glossary governs the terms inside them. URL: https://compliance-glossary.teamkit.dev/appfox-approvals-vs-compliance-glossary A fair AppFox Approvals vs Compliance Glossary comparison for regulated Confluence teams deciding between page sign-off routing and controlled term definitions with approval evidence, version history, scanner findings, and CSV export. ## Workflows for Confluence routes documents through review; Compliance Glossary controls the vocabulary they rely on. URL: https://compliance-glossary.teamkit.dev/appfox-workflows-vs-compliance-glossary A fair Workflows for Confluence (AppFox) vs Compliance Glossary page for regulated teams deciding between document approval routing and term-level governance with approval evidence and audit-ready export. ## Approval Path proves a page version was signed off; Compliance Glossary provides term-level approval and scan evidence. URL: https://compliance-glossary.teamkit.dev/approval-path-vs-compliance-glossary A fair Approval Path for Confluence vs Compliance Glossary page for teams deciding between page sign-off workflows and controlled terminology governance with exportable evidence. ## ApprovalFlow approves page versions; Compliance Glossary approves the definitions those pages depend on. URL: https://compliance-glossary.teamkit.dev/approvalflow-vs-compliance-glossary A fair ApprovalFlow for Confluence vs Compliance Glossary page for regulated teams deciding where approval should bind: page versions, or term definitions and scanner evidence across pages. ## Do suggested links count as evidence? URL: https://compliance-glossary.teamkit.dev/approved-vs-candidate-trace-links No. A candidate trace link is review-only and does not count as governed evidence. Compliance Glossary includes imported and approved links in evidence traversal. Rejected links appear in neither the governed set nor the candidate set. The Enterprise evidence workspace displays retained governed hops, while unapproved endpoints can create a Coverage blockers warning. ## What is a glossary slice? URL: https://compliance-glossary.teamkit.dev/artifact-specific-glossary-slice A glossary slice is the frozen subset of approved meanings used by one retained artifact. Production v6 derives it from indexed usage evidence in a deposited baseline. The slice includes the artifact hash, archive reference, meanings, usages, counts, and its own SHA-256 value. It is not the organization's full glossary. ## Audit Committee Scrutiny in 2026: The Controls Artifacts CFOs Should Bring URL: https://compliance-glossary.teamkit.dev/audit-committee-cfo-evidence PwC 2025 finds 55% of directors want a colleague replaced, the highest ever. KPMG's 2025 agenda expands to AI, cyber, and compliance. ## AURA Workflow & Approval governs a page's lifecycle; Compliance Glossary governs the terms on every page. URL: https://compliance-glossary.teamkit.dev/aura-workflow-approval-vs-compliance-glossary AURA Workflow & Approval for Confluence runs page lifecycle workflows: states, approvals, publishing, permissions, and automations. Compliance Glossary governs the controlled terms and definitions used across many pages — different jobs, complementary tools. ## Are pages scanned after edits? URL: https://compliance-glossary.teamkit.dev/automatic-terminology-scan-confluence Yes. Confluence page creation and update events start an automatic terminology check. The app first marks the older page result stale. It applies a five-minute per-page debounce and scans the current page. Findings stay within the page’s effective glossary. The app saves findings, approved usage, page version, and scan time. Failures remain logged. ## What does conformance show? URL: https://compliance-glossary.teamkit.dev/baseline-conformance-report Conformance shows whether recorded evidence matches the deposited baseline. The report gives the baseline an overall status: conformant, incomplete, or nonconformant. It also preserves each artifact’s checks, conflicts, unresolved checks, and coverage reasons. Availability remains a separate field. An unavailable record is not presented as a verified match or silently merged with a nonconforming result. ## What are coverage blockers? URL: https://compliance-glossary.teamkit.dev/baseline-coverage-blockers Coverage blockers show where Compliance Glossary cannot present a complete evidence view. They identify bounded query gaps, missing or unapproved graph nodes, and unavailable evidence. The workspace marks results as partial while a blocker remains. Review each blocker before using the view for an audit, release handoff, or incident analysis. ## How do retention and legal hold work? URL: https://compliance-glossary.teamkit.dev/baseline-retention-and-legal-hold Administrators record a retention class, a Retain until date, and an optional Legal hold when creating an enterprise freeze. Missing retention data blocks capture. An active hold blocks deletion after the date passes. Compliance Glossary enforces the recorded state. Your organization remains responsible for the lawful duration, hold decision, and release process. ## Which app fits terminology evidence? URL: https://compliance-glossary.teamkit.dev/best-confluence-compliance-apps Choose Compliance Glossary when the controlled object is a term: its approved meaning, history, page usage, findings, and frozen evidence. Choose a page-approval app for sign-off, document control for lifecycle states, requirements software for traceability matrices, and audit management for audit programs. No single app covers these jobs. Start with the evidence object your reviewer must inspect. ## Board Regulatory Disclosure: The CEO Credibility Test URL: https://compliance-glossary.teamkit.dev/board-regulatory-disclosure-ceo 64% of CEOs call regulation the #1 barrier (PwC). Only 14% have appropriate AI controls (EY Aug 2025). One audit-trail artifact answers the board's AI... ## Can I add CAD files? URL: https://compliance-glossary.teamkit.dev/cad-file-compliance-evidence Yes, as metadata-only evidence. Production v6 accepts allow-listed DWG, DXF, STEP, STP, STL, IGES, and IGS files when extension and MIME type match. It records the file hash, revision, provenance, format metadata, retention, and declared candidate links. It does not interpret geometry, design intent, or CAD semantics. ## CEO Forced Exit: What the Spencer Stuart and Russell Reynolds Data Actually Say URL: https://compliance-glossary.teamkit.dev/ceo-forced-exit-compliance Spencer Stuart 2024: 8% of S&P 1500 CEO transitions were forced. More than 100 activist campaigns since 2018 targeted CEOs. ## Changelog URL: https://compliance-glossary.teamkit.dev/changelog Release history and changelog for Compliance Glossary for Confluence. Track new features, improvements, and fixes. ## Which problem does each app solve? URL: https://compliance-glossary.teamkit.dev/comala-vs-compliance-glossary Comala Document Management centers document lifecycle workflows, reviews, approvals, publishing, and related page controls. Compliance Glossary centers governed terminology, usage scanning, frozen evidence, impact, and traceability. They address different control layers. A team may need one, the other, or both, based on whether the core problem is document state or terminology evidence. ## Regulatory Compliance Deadlines — 2026–2028 Calendar for Regulated Teams URL: https://compliance-glossary.teamkit.dev/compliance-calendar Track key dates for the EU AI Act, DORA, NIS2, FDA QMSR, EU CRA, and Product Liability Directive with sourced compliance milestones. ## Compliance Documentation Checklist URL: https://compliance-glossary.teamkit.dev/compliance-documentation-checklist A practical compliance documentation checklist covering what auditors look for across SOC 2, ISO 27001, FDA, and EU regulations. Use it before your audit. ## What happens when links form a cycle? URL: https://compliance-glossary.teamkit.dev/compliance-evidence-graph-cycles Production v6 keeps cyclic relationships visible and bounds their traversal. The graph walk records an edge that returns to a visited node as a cycle. It does not enqueue the node again. Direction, hop limits, result limits, and visited-node tracking prevent an endless query while preserving the relationship for review. ## Can Confluence support controlled terminology evidence? URL: https://compliance-glossary.teamkit.dev/compliance-for-confluence Yes. Compliance Glossary adds governed term records, review, scanning, frozen baselines, impact analysis, traceability, and verifiable exports to Confluence. It helps teams preserve what a term meant, where it appeared, what changed, and which governed evidence supports a decision. It does not turn Confluence into a QMS. ## Which features are included in v6? URL: https://compliance-glossary.teamkit.dev/compliance-glossary-features Yes. Production v6 includes term governance, scoped Confluence scanning, approved-term macros, readiness mapping, baselines, evidence exports, and cross-space subscriptions. Optional administrator tools add GitHub findings, offline manifests, file evidence, trace views, archive operations, and draft-only AI curation. Each feature has explicit scope and limits. The app produces evidence; it does not certify compliance. ## Where is evidence stored? URL: https://compliance-glossary.teamkit.dev/compliance-glossary-forge-data-storage Production v6 stores terminology and scan records in Forge KVS. It uses tenant-scoped Forge SQL for indexed enterprise evidence and Forge Object Store for frozen content, archive parts, and manifests. The deployed manifest also includes an LLM module and GitHub backend egress. Deployment confirms availability, not staging qualification, measured capacity, physical residency, or legal immutability. ## How does Compliance Glossary handle GDPR data rights? URL: https://compliance-glossary.teamkit.dev/compliance-glossary-gdpr-data-rights Compliance Glossary reports stored Atlassian account identifiers to Atlassian’s privacy service each week. When Atlassian returns a closed status, production v6 replaces covered actor references and removes that account from the app administrator list. Governed records remain intact. This is targeted actor-reference replacement, not a promise to delete every record or complete every GDPR request automatically. ## What happens when the license is inactive? URL: https://compliance-glossary.teamkit.dev/compliance-glossary-license-behavior Administrative and evidence workflows stop when the production license is inactive. Production resolvers fail closed before governed writes, scans, exports, connector work, or enterprise evidence operations. The narrow continuity exception is approved read-only glossary macro content. Existing page and inline macros can keep showing approved terms without enabling administration. ## What does Compliance Glossary not do? URL: https://compliance-glossary.teamkit.dev/compliance-glossary-limitations Compliance Glossary does not certify compliance, approve releases, execute electronic signatures, replace a QMS, provide legal WORM storage, or interpret CAD and PDF semantics. It governs terminology and preserves bounded evidence within defined controls. Verification detects changes to recorded evidence. It does not prove source correctness, legal validity, or production capacity at unmeasured scale. ## Can Compliance Glossary support 200,000 pages? URL: https://compliance-glossary.teamkit.dev/compliance-glossary-scale-limits Not as a verified Forge production claim. Compliance Glossary has no measured result for 200,000 Confluence pages. A local deterministic simulation processed 250,000 mixed artifacts across eight classes. One class represented Confluence documents. It recorded recovery and modeled resource signals. It did not measure Forge latency, consumption, cost, data residency, or tenant throughput. Production capacity remains unqualified. ## Compliance Guide URL: https://compliance-glossary.teamkit.dev/compliance-guide Real audit control weaknesses that auditors flag in terminology management — and how Compliance Glossary for Confluence addresses each one. ## Turn glossary cleanup into audit-ready terminology evidence. URL: https://compliance-glossary.teamkit.dev/compliance-terminology-templates Use these templates to find terminology drift, start a controlled vocabulary, and prepare evidence questions before a SOC 2, ISO, FDA, DORA, NIS2, GDPR, or AI Act review. ## Can AI draft glossary terms? URL: https://compliance-glossary.teamkit.dev/confluence-ai-assisted-term-drafts Yes. In production v6, a user with term-management access can generate editable candidate previews from selected undefined-term findings. Forge LLM uses bounded, redacted evidence from current Confluence page revisions. A preview becomes a normal Draft only after human review, scope selection, and explicit creation. AI cannot approve, publish, overwrite a term, or change a Confluence page. ## Native Confluence approvals sign off pages; Compliance Glossary controls the regulated terms inside them. URL: https://compliance-glossary.teamkit.dev/confluence-approvals-vs-compliance-glossary Native Confluence approvals handle page-level sign-off. Compliance Glossary governs the controlled terms and definitions inside those pages: approval evidence, scanning, and export. ## What can I export for an auditor? URL: https://compliance-glossary.teamkit.dev/confluence-audit-evidence-export Production v6 exports supported terminology governance and scanner records for the selected scope and period. Available evidence can include terms, version history, approvals, findings, resolutions, scan history, page status, usage, and scope-register context. Enterprise baselines and archives provide separate frozen package evidence. The export supports review; it does not run the audit. ## What audit evidence does the app produce? URL: https://compliance-glossary.teamkit.dev/confluence-audit-evidence Compliance Glossary produces four evidence layers. Version History records governed term decisions. Compliance Scanner records page status, findings, resolutions, and scan history. Terminology Baseline freezes term and scanned-page state for comparison. Enterprise evidence workspace adds hashes, verification, trace links, conformance, and portable archives. These records support an audit; they do not perform one or certify compliance. ## How do I explain a finding to an auditor? URL: https://compliance-glossary.teamkit.dev/confluence-audit-finding-response Use the finding record as the response spine. In Compliance Scanner, record status, owner, due date, severity, justification, and closure evidence. The app stores the page ID, term ID, actor, and decision time. Re-scan after remediation. Then generate an Audit Evidence Package so the auditor can correlate the resolution with page status and retained scan history. ## Which content is included in Confluence audit evidence? URL: https://compliance-glossary.teamkit.dev/confluence-audit-scope Audit scope is the evidence boundary you declare and then validate against recorded coverage. In Audit Scope Register, name included and excluded spaces, pages, repositories, and paths. Add Glossary revision, Last scan timestamp, and Scope notes. Then compare the declaration with Space Pages Status and baseline coverage. Declared fields do not enforce page, repository, or path filtering. ## What can a Confluence board compliance posture report show? URL: https://compliance-glossary.teamkit.dev/confluence-board-compliance-posture-report A board posture report can summarize recorded glossary governance, requirement coverage, page-scan evidence, gaps, and follow-up work. Use Dashboard for term status, Requirements Mapper for mapped-term readiness, and Audit Evidence Package for scoped evidence. Report the period and limits with every number. These operational signals support oversight. They do not certify compliance or replace management judgment. ## Can I update many terms at once? URL: https://compliance-glossary.teamkit.dev/confluence-bulk-term-management Yes. Administrators can process up to 100 terms per bulk operation. Filter to one status, select records, and use Submit for Review, Approve Selected, Deprecate Selected, or Delete Selected. Every action requires one change reason and writes a version before changing the term. Approval still enforces four-eyes separation. Ineligible records are skipped with errors. ## How do I show that a Confluence page has no current terminology findings? URL: https://compliance-glossary.teamkit.dev/confluence-clean-page-terminology-status A current Passed status shows that a completed scan found zero terminology findings for the recorded page version and Glossary Revision. Confirm the row in Space Pages Status, including Findings, Version, and Last Scanned. If the page changes, its status becomes Stale until another scan. This result does not promise that future edits remain clean. ## How does the app support compliance documentation? URL: https://compliance-glossary.teamkit.dev/confluence-compliance-documentation Compliance Glossary supports compliance documentation by governing shared terminology and preserving connected evidence. Teams can review definitions, scan usage, freeze exact page revisions, verify deposited packages, trace approved relationships, and export records. The organization still owns document authorship, legal interpretation, page approval, release decisions, and controlled issuance. ## What does Compliance Glossary for Confluence do? URL: https://compliance-glossary.teamkit.dev/confluence-compliance-glossary-app Production v6 governs terms, separates editing from approval, scans Confluence pages, publishes approved definitions, maps required terms, and exports audit records. It also includes legacy baselines and an enterprise workspace for exact revisions, traceability, verification, archives, file evidence, and external handoffs. Deployment is confirmed. Forge staging qualification, measured capacity, residency, certification, release approval, signatures, and QMS replacement are not established. ## How to Use Confluence for Regulatory Compliance Documentation URL: https://compliance-glossary.teamkit.dev/confluence-compliance-guide Confluence Cloud holds SOC 2, ISO 27001, and FedRAMP certifications, but native features miss approval workflows and terminology control. Bridge the gap. ## Does the app replace document control? URL: https://compliance-glossary.teamkit.dev/confluence-controlled-documentation No. Compliance Glossary does not replace document control. It governs terminology, scans usage, preserves exact evidence, calculates impact, and prepares external reissue handoffs. A document-control or quality system still owns document approval, issuance, effective dates, distribution, signatures, training, and withdrawal under the organization's controlled process. ## How do I manage a controlled vocabulary in Confluence? URL: https://compliance-glossary.teamkit.dev/confluence-controlled-vocabulary Create each controlled term as a governed record with a required name and definition. Scope it to one space or All spaces. Add category, synonyms, owner, review dates, and notes as needed. Move it from Draft to In Review, then have a different eligible administrator approve it. Only Approved terms appear in the page glossary and inline term macros. ## How do I map terms across regulations? URL: https://compliance-glossary.teamkit.dev/confluence-cross-regulation-term-mapping Use Regulation Requirements Mapper to select a regulation and, when needed, a Consumer Space. The app matches each required term against glossary names and synonyms. Its Term Mapping table keeps the source controls visible. When a required term belongs to multiple catalogs and matching glossary records have different definitions, Cross-Regulation Definition Conflicts shows each record without changing either meaning. ## Can one space use terms from another? URL: https://compliance-glossary.teamkit.dev/confluence-cross-space-glossary-subscriptions Yes. A term manager can let one team or project space reuse approved terms from selected source spaces. In Settings, choose the consumer under Space that will use shared terms, select Spaces to read approved terms from, then save. The effective glossary contains global terms, the consumer’s own terms, and direct source-space terms. Page macros and scans use that scope. ## What happens during the first scan? URL: https://compliance-glossary.teamkit.dev/confluence-first-run-terminology-scan The first completed scan establishes page coverage for the selected Confluence space and records supported terminology findings. When the effective glossary is empty, production v6 can surface undefined candidate terms for review. Candidates are not approved glossary entries. Term managers must review, edit, and submit useful candidates through the normal workflow. ## What does the activity log record? URL: https://compliance-glossary.teamkit.dev/confluence-glossary-activity-log The activity log records supported governed actions available to the app, including who acted and when. It helps administrators review recent operational activity. For content-level evidence, open the related term history and exact version. The log does not capture decisions made only in email, external systems, or unsupported Confluence actions. ## How do I import glossary terms from CSV? URL: https://compliance-glossary.teamkit.dev/confluence-glossary-csv-import Open Terms, select Import CSV, and upload a structured glossary file. Production v6 validates headers, row limits, field lengths, duplicates, and supported values before creating governed records. Imported terms do not bypass review. Teams must inspect validation results, correct rejected rows, and approve accepted content through the normal workflow. ## How do I publish a glossary on a page? URL: https://compliance-glossary.teamkit.dev/confluence-glossary-macro Insert the Compliance Glossary macro on a Confluence space page. It shows approved terms visible to that space. This includes terms from the page space, global scope, and subscribed source spaces. Readers see each term’s name, category, synonyms, definition, and notes. They can search the list or filter it by category. ## How do I show one term inline? URL: https://compliance-glossary.teamkit.dev/confluence-inline-glossary-term Add the Compliance Glossary inline macro and select one approved, effective term from the page's available glossary scope. Readers see the term in context and can open its current definition. The macro is read-only. It does not approve terms, freeze a historical meaning, or replace release-bound baseline evidence. ## What should security teams review? URL: https://compliance-glossary.teamkit.dev/confluence-procurement-security-review Security teams should review Forge permissions, Confluence read scopes, storage, GitHub egress, data types, retention, roles, licensing, upload limits, and failure handling. They should also confirm product boundaries. These include no certification, legal WORM storage, release approval, or signature execution. ## What are regulation packs? URL: https://compliance-glossary.teamkit.dev/confluence-regulation-packs Regulation packs are starter collections of terminology that administrators can add as drafts. They reduce initial data entry for supported compliance topics. Every imported meaning still needs contextual review and normal approval. A pack is not legal advice, a compliance determination, a certification, or proof that every required term is present. ## Who owns terminology remediation? URL: https://compliance-glossary.teamkit.dev/confluence-remediation-ownership Assign page-correction work to the responsible content owner and keep term approval with permitted term managers. Production v6 supports finding ownership and governed term roles as separate concerns. This separation prevents a page owner from silently changing the approved meaning while still making remediation responsibility visible. ## What does the requirements mapper do? URL: https://compliance-glossary.teamkit.dev/confluence-requirements-mapper The requirements mapper links recorded internal evidence to supported catalog requirements and shows current recorded readiness and gaps. It helps teams organize evidence by control or requirement. It does not decide legal applicability, certify compliance, or prove that a mapped record is sufficient. Qualified owners must review every mapping and gap. ## How do I prioritize findings in a space? URL: https://compliance-glossary.teamkit.dev/confluence-space-remediation-queue Open Space Remediation Queue for the selected space. Production v6 combines stored page findings with resolution records, sorts unresolved work first, and shows page, term, finding type, status, and owner. Filter by status or page text, assign responsibility in the finding, then rescan after underlying corrections. ## What is the term lifecycle? URL: https://compliance-glossary.teamkit.dev/confluence-term-lifecycle-management Every new term starts as Draft. An administrator can Submit it for review. A separate administrator can Approve it or Reject it to Draft. An Approved term can be sent for review or deprecated. A Deprecated term can be reactivated for review. Each transition records a new version, actor, time, status, and required reason. ## Who can manage glossary terms? URL: https://compliance-glossary.teamkit.dev/confluence-term-manager-rbac Configured Term Managers (RBAC) can perform governed term administration. Production resolvers check the authenticated account, active license, and configured role before protected actions. Four-eyes rules still separate approval from content creation. Readers can view approved macro content as designed, but read access does not grant management authority. ## How does term review work? URL: https://compliance-glossary.teamkit.dev/confluence-term-review-workflow A term manager selects Submit and records a reason. The term moves from draft to review. Another eligible term manager selects Approve or Reject. Approval is blocked for the creator, submitter, or last content editor. Every transition creates a new version with actor, time, status, and reason before the current term is updated. ## How do I prove where a term is used? URL: https://compliance-glossary.teamkit.dev/confluence-term-usage-proof Usage evidence links a governed term to indexed page observations produced by a completed scan. Production v6 can preserve the page identity, page revision, scan state, glossary revision, and approved usage records available to the app. This proves recorded observations in scope. It does not prove every possible use across unscanned or inaccessible content. ## Can I see a term’s complete history? URL: https://compliance-glossary.teamkit.dev/confluence-term-version-history Yes. Production v6 keeps versioned governed records and history for supported term actions. Administrators can inspect prior meanings, changed fields, lifecycle states, actors, timestamps, decisions, and reasons recorded by the app. A later version does not overwrite prior approval evidence. Export and baseline evidence can preserve the relevant version for a controlled scope. ## What does the scanner check? URL: https://compliance-glossary.teamkit.dev/confluence-terminology-compliance-scanner The scanner checks governed Confluence pages for undefined terms, deprecated terms, unapproved governed terms, and configured non-preferred synonyms. It compares page content with the effective approved glossary for the selected scope. Results become page-linked findings and coverage evidence. A scan proves that recorded run, not permanent future compliance. ## What does the Confluence terminology dashboard show? URL: https://compliance-glossary.teamkit.dev/confluence-terminology-dashboard The Dashboard shows the current state of your glossary. It reports Total Terms, Approved, In Review, Draft, and Deprecated counts. It also shows the approved share, stale approvals, and category totals. Use it to identify governance work. The displayed percentage measures approval status. It does not prove compliance or provide certification. ## How do I resolve a finding? URL: https://compliance-glossary.teamkit.dev/confluence-terminology-finding-resolution Open the finding, review its page and governing term, then record the supported disposition and reason. Correct the Confluence page or glossary record when required. A disposition explains the decision; it does not change page content. Run a new scan after the underlying content changes to establish the current state. ## Can I compare scans over time? URL: https://compliance-glossary.teamkit.dev/confluence-terminology-scan-history Yes. Space Scan History lists completed scans with their recorded date, finding count, page count, and glossary revision. This lets teams compare scan outcomes across time and relate a result to its terminology policy state. Counts show recorded runs. They do not explain every change or prove that current pages remain unchanged. ## How should teams learn the workflow? URL: https://compliance-glossary.teamkit.dev/confluence-terminology-training Train one responsibility at a time. Production v6 has one administrative RBAC role, Term Manager, plus read-only page macros. Authors, reviewers, and evidence administrators are operating responsibilities assigned among Term Managers. Use different people for content creation and approval. Teach readers only glossary use. Then rehearse one governed term from Draft through evidence export. ## Can I monitor findings over time? URL: https://compliance-glossary.teamkit.dev/confluence-terminology-trend-monitoring Partly. Space Scan History lists saved page-scan snapshots for the selected space. Each row shows a date, the finding count for that page scan, and flagged term names. The view shows the latest 20 snapshots. It does not chart trends, identify the page, aggregate a space scan, or classify changes as new, persistent, or resolved. ## How do I find undefined terms? URL: https://compliance-glossary.teamkit.dev/confluence-undefined-term-scanner Open Compliance Scanner, select a space, and choose Scan Space. The scan checks accessible pages for uppercase acronyms and mixed-case tokens absent from the effective glossary's names and synonyms. Top Undefined Terms ranks candidates by affected pages and returned findings. Review each result before adding a space-scoped draft definition or assigning remediation. ## Compliance Glossary Content Library URL: https://compliance-glossary.teamkit.dev/content-hub Browse every public Compliance Glossary for Confluence guide, workflow, evidence page, comparison, and trust document in one categorized library. The page remains fully readable without JavaScript and adds an optional title-and-description filter. ## How are connector failures shown? URL: https://compliance-glossary.teamkit.dev/connector-failure-evidence Production contracts keep connector failure causes separate. They distinguish permission revocation, source deletion, source unavailability, replay, lag, partial batches, rate limiting, disabled connectors, and failed jobs. The current GitHub terminology workflow shows job and finding states. Generic connector health contracts should not be presented as enabled provider integrations. ## What is a reissue handoff? URL: https://compliance-glossary.teamkit.dev/controlled-document-reissue-handoff A reissue handoff is an evidence package for external document control. Production v6 binds an affected artifact to its glossary slice, baseline, archive, change context, and required external actions. The handoff records that execution is external and false inside the app. It does not approve, issue, or sign the document. ## How do I create an enterprise baseline? URL: https://compliance-glossary.teamkit.dev/create-enterprise-baseline-confluence Production version 6 lets an administrator initiate an enterprise baseline from Terminology Baseline. Under Create enterprise freeze, select scanned spaces, set retention, and choose Prepare and queue freeze. The server prepares, queues, captures, verifies, and promotes only complete evidence. Deployment is confirmed. Forge staging qualification and production capacity, cost, and residency evidence remain incomplete. ## Cyprus Cap 113 + NIS2: The CEO-Director Personal Liability Framework URL: https://compliance-glossary.teamkit.dev/cyprus-director-personal-liability-ceo Cap 113 ss.311/197/43 + NIS2 Art. 20(1)/32(5)(b) (national transposition) create non-waivable personal liability for Cyprus CEO-directors. ## D&O Insurance 2026: AI Governance Is the CEO's Pricing Driver URL: https://compliance-glossary.teamkit.dev/do-insurance-ai-governance 53 AI securities class actions since 2020. D&O settlement costs up 27% to $56M in H1 2025. Underwriters now probe AI governance evidence at renewal. ## D&O Renewal 2026: Governance Evidence Underwriters Want URL: https://compliance-glossary.teamkit.dev/do-renewal-cfo-governance Fintech, crypto, and VC-backed CFOs pay 2-3x mainstream D&O premiums (Price Forbes 2025). What renewal questionnaires now ask, and which artifacts hold up. ## Documentation URL: https://compliance-glossary.teamkit.dev/docs Install and use Compliance Glossary for Confluence: approvals, scanner, requirements mapper, settings, CSV import, and CSV evidence export. ## Document Control signs off your documents; Compliance Glossary keeps the terms inside them controlled everywhere they appear. URL: https://compliance-glossary.teamkit.dev/document-control-confluence-vs-compliance-glossary A fair Document Control for Confluence vs Compliance Glossary comparison for regulated Confluence teams that need both document sign-off and term-level governance across pages. ## Manager Liability Under DORA: The Governance Artifacts Regulators Will Ask to See URL: https://compliance-glossary.teamkit.dev/dora-cfo-personal-liability DORA Article 50 manager penalties depend on national transposition. Review the rule, Ireland example, governance evidence, and source links. ## DORA Regulation Terminology for Confluence URL: https://compliance-glossary.teamkit.dev/dora-terminology Manage DORA terminology in Confluence with audit trails, four-eyes approval, and compliance scanning. Built for banks, insurers, investment firms, and... ## Data Processing Agreement URL: https://compliance-glossary.teamkit.dev/dpa Data Processing Agreement (DPA) for Compliance Glossary for Confluence by DailyMind LTD. GDPR Article 28 compliant. ## Does the app execute signatures? URL: https://compliance-glossary.teamkit.dev/electronic-signature-boundary No. Compliance Glossary does not execute electronic signatures. It can preserve approval references and prepare a controlled reissue handoff for an external system. The production handoff contract fixes execution to external only and records that execution is false. The qualified release or quality system remains responsible for identity, intent, signature, and approval controls. ## What is stored in an enterprise baseline? URL: https://compliance-glossary.teamkit.dev/enterprise-baseline-contents An enterprise baseline stores a fixed membership set for approved term meanings and captured Confluence revisions. It includes revision hashes, canonical content objects, usage observations, finding descriptors, counts, coverage, retention, chunk roots, object checksums, conformance, and a root hash. Trace links are stored only when supplied. The workspace displays a smaller projection, not the full stored record. ## What is the enterprise evidence workspace? URL: https://compliance-glossary.teamkit.dev/enterprise-evidence-workspace-confluence The enterprise evidence workspace is the Terminology Baseline interface for deposited evidence and controlled evidence operations. It shows frozen meanings, revisions, SHA-256 hashes, availability, conformance, impact, trace links, and coverage blockers. Administrators can queue freezes, run verification, import or export archives, upload files, and download artifact outputs. The interface has a read-only state, while the current resolver layer requires administrator access. ## eSign Document QMS controls regulated documents and training; Compliance Glossary controls the terminology inside them. URL: https://compliance-glossary.teamkit.dev/esign-document-qms-vs-compliance-glossary eSign Document QMS and Training vs Compliance Glossary for Confluence: regulated document and training control versus governed terminology with approval evidence and audit-ready export. ## Does evidence survive source deletion? URL: https://compliance-glossary.teamkit.dev/evidence-after-source-deletion Yes. A completed baseline can preserve evidence after its live Confluence source is deleted. The freeze stores canonical content separately and records the exact revision, hash, usages, and findings. Survival depends on retained frozen content and successful package checks. Archive records alone cannot recreate missing body bytes. Verification reports source deletion as a distinct evidence gap. ## What happens if an archive changes? URL: https://compliance-glossary.teamkit.dev/evidence-archive-mutation-detection Archive validation fails when protected content changes. Compliance Glossary recalculates part hashes, content hashes, counts, order, chain links, tenant identity, and the root hash. Missing parts, changed evidence, reordered records, or tenant mismatches return distinct errors. Invalid evidence is not reconstructed as a valid imported package and cannot pass parity verification. ## What is the baseline root hash? URL: https://compliance-glossary.teamkit.dev/evidence-baseline-root-hash The baseline root hash is a SHA-256 fingerprint that summarizes the versioned evidence package. Enterprise freeze derives it from baseline identity and sorted chunk roots; each chunk root covers captured records and membership. Verification separately recomputes canonical manifest material and compares root and counts. A match detects unchanged recorded structure, but it does not prove that the original source was correct. ## Can many tools use one evidence model? URL: https://compliance-glossary.teamkit.dev/evidence-from-multiple-tools Yes, when each enabled source provides stable revision identity, provenance, bounded records, and supported evidence types. Production v6 uses shared contracts across Confluence evidence and controlled file uploads. GitHub and provider-neutral mapping contracts also exist, but current public workflow claims must stay limited to runtime-wired, user-visible source paths. ## How are uploads verified? URL: https://compliance-glossary.teamkit.dev/evidence-upload-integrity Production v6 verifies upload type, size, ownership, retention, completeness, and SHA-256 values before evidence is accepted. Staged uploads check every chunk at its exact position, then recalculate the assembled file hash. The ingestion path also rejects unsupported, encrypted, malformed, oversized, expired, incomplete, or parser-budget failures. ## Can I add Excel workbooks? URL: https://compliance-glossary.teamkit.dev/excel-compliance-evidence Yes. Upload an XLSX workbook through Upload controlled evidence. Compliance Glossary validates its extension and MIME type. It rejects encrypted or malformed packages and hashes the source bytes. The app extracts bounded worksheet cell values without executing formulas. It records provenance, retention, worksheet and cell counts, a frozen revision, and exact approved-term usages. ## How do I export an archive? URL: https://compliance-glossary.teamkit.dev/export-compliance-evidence-archive Open Enterprise evidence workspace and select Export archive for the active deposited baseline. The app queues a resumable server job. It writes bounded, content-addressed parts for meanings, artifacts, usage, links, and conformance. Before finalization, it verifies part order, hashes, record counts, section counts, and the root manifest. ## Which external evidence connectors are available in Compliance Glossary? URL: https://compliance-glossary.teamkit.dev/external-evidence-connector-limits Production v6 exposes three user-visible external evidence paths: Git Connector, Offline Manifest Sync, and Upload controlled evidence. GitHub and manifest imports are administrator-enabled and default off. File upload appears for licensed administrators with a current baseline. Generic approved HTTPS and the Requirements Yogi, Sodius, and Systems Engineering Studio profiles are contracts, not enabled integrations. ## From 483 to Warning Letter: FDA Data-Integrity Terminology Traps URL: https://compliance-glossary.teamkit.dev/fda-483-cfo-readiness A data-integrity Form 483 triggers remediation and launch delays that land on CFO guidance. Controlled terminology defends ALCOA+ attribution. ## FDA Terminology Management for Confluence URL: https://compliance-glossary.teamkit.dev/fda-terminology Manage FDA-regulated terminology in Confluence with audit trails, approval workflows, and 21 CFR Part 11 alignment. 43-term template included. ## What is affected when a requirement changes? URL: https://compliance-glossary.teamkit.dev/find-artifacts-affected-by-requirement-change Start from the frozen requirement and use Forward impact to see connected governed evidence. Production v6 can traverse approved or imported links to documents, code references, tests, deviations, terms, and release gates. It reports broken or moved endpoints. Candidate links remain separate and do not expand the governed result. ## What is affected when a term changes? URL: https://compliance-glossary.teamkit.dev/find-artifacts-affected-by-term-change Impact lookup returns artifacts connected to the term through imported or approved evidence links. Results can include requirements, documents, code references, tests, deviations, and release gates. The graph also shows broken or moved endpoints and bounded results. Candidate and rejected links stay outside the governed impact result. ## How do I find deprecated terms? URL: https://compliance-glossary.teamkit.dev/find-deprecated-terms-confluence Run Compliance Scanner for the governed space. Production v6 compares page terminology with the effective glossary and creates page-linked findings when deprecated records are used. Review the affected page, current governed term, and replacement guidance. Correct the page or governance record, record the disposition, and run a new scan. ## How do I find non-preferred synonyms? URL: https://compliance-glossary.teamkit.dev/find-disallowed-synonyms-confluence Add the known synonym to its governed term, then run Compliance Scanner. Production v6 can identify configured synonym usage and point reviewers to the preferred approved term. Review each page-linked finding, update the content when required, record the disposition and reason, and rescan to establish the new state. ## How do I find unapproved terms? URL: https://compliance-glossary.teamkit.dev/find-unapproved-terms-confluence Run Compliance Scanner for the governed space. Production v6 can flag known governed terms that appear in content before approval. Review the page and the term's lifecycle state. Remove or replace the usage, or complete the required independent review. Then run a new scan to record the current result. ## FinTech Compliance Terminology — Auditor-Ready Governance for DORA & NIS2 URL: https://compliance-glossary.teamkit.dev/fintech-compliance-terminology Terminology governance for DORA Art. 5, NIS2 Art. 21, and SOC 2. FinTech compliance teams manage regulatory terms in Confluence with four-eyes approval... ## How do I trace a requirement forward? URL: https://compliance-glossary.teamkit.dev/forward-traceability-requirements Forward requirement traceability starts with a governed requirement and follows approved or imported links to dependent requirements, documents, code references, tests, deviations, and approval evidence. In the Enterprise evidence workspace, Forward impact presents retained hops. Candidate and rejected links do not count as governed evidence. Coverage blockers show where the visible path is incomplete. ## What is forward term traceability? URL: https://compliance-glossary.teamkit.dev/forward-traceability-terminology Forward term traceability starts with a governed term and shows connected evidence in the recorded direction. Compliance Glossary can display linked requirements, documents, code references, tests, and deviations. Only approved or imported links count as governed evidence. Candidate and rejected links stay outside the trace. Coverage blockers show when results are partial. ## How does four-eyes approval work? URL: https://compliance-glossary.teamkit.dev/four-eyes-approval-confluence-glossary The person who creates, edits, or submits a term cannot approve that same content. A separate permitted reviewer must make the approval decision. Production v6 validates this separation before recording approved evidence. It preserves the content version, actors, timestamps, decision, and reason with the governed term history. ## Four-Eyes Principle in Documentation URL: https://compliance-glossary.teamkit.dev/four-eyes-principle The four-eyes principle bars self-approval. MiFID II, SOX 404, FDA GMP, ISO 27002 clause 5.3 all require it. See how Compliance Glossary enforces it in... ## How are approved meanings frozen? URL: https://compliance-glossary.teamkit.dev/freeze-approved-term-meanings Approved meanings are frozen as complete, versioned copies inside baseline membership. The app records the term, definition, category, synonyms, notes, scope, references, effective dates, ownership, review dates, approval chain, change reason, and a deterministic hash. It rejects unapproved, incomplete, or self-approved records. Later glossary edits do not rewrite the deposited copy. ## How are exact Confluence page revisions frozen? URL: https://compliance-glossary.teamkit.dev/freeze-confluence-page-revisions Exact Confluence page revisions are frozen by matching each saved scan row to the live page version and modified time before capture. The app copies canonical storage-format bytes, computes SHA-256, records source and scan coordinates, and binds usage and findings to that revision. If the page changed or cannot be read, the enterprise freeze fails instead of depositing different content. ## Fundraising Diligence: The AI Act Question That Moves the Term Sheet URL: https://compliance-glossary.teamkit.dev/fundraising-regulatory-diligence-ceo 64% of CEOs call the regulatory environment the #1 barrier to reinvention (PwC). At term sheet, 'are you AI Act compliant?' is now a diligence question. ## Git compliance controls code changes. Terminology governance controls what those changes mean. URL: https://compliance-glossary.teamkit.dev/git-compliance-terminology-governance Git compliance covers code history. Add terminology governance in Confluence with approved terms, human review, page scanning, and CSV evidence. ## How do I detect Git terminology drift? URL: https://compliance-glossary.teamkit.dev/git-to-confluence-terminology-drift Configure Git Connector for an approved repository, Confluence space, and allowed paths, then run a bounded terminology scan. Production v6 compares supported repository text at an immutable revision with the approved glossary policy. It records report-only jobs and findings. The connector does not edit source files or create governed requirement trace links. ## What is a terminology manifest? URL: https://compliance-glossary.teamkit.dev/git-to-confluence-terminology-manifest A terminology manifest is a bounded JSON record of repository terminology observations at a named source revision and glossary policy version. Production v6 imports it through Offline Manifest Sync as report-only evidence. It can preserve terms, findings, and source context without continuous repository access. It does not modify code or approve terminology. ## How do GitHub and Confluence share one trace? URL: https://compliance-glossary.teamkit.dev/github-confluence-evidence-traceability Production version 6 does not provide an end-to-end GitHub-to-Confluence trace workflow. Git Connector performs report-only terminology checks. Separate backend code can normalize immutable GitHub code and test revisions into enterprise evidence contracts. It emits candidate links, but the connector does not call it. No visible control approves candidates, and the trace workspace does not send a selected start node for traversal. ## Confluence Glossary Apps Compared by Job URL: https://compliance-glossary.teamkit.dev/glossary-comparison Compare Confluence glossary and approval tools by job: definition discovery, page approval, terminology governance, scanning, and evidence export. ## Why is a glossary export not a baseline? URL: https://compliance-glossary.teamkit.dev/glossary-export-vs-evidence-baseline A glossary export is not an evidence baseline because it reports selected records, while a baseline fixes a versioned evidence state. The export supports review in CSV or a print-ready package. The baseline preserves approved meanings, exact document revisions, hashes, usages, findings, coverage, and trace relationships. It can then be verified and packaged as an archive. ## GxP Documentation Management in Confluence URL: https://compliance-glossary.teamkit.dev/gxp-documentation Manage GxP documentation in Confluence with controlled vocabulary, audit trails, and approval workflows across GMP, GLP, GCP, GDP, and GVP. ## HIPAA Terminology Management for Confluence URL: https://compliance-glossary.teamkit.dev/hipaa-terminology HIPAA terminology managed in Confluence with four-eyes approval and version control. Keep Privacy Rule, Security Rule, and Breach Notification... ## How It Works URL: https://compliance-glossary.teamkit.dev/how-it-works Technical overview of how Compliance Glossary works: deterministic scanner detection logic, Forge Custom UI architecture, data storage, and security model. ## How do I re-import an archive? URL: https://compliance-glossary.teamkit.dev/import-compliance-evidence-archive Select the archive package and choose Import archive. Compliance Glossary treats the package as untrusted. It validates tenant and schema identity, ordered parts, record counts, canonical hashes, and the root hash. Stored multipart imports run in bounded, resumable deliveries. Promotion occurs only after imported counts and the compact part proof match the manifest. ## How do I reconstruct a decision after an incident? URL: https://compliance-glossary.teamkit.dev/incident-evidence-reconstruction Reconstruct an incident from a deposited baseline, not the current live pages. Verify the package first. Find the affected artifact and exact revision. Then use reverse provenance to follow governed links through tests, requirements, business decisions, and regulatory roots. Each retained hop shows its evidence reference or explains why that evidence is unavailable. ## InfoSec Terminology Management — SOC 2 & ISO 27001 Controlled Vocabulary URL: https://compliance-glossary.teamkit.dev/infosec-terminology-management SOC 2 and ISO 27001 auditors check document consistency. Control your security terminology — incident, vulnerability, breach, event — with a governed... ## How do I install Compliance Glossary? URL: https://compliance-glossary.teamkit.dev/install-compliance-glossary-confluence A Confluence administrator installs Compliance Glossary from Atlassian Marketplace, reviews the requested permissions, and opens Compliance Glossary from Apps. The installation event adds the installer to Term Managers. Open Settings to confirm role access before adding terms or scanning pages. Installation is for Confluence Cloud and does not permit the app to edit Confluence pages. ## ISO 13485 Terminology Management for Confluence URL: https://compliance-glossary.teamkit.dev/iso-13485-terminology Manage ISO 13485:2016 terminology in Confluence with audit trails, version control, and four-eyes approval. Built for notified body audits. ## ISO 27001 Terminology Management for Confluence URL: https://compliance-glossary.teamkit.dev/iso-27001-terminology ISO 27001 terminology managed in Confluence with version control, four-eyes approval, and audit export. Keep risk register, policies, and SOA aligned. ## Keysight's Glossary covers Confluence Server; Compliance Glossary covers controlled definitions in Confluence Cloud. URL: https://compliance-glossary.teamkit.dev/keysight-glossary-alternative A Glossary by Keysight Technologies alternative for teams moving from Confluence Server to Cloud who need controlled definitions with approval evidence and audit-ready export. ## What is the maximum upload size? URL: https://compliance-glossary.teamkit.dev/large-evidence-file-upload Direct evidence upload supports files up to 350 KiB. Larger supported files use staged upload up to 25 MiB. Staged sessions use 256 KiB chunks and allow no more than 100 chunks. Each session expires after one hour. Production v6 verifies chunk hashes and the final file hash before ingestion. ## Legal Glossary Articles for Lawyers and In-House Counsel URL: https://compliance-glossary.teamkit.dev/legal-articles Source-backed legal glossary articles for in-house counsel, legal ops, product counsel, privacy counsel, AI governance, and regulatory lawyers using Confluence. ## Legal Department AI Governance Roles Term Map URL: https://compliance-glossary.teamkit.dev/legal-department-ai-governance-roles-term-map Map legal, privacy, security, product, and executive AI-governance roles to controlled terms, owners, reviewers, and evidence in Confluence. ## Legal Glossary in Confluence URL: https://compliance-glossary.teamkit.dev/legal-glossary-confluence Build a legal glossary in Confluence with approved terms, legal sources, definition owners, independent review, scanner checks, and evidence. ## Legal Operations Knowledge Management Taxonomy URL: https://compliance-glossary.teamkit.dev/legal-operations-knowledge-management-taxonomy Structure legal knowledge in Confluence with controlled definitions, policy and template terms, source links, ownership, review, and evidence. ## What happens after a live page changes? URL: https://compliance-glossary.teamkit.dev/live-edits-after-baseline-freeze After a live Confluence page changes, the completed baseline stays unchanged. Its copied revision bytes, content hash, scan evidence, membership, and root remain tied to the earlier page version. The page-change trigger marks current scan evidence stale and can record a new scan. Preserve the edit in a later verified baseline; do not overwrite the earlier evidence. ## M&A Exit: When Diligence Rewrites the CEO's Offer URL: https://compliance-glossary.teamkit.dev/ma-exit-compliance-ceo HSF Kramer 2025: many 2024 deals aborted on diligence findings. Compliance gaps drive purchase-price cuts. A controlled glossary is a VDR artifact, not... ## Material Weakness and CFO Departure: Notre Dame's Data, and What to Do About Terminology Drift URL: https://compliance-glossary.teamkit.dev/material-weakness-cfo-departure Failed remediation of a material weakness is associated with higher C-suite turnover and negative market returns. How terminology governance closes one... ## Public MCP Server — Compliance Glossary for Confluence URL: https://compliance-glossary.teamkit.dev/mcp The public MCP server lets compatible AI assistants search and fetch Compliance Glossary for Confluence documentation with exact canonical source URLs. It exposes only read-only search and fetch tools and cannot access customer Confluence spaces, Forge tenant data, private evidence, or write actions. ## How are evidence failures reported? URL: https://compliance-glossary.teamkit.dev/missing-moved-deleted-evidence Compliance Glossary reports evidence failures as separate states. Missing, moved, deleted, corrupted, dangling, stale, unavailable, and unindexed records are not collapsed into one warning. This distinction shows leaders whether evidence changed, disappeared, lost a target, fell behind its source, or was never available to the index. The app does not silently mark partial evidence complete. ## M&A VDR Readiness: How a Controlled Glossary Survives Diligence (Sell-Side and Buy-Side) URL: https://compliance-glossary.teamkit.dev/mna-vdr-cfo-readiness 14% of large M&A deals die on antitrust; ~60% of execs blame failed deals on poor diligence. How a controlled glossary survives the VDR. ## NIS2 Article 32: CEO Management-Ban Request Power URL: https://compliance-glossary.teamkit.dev/nis2-ceo-suspension NIS2 Article 32(5)(b) lets supervisors ask national bodies, courts, or tribunals for temporary management-function bans in essential entities. ## NIS2 Article 20(2): The CEO Training Duty You Cannot Delegate URL: https://compliance-glossary.teamkit.dev/nis2-ceo-training-duty NIS2 Article 20(2) requires management-body members to follow cybersecurity training. Approved terminology is one engagement artifact, not a substitute. ## NIS2 Article 20: What the Management-Body Duty Demands from CFOs URL: https://compliance-glossary.teamkit.dev/nis2-cfo-personal-liability NIS2 Article 20 puts cybersecurity oversight on management bodies. For CFOs, personal-liability mechanics depend on national transposition. ## NIS2 Directive Terminology for Confluence URL: https://compliance-glossary.teamkit.dev/nis2-terminology NIS2 penalties hit €10M or 2% of global turnover. Align cybersecurity terms across IT, legal, and compliance teams in Confluence with version control... ## Can I sync without continuous repository access? URL: https://compliance-glossary.teamkit.dev/offline-terminology-manifest-sync Yes. Offline Manifest Sync imports a bounded JSON terminology manifest without continuous repository access. The manifest keeps its source revision, policy version, terms, findings, and import identity. Production v6 limits each manifest to 256 KB and 1,000 terms. Imported observations remain report-only evidence and do not edit repository files. ## Page Approval proves a page was approved; Compliance Glossary provides term-level approval and scan evidence. URL: https://compliance-glossary.teamkit.dev/page-approval-vs-compliance-glossary A fair Page Approval for Confluence vs Compliance Glossary page for regulated teams that need term-level approval evidence, version history, scanner findings, and exportable evidence alongside page-level sign-off. ## Can I add PDF files? URL: https://compliance-glossary.teamkit.dev/pdf-compliance-evidence Yes. In production version 6, Upload controlled evidence accepts an exact .pdf and application/pdf pair. It checks only the %PDF-x.y header and a %%EOF marker, then records PDF version and byte length. It hashes and stores the original bytes with provenance and an immutable revision. It performs no text extraction, OCR, semantic analysis, signature verification, legal validation, or term matching. ## Pharma Terminology Management — Audit-Ready Terminology Control for Pharma and MedTech URL: https://compliance-glossary.teamkit.dev/pharma-terminology-management Pharma and MedTech QA/RA teams use Compliance Glossary to close terminology gaps before the next inspection. Four-eyes approval aligned with 21 CFR Part... ## Privacy Policy URL: https://compliance-glossary.teamkit.dev/privacy Privacy policy for Compliance Glossary for Confluence by DailyMind LTD. ## From Regulatory Change Memo to Controlled Vocabulary URL: https://compliance-glossary.teamkit.dev/regulatory-change-memo-controlled-vocabulary Turn a regulatory change memo into controlled Confluence terms with legal sources, affected policies, owners, review dates, scanning, and evidence. ## Regulatory Complexity Overload: Why “Unsettled Legal Environment” Tops the CFO Risk List URL: https://compliance-glossary.teamkit.dev/regulatory-complexity-cfo Gartner ranks unsettled regulatory environment the #1 emerging risk. EY: 81% of CFOs call Pillar Two top issue, only 21% feel prepared. ## Regulatory Source of Truth in Confluence: How Legal Owns Definitions Without Bottlenecking Teams URL: https://compliance-glossary.teamkit.dev/regulatory-source-of-truth-confluence-legal-definitions Create a regulatory source of truth in Confluence so Legal can govern definition owners, reviewers, sources, usage, and review cadence. ## How do I prepare document reissue? URL: https://compliance-glossary.teamkit.dev/reissue-documents-after-term-change Start from the changed approved term and review Forward impact. Confirm each affected retained artifact, generate its glossary slice, and download a reissue handoff. The handoff gives the external document-control owner frozen meanings, usage evidence, archive context, and required actions. Approval, issuance, and signatures remain outside Compliance Glossary. ## What evidence should a release preserve? URL: https://compliance-glossary.teamkit.dev/release-evidence-package A release package should preserve the exact evidence used for that release. This includes approved meanings, source revisions, hashes, usages, findings, coverage, governed links, verification, and external approval references. Production v6 can freeze and export these records. It does not approve the release or execute signatures. ## How are requirement levels connected? URL: https://compliance-glossary.teamkit.dev/requirements-traceability-levels Requirement levels are connected with typed, versioned evidence links. A derives relationship can connect one requirement to another. An authorizes relationship can connect a business decision to a requirement. Production v6 validates each node type, link type, approval state, effective period, and provenance before the relationship can count as governed evidence. ## What is reverse traceability? URL: https://compliance-glossary.teamkit.dev/reverse-traceability-compliance Reverse traceability starts with an implementation artifact and follows imported or approved evidence toward its governing reason. Production v6 labels this action Reverse provenance. A path can connect code, documents, tests, or deviations to requirements, business decisions, regulations, and approval evidence. Missing retained evidence remains visible at the affected hop. ## Is Compliance Glossary eligible for Runs on Atlassian? URL: https://compliance-glossary.teamkit.dev/runs-on-atlassian-eligibility No. Forge CLI reports production version 6 as ineligible for Runs on Atlassian. The returned reason is App is egressing data. Its manifest declares one backend destination, https://api.github.com, for the optional GitHub connector. This result is an Atlassian program eligibility outcome. It is not a security failure, compliance verdict, certification, or statement that the app uses a vendor-operated backend. ## Scroll Content Quality lints your pages; Compliance Glossary governs the terms in them. URL: https://compliance-glossary.teamkit.dev/scroll-content-quality-vs-compliance-glossary An honest Scroll Content Quality vs Compliance Glossary comparison for regulated Confluence teams deciding between generic content-quality rules and controlled-term governance. ## Can I search a frozen baseline? URL: https://compliance-glossary.teamkit.dev/search-frozen-compliance-evidence Yes. Production v6 searches the active enterprise baseline through indexed prefixes on frozen subject names or linked artifact titles. Each server page contains up to 50 records and uses stable cursors. The text field also applies local substring matching to the loaded page. Subject, Artifact, Conformance, and Impact filter only those loaded records. This is not arbitrary full-text search. ## Security Questionnaires Are Eating Your Engineering Week. Terminology Governance Gets It Back. URL: https://compliance-glossary.teamkit.dev/security-questionnaire-terminology Security questionnaires take 10-40 hours each; a 400-question DDQ burns an engineer-week. A shared approved glossary cuts the definitional portion and... ## Security Whitepaper — Vendor Assessment for Procurement Teams URL: https://compliance-glossary.teamkit.dev/security-whitepaper Vendor security assessment for Compliance Glossary: Forge architecture, data handling, encryption, incident response, and AI release gates. ## Security Policy URL: https://compliance-glossary.teamkit.dev/security Security policy for Compliance Glossary for Confluence: Atlassian Forge architecture, data isolation, encryption, vulnerability reporting, and GDPR... ## What does an evidence hash prove? URL: https://compliance-glossary.teamkit.dev/sha-256-compliance-evidence An evidence hash proves whether the checked bytes match the recorded bytes. Compliance Glossary uses SHA-256 across frozen records, file uploads, archive parts, and baseline manifests. A mismatch exposes change or corruption. A matching hash does not prove that the source was correct, legally valid, approved, or stored under WORM controls. ## Is Compliance Glossary an alternative to Smart Terms? URL: https://compliance-glossary.teamkit.dev/smart-terms-alternative Compliance Glossary is an alternative only when the main job is governed terminology evidence. Choose it for controlled states, separate approval, scan findings, frozen baselines, and traceability. Smart Terms is designed for glossary discovery, configurable highlighting, rich term content, relationships, and multiple languages across Confluence and Jira. Neither is the universal replacement for the other. ## The SOC 2 Revenue Gate: Why Terminology Controls Are the Fastest Path Through Security Questionnaires URL: https://compliance-glossary.teamkit.dev/soc-2-cfo-revenue-gate Stalled SOC 2 questionnaires delay enterprise deals and miss CFO guidance. Audit-trailed terminology is a citable control artifact. $3.35/user/month. ## SOC 2 Terminology Management for Confluence URL: https://compliance-glossary.teamkit.dev/soc2-terminology SOC 2 terminology management is the practice of version-controlling defined terms (“incident”, “risk owner”, “change management”) so auditors see one consistent definition across policies, runbooks, and evidence. Compliance Glossary for Confluence ships 40 SOC 2 terms pre-mapped to SOC 2 Trust Services Criteria CC1.4, CC2.1, CC3.1, CC5.2, CC7.2, and CC8.1 — with four-eyes approval and append-only version history. ## SoftComply manages controlled documents; Compliance Glossary manages controlled terminology. URL: https://compliance-glossary.teamkit.dev/softcomply-vs-compliance-glossary SoftComply Document Manager vs Compliance Glossary: SoftComply manages controlled documents for QMS and ISMS; Compliance Glossary manages controlled terminology inside Confluence. They can be complementary. ## SOX 302 in the AI Era: What Reasonable Care Looks Like When Your 10-K Talks About AI URL: https://compliance-glossary.teamkit.dev/sox-302-ai-era SOX 302/906: CEO/CFO certification duties, Section 906 criminal penalties, and why AI claims need a dated terminology-control record. ## SOX 302/906: The CEO Certification That Can Send You to Prison URL: https://compliance-glossary.teamkit.dev/sox-ceo-certification-liability SOX 906 willful false certification: $5M fine, 20 years prison. Jerry Dale Cash drew 9 years. CEOs personally sign every 10-Q and 10-K. Governance matters. ## Replace legal term spreadsheets with a controlled Confluence glossary URL: https://compliance-glossary.teamkit.dev/spreadsheets-wikis-proposal Commercial proposal for legal teams moving glossary work from spreadsheets and wiki pages into source-backed Confluence terminology governance. ## Support SLA URL: https://compliance-glossary.teamkit.dev/support-sla Support service level agreement for Compliance Glossary for Confluence. Response times, severity levels, and contact information. ## How to Build a Terminology Management System URL: https://compliance-glossary.teamkit.dev/terminology-management-guide Step-by-step guide to building a governed terminology system: from flat glossary to approval workflows, version control, and audit-trail enforcement. ## Terms of Service URL: https://compliance-glossary.teamkit.dev/terms Terms of Service and End User License Agreement for Compliance Glossary for Confluence by DailyMind LTD. ## Can I add text files? URL: https://compliance-glossary.teamkit.dev/text-file-compliance-evidence Yes. Production v6 accepts allow-listed TXT, Markdown, CSV, JSON, and XML files when the extension and MIME type match. It validates UTF-8 content, checks JSON or basic XML structure where relevant, computes SHA-256, and records artifact, revision, provenance, retention, and bounded extracted text evidence. ## How do I trace code to regulation? URL: https://compliance-glossary.teamkit.dev/trace-code-to-regulatory-requirement Select the captured code revision and choose Reverse provenance. Approved or imported links can lead from the code reference to component, system, or business requirements, then to the recorded regulation. Each hop keeps its type, provenance, and evidence reference. Candidate links remain outside the governed path until reviewed. ## How do I trace GitHub code to requirements? URL: https://compliance-glossary.teamkit.dev/trace-github-code-to-requirements No. Production version 6 does not provide end-to-end GitHub-code-to-requirement tracing. Git Connector performs report-only terminology checks and never calls the separate evidence mapper. That mapper can create an immutable code revision and candidate implements link. However, no resolver or visible control approves that candidate. The workspace also does not request traversal from a selected code node. ## How do I connect GitHub tests to requirements? URL: https://compliance-glossary.teamkit.dev/trace-github-tests-to-requirements No. Production version 6 does not provide end-to-end GitHub-test-to-requirement tracing. Git Connector performs report-only terminology checks and never calls the separate evidence mapper. That mapper can create an immutable test revision and candidate verifies link. However, no resolver or visible control approves that candidate. The workspace also does not request traversal from a selected test node. ## How do I prove why an implementation exists? URL: https://compliance-glossary.teamkit.dev/trace-implementation-to-business-decision Start with the deposited implementation evidence and select Reverse provenance. Compliance Glossary follows imported or approved links through component and system requirements to the recorded business decision. Each hop shows its relationship and evidence reference. Missing evidence remains visible. This gives leaders a reviewable reason chain without requiring a graph query language. ## How are tests and deviations connected? URL: https://compliance-glossary.teamkit.dev/trace-tests-and-deviations Tests and deviations are stored as typed evidence nodes. A test can verify a requirement, document, or code reference. A deviation can link to any of those records or to a test. Each link keeps its direction, approval state, effective dates, and provenance. Only approved or imported links count as governed evidence. ## Do users need a query language? URL: https://compliance-glossary.teamkit.dev/traceability-without-query-language No. Enterprise evidence workspace presents traceability through two controls: Forward impact and Reverse provenance. Users follow ordered evidence hops and open retained proof without writing graph syntax. The service queries directional indexes behind the interface. The start node and every traversed link must already exist as imported or approved evidence. ## VECTORS Glossary makes terms easy to find; Compliance Glossary makes them audit-ready. URL: https://compliance-glossary.teamkit.dev/vectors-glossary-alternative A fair VECTORS Glossary alternative page for regulated Confluence teams that need approval evidence, version history, scanner findings, and exportable term-level evidence. ## What is a verifiable evidence archive? URL: https://compliance-glossary.teamkit.dev/verifiable-compliance-evidence-archive A verifiable evidence archive is a deterministic package for one deposited baseline. Its manifest identifies the tenant, baseline, product release, coverage, section counts, ordered parts, content hash, and root hash. Its parts carry meanings, artifacts, usage, links, and conformance records. Validation recalculates hashes and counts before an archive can be accepted. ## How do I verify a baseline? URL: https://compliance-glossary.teamkit.dev/verify-evidence-baseline-integrity Select the deposited baseline and choose Run verification. Compliance Glossary recalculates recorded hashes, section counts, member order, baseline identity, and governed references. The check does not change the package. It reports missing, changed, stale, moved, dangling, or unindexed evidence as distinct findings when the supplied verification evidence supports those checks. ## How do I verify an archive? URL: https://compliance-glossary.teamkit.dev/verify-exported-evidence-archive Use Import archive to run package validation, but do not treat the workspace completion message as verification evidence. The service recalculates part, content, and root hashes. It checks schema, identities, part chain, keys, ranges, record order, counts, and reconstruction parity. The current workspace does not display the detailed validation response. Run verification checks the baseline, not the archive. ## What is a compliance evidence baseline? URL: https://compliance-glossary.teamkit.dev/what-is-compliance-evidence-baseline A compliance evidence baseline is a point-in-time record used to compare later terminology and document state. Compliance Glossary has two baseline paths. Create baseline freezes term versions and scanned page references, but not page bytes, hashes, or trace links. Prepare and queue freeze creates the richer enterprise package with retention, exact revisions, hashes, evidence collections, and verification. ## Why compliance glossaries don’t belong in spreadsheets URL: https://compliance-glossary.teamkit.dev/why-compliance-glossaries-dont-belong-in-spreadsheets Why spreadsheet glossaries cannot control terminology across Confluence—and how approved definitions, change history, and page scanning make knowledge active. ## Can I add Word documents? URL: https://compliance-glossary.teamkit.dev/word-document-compliance-evidence Yes. Production version 6 accepts only .docx with the exact Word MIME type. It opens a bounded ZIP package, requires word/document.xml, and extracts non-empty paragraph text, including table-cell paragraphs. It records paragraph count, hashes and stores source bytes, and indexes exact approved-term matches. It does not interpret layout, headers, footers, comments, tracked changes, embedded objects, signatures, meaning, or legal validity.