The Changes view shows only published, tenant-visible signals.

Triage order

1

Read the stable fields

Start with signal_type, severity, entity, detection time, and verification status. Use the summary as context, not as the automation contract.
2

Inspect the delta

Review type-specific details such as removed operations, newly required parameters, tool schema hashes, release metadata, or replay assertion failures.
3

Open evidence

Compare the before/after excerpts at the stable pointer and confirm the snapshot lineage and source.
4

Assess impact

Determine whether the changed surface is used by your product. Stage 2 deployments can intersect verified signals with repository exposures.
5

Acknowledge when handled

Acknowledgement removes a breaking signal from the unacknowledged CI-gate set. It does not delete the signal or evidence.

Read through the API

Then retrieve one signal’s evidence:
See Changes and Evidence for response fields.