Live State

Lens reads the workspace as it exists now.

CTK Lens is built around the current workspace scene, not a disconnected dashboard. It restores launcher context, reads the latest shared intelligence, and projects live operational posture into one visual model without obscuring where the state came from.

See Signals See Situational Awareness

Operator Questions

Is this workspace scene fully hydrated or only partially available?

Which product authored the current state I am looking at?

How fresh is the topology, incident, and adjudication data?

What is ready to act on right now, and what still needs confirmation?

State Model

Live state is assembled with explicit boundaries.

Launch Context

Lens starts with validated launcher context so the workspace boundary and operator authority are never ambiguous.

Workspace Scene

The product hydrates a live scene from launcher state, CTK intelligence bundles, and Replay models already published into the stack.

Freshness Posture

Every serious signal keeps freshness and source provenance attached so stale data cannot masquerade as live truth.

Partial Sources

Lens can still project a scene when one source is missing, but it keeps the gap explicit instead of inventing confidence.