Incidents

Incidents land on the scene where they matter.

CTK Lens does not treat incident handling as a detached queue. It projects incident pressure directly onto the live workspace topology so the operator can see the affected scope, the supporting evidence, and the nearby contradictions before deciding what happens next.

Open Topology View Open Situational Awareness

Triage Questions

Which service or edge is actually degraded?

Is this incident CTK-authored, Replay-confirmed, or still unresolved?

How much supporting evidence is attached to the affected relationship?

What nearby contradiction or truth decision should influence triage?

Incident Flow

Lens turns incident pressure into spatial context.

Detect

CTK Reason intelligence and workspace observations identify the affected node, edge, or service relationship.

Project

Lens raises overlays and incident context directly inside the topology instead of isolating the event in a separate feed.

Contextualize

Evidence counts, contradictions, freshness, and adjudication posture explain whether the incident is stable, contested, or still emerging.

Orient

The operator sees where the issue lives, what it affects, and which next review should happen before any risky action.