Compliance Glossary for Confluence

What is a 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.

Last verified against production v6 · 26 September 2026

At a glance

InputActionOutputLimit
Source revision and policy versionValidate stable manifest contextRevision-bound import identityValues must meet bounded contract rules
Observed terms and findingsValidate manifest recordsReport-only evidenceMaximum 1,000 terms
JSON fileLoad and import itImport summary and findingsMaximum 256 KB
Repeated identical manifestReuse prior identityIdempotent resultChanged evidence needs a new manifest

How it works

  1. Generate the supported JSON manifest for one source revision.
  2. Open Offline Manifest Sync.
  3. Choose the local manifest file.
  4. Review the JSON before import.
  5. Select Import manifest.
  6. Review the import summary and findings.

Example

A restricted build environment creates a manifest for one commit and policy version. An administrator imports it without granting ongoing repository access. Findings remain tied to that supplied revision and do not change the source repository.

What this does not mean

The manifest is supplied evidence. Compliance Glossary does not inspect the source repository during offline import or prove that the generator covered every file. Protect the generation process.

Related questions

Offline Terminology Manifest SyncGit To Confluence Terminology DriftExternal Evidence Connector Limits

Next step

Generate each manifest inside the controlled source pipeline.

View on Atlassian Marketplace
Verification basis: production v6 code, tests, manifest, and operations guidance. Verified 26 September 2026.