At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Completed baseline | Read its stored revision, membership, and root | Evidence tied to the captured page version | A live edit does not update this record |
| Page create or update event | Mark the prior current scan stale, then run the page scan | Stale status and, when the scan completes, current evidence | A five-minute debounce can skip a repeated fetch; operational errors can prevent a new scan |
| Edited page version | Capture canonical body bytes and calculate a new content hash | A distinct revision identity for a later freeze | The source version must still match during capture |
| Source drift during freeze | Compare the prepared snapshot with the source | Failed freeze with no current-pointer promotion | Mixed or incomplete evidence is not promoted |
| Verified later freeze | Check counts and aggregate roots, then promote its pointer | A new current baseline | The earlier baseline remains stored under its own identity |
How it works
- Open Compliance Scanner.
- Under Select Space to Scan, choose the space and select Scan Space.
- Check Space Scan History for the new completed scan.
- Open Terminology Baseline and review Changed since baseline.
- Under Term usage and impact, select Look up usage when the edit affects terminology.
- Under Create enterprise freeze, set the scope and retention fields, then select Prepare and queue freeze.
- Select Run verification before treating the later baseline as current evidence.
Example
Baseline A contains page version 12 and its content hash. An editor saves version 13. Baseline A still identifies version 12. The current scan becomes stale, and a completed scan can capture version 13. A later verified Baseline B can then include version 13 under a separate baseline identity.
What this does not mean
A page edit never mutates completed baseline evidence. Automatic scanning is not a completion guarantee: debounce handling or an operational error can leave the current scan stale. A later enterprise freeze requires complete, consistent source evidence. Verification checks stored counts and roots before pointer promotion; it does not determine whether the edited wording is legally or semantically correct.
Related questions
Next step
After a controlled page edit, confirm the new scan, review its impact, and create a later verified baseline when the change must enter evidence.
View on Atlassian Marketplace