At a glance
| Evidence layer | Records produced | Primary use | Limit |
|---|---|---|---|
| Term governance | Current term, status, version, actor, time, reason, and available communication evidence | Reconstruct terminology decisions in Version History | Only data recorded through the workflow is available |
| Page scanning | Latest page status, findings, approved usage, page version, scan time, and glossary revision | Show the terminology state observed on a Confluence page | A scan is point-in-time evidence, not permanent page cleanliness |
| Finding response | Status, owner, due date, severity, justification, closure evidence, actor, and time | Explain remediation or an accepted exception | The latest resolution state is retained for each finding key |
| Audit Evidence Package | Term history, page status, retained scan snapshots, and finding resolutions | Export scoped operational evidence as CSV or a print-ready package | Source page body text is not included |
| Terminology Baseline | Frozen glossary term states and scanned page states for selected spaces | Compare changed terms, changed pages, usage, and new findings | This Confluence baseline stores page versions, not content hashes or trace links |
| Baseline impact | Frozen and current indexed term usage by page | Identify observed pages affected by a term change | Results are bounded and can be marked truncated |
| Enterprise freeze | Frozen meanings, artifact revisions, usage observations, findings, trace links, counts, coverage, and hash roots | Deposit a verifiable evidence package | Coverage depends on the records captured by each source adapter |
| Run verification | Manifest count and root-hash checks, artifact checks, usage states, and trace endpoint states | Separate conformant, incomplete, and nonconformant evidence | Verification checks recorded evidence; it does not validate legal conclusions |
| Trace graph | Approved or imported links between evidence nodes | Follow evidence forward or backward | Candidate links are not governed trace evidence |
| Export archive | Ordered, content-addressed parts and a root manifest | Move a frozen package between controlled environments | Export is a queued job and is complete only after final verification |
How it works
- Define the audit question and evidence period.
- For current operational records, open Audit Evidence Export.
- Set Evidence scope, Period from, and Period to.
- Select Generate Evidence Package. Download the CSV or open the print-ready package.
- For a comparison point, open Terminology Baseline.
- Enter Reason for this baseline, select Spaces included, and select Create baseline.
- Review Baseline evidence report and Changed since baseline.
- For hashed integrity or cross-artifact trace evidence, open Enterprise evidence workspace.
- Resolve Coverage blockers, then select Run verification.
- Use Trace graph for evidence paths. Select Export archive for a portable frozen package.
Example
A release review needs decision, adoption, and integrity evidence. The team exports the approved term's Version History and the affected pages' scan records. A Terminology Baseline shows which term and page versions changed after the release point. The enterprise baseline verifies stored hashes and trace endpoints. Its archive packages the frozen evidence for controlled handoff.
What this does not mean
The app records terminology governance and related evidence. It does not run an audit, interpret a regulation, certify compliance, approve a release, or replace an electronic signature. Operational exports are not immutable signing systems. The standard Confluence baseline has explicit hash and trace limits. Enterprise conclusions remain limited by captured sources, coverage blockers, and unresolved checks.
Related questions
Next step
Choose the smallest evidence layer that answers the audit question, verify its coverage, and export the scoped records.
View on Atlassian Marketplace