Topology View

See the operational shape of the workspace, not just its labels.

CTK Lens uses topology view to make the workspace spatially legible. Services, dependencies, repositories, incidents, contradictions, and evidence overlays stay attached to the exact nodes and edges where operators need to reason about them.

Why Topology Matters

Topology compresses the shape of the workspace faster than a list ever can
Edges reveal where evidence and incident pressure accumulate
Overlays make contradiction and adjudication visible in place
Node details let operators inspect scope without losing scene context

Topology Layers

The map stays interactive, scoped, and evidence-aware.

Workspace Scope Strip

Lens keeps the active workspace boundary visible so the operator knows which repos and services are currently in play.

Operational Nodes

Services, runtimes, dependencies, and relationships are projected into one navigable topology canvas.

Overlay Layers

Contradictions, evidence counts, incident markers, and truth posture can be attached directly to nodes and edges.

Detail Panels

Selecting a node reveals confidence, related incidents, peer relationships, and attached signal context.

Topology FAQ

Topology should explain why the scene is operationally useful.

What does CTK Lens topology view show?

Topology view projects services, repositories, dependencies, overlays, evidence counts, and incident context into one spatial workspace map.

Why is topology better than a list during incident work?

Topology compresses workspace shape faster than a list and makes it easier to see where evidence, contradiction pressure, and incidents are actually landing.

What are overlay layers in topology view?

Overlay layers attach contradictions, incident markers, truth posture, and evidence context directly to nodes and edges instead of hiding them in separate panels.

Does topology view replace product provenance?

No. Lens keeps the scene visual, but the underlying authorship and operational meaning still come from launcher authority, CTK Reason, and CTK Replay.