Compliance Glossary for Confluence

How do I reconstruct a decision after an incident?

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.

Last verified against production v6 · 26 September 2026

At a glance

InputActionOutputLimit
External evidence archiveUse Import archiveValidated package or explicit import errorsTenant, schema, count, order, and hash failures block acceptance
Deposited baselineSelect Run verificationIntegrity and conformance resultVerification does not prove source correctness
Affected artifactUse Search deposited evidence or the Artifact filterFrozen artifact recordSearch covers indexed evidence fields, not arbitrary full text
Exact revision and hashSelect Open evidenceRevision-specific evidenceUnavailable content remains unavailable
Approved or imported trace linksSelect Reverse provenancePath to tests, requirements, decisions, or regulatory rootsCandidate and rejected links do not count as governed evidence
Missing endpoint or bounded resultReview Coverage blockersVisible reconstruction gapA partial trace cannot support a complete claim

How it works

  1. Open Enterprise evidence workspace.
  2. If needed, select an Archive package and choose Import archive.
  3. Select the deposited baseline. Review Coverage blockers.
  4. Select Run verification.
  5. Use Search deposited evidence or the Artifact filter.
  6. Open the affected revision with Open evidence.
  7. In Trace graph, select Reverse provenance. Open each Evidence reference.

Example

An incident concerns a changed controller revision. The deposited baseline preserves the earlier revision and its hash. Reverse provenance links that code reference to its component requirement. Further governed links reach the system requirement, a business decision, and the regulatory basis. A linked test supplies validation context. A missing hop appears as a coverage blocker.

What this does not mean

The workspace reconstructs recorded evidence. It does not perform root-cause analysis. It does not restore absent source content. It does not approve remediation or certify compliance. Archive hashes provide tamper evidence, not legal WORM storage. Conclusions remain limited to the verified package and governed links.

Related questions

Verify Evidence Baseline IntegrityReverse Traceability ComplianceEvidence After Source Deletion

Next step

Verify the deposited baseline before using its reverse trace in an incident review.

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