Findings
Understand Integrity finding codes, severity, enforcement, redaction, action targets, and why findings disappear when fixed.
An Integrity finding is a current-state diagnostic. It says that workspace data or configuration currently violates a code-defined rule.
Each finding has a stable code such as trace.required_link_missing, identifier.next_generated_collision, or import.readiness_blocking. Codes are stable so Integrity views, inline warnings, tests, docs, and agent explanations all use the same vocabulary.
Review findings
Open Workspace -> Integrity -> Findings.
You can filter by:
- severity
- rule pack
- source
- entity type
- status or blocking state
- visible versus restricted detail
- actionable versus informational findings
You can group the table by rule pack, source, artefact, or remediation target.
Severity
| Severity | Meaning |
|---|---|
| Info | Worth knowing, but not usually a workflow problem. |
| Warning | Review the issue before it becomes harder to interpret or fix. |
| Critical | Source-of-truth integrity is at risk and should be fixed soon. |
| Blocking | A workflow such as import or baseline locking cannot safely continue until the issue is fixed. |
Severity describes how urgent the finding is. Enforcement describes what workflow, if any, is blocked.
Enforcement
Integrity findings can be:
- Advisory - visible guidance, no workflow block.
- Creation-blocking - new rows or identifiers cannot be created safely.
- Import-blocking - the import cannot proceed until readiness blockers are resolved.
- Baseline-blocking - a baseline cannot lock with the current evidence state.
- Workflow-blocking - a specific configuration or product workflow cannot continue.
- None - informational only.
Blocking findings are not just UI warnings. The authoritative workflow gate stays in the underlying product surface, such as import readiness or baseline locking.
Visibility
Unrestricted findings show source, artefact, route, and evidence context that you are allowed to see. Restricted findings show only display-safe aggregate information.
Restricted findings do not expose:
- source names
- artefact identifiers
- link details
- import evidence
- coverage configuration context
- agent-ready repair detail
Action targets
A finding has one primary action target when Integrity knows where you should start. Examples include opening an artefact, a source, a Trace Schema row, an import report, a baseline, or a filtered Integrity view.
Some findings also have secondary actions. A missing required-link finding can keep Open artefact as its primary remediation action and add Coverage as a secondary drill-down when Integrity can identify one unambiguous required Trace Schema config.
Why findings disappear
Integrity recomputes findings from current workspace state. If you fix the underlying issue, the finding disappears after data refresh and realtime invalidation. If it comes back, the current state still violates the rule.