Core Trail Labs
Core Trail Kit
CTK Lens
CTK Lens is the read-only visual workspace intelligence surface in the Core Trail Labs product line. It consumes launcher-authoritative workspace observations, CTK Reason topology intelligence, and CTK Replay adjudication signals without becoming the authority for any of them.
Lens Surfaces
View 1
Workspace Status
View 2
Topology Map
View 3
Incident Panels
View 4
Live Timeline
View 5
Truth And Provenance
Why it exists
Lens exists for the operator who needs the current workspace story at a glance: which nodes are live, where contradictions landed, what incidents are active, and how recent truth decisions should affect the next action.
Signal authors stay visible
3 streams
Workspace story posture
Live
Scene mode
Read-only
Scene Model
Operators trust CTK Lens when they can still tell where workspace authority ends, where reasoning begins, and where adjudication changed the current posture. The scene is richer because those boundaries remain visible instead of being collapsed into a decorative graph.
Authority Layer
workspace scopeCTK Launcher defines who the operator is, which workspace is active, and what boundary Lens should render.
Intelligence Layer
ctk + replayCTK Reason and CTK Replay publish different kinds of intelligence, and Lens projects both without flattening ownership.
Visual Layer
scene projectionTopology, incidents, overlays, provenance, and freshness become one legible workspace picture.
Product Boundary
CTK Lens does not select workspaces, issue credentials, run observation setup, or silently rewrite product truth. It projects what the wider CTL stack already knows into one visual model while keeping freshness and provenance attached to every serious signal.
Core Surfaces
Live Workspace Topology
Project launcher-authoritative workspace scope, service relationships, and operational edges into one readable scene.
Source Provenance
Keep Launcher, CTK Reason, and CTK Replay signals visibly separate so operators know who authored each claim.
Incident Projection
Raise incident overlays, contradiction pressure, and evidence counts directly on the nodes and edges that matter.
Situational Awareness
Combine topology, timeline, incidents, and final-truth posture into one read-only operational picture.
How Lens Works
Lens restores launcher context, reads shared product state, and projects it into a workspace scene. That scene carries topology shape, signal provenance, incident overlays, evidence metrics, and timeline context so the operator can orient quickly without switching across tools.
1. Launch
CTK Launcher validates operator access, restores workspace context, and issues Lens the scoped launch contract.
2. Hydrate
Lens reads launcher state, CTK intelligence bundles, and Replay models without taking ownership of any of them.
3. Project
Signals become a live scene with topology nodes, overlays, incident panels, evidence counts, and timeline entries.
4. Monitor
Push refresh and local state reads keep the visual scene aligned as workspace conditions and adjudications evolve.
Signal Streams
Different products publish different kinds of intelligence. Lens does not blur those boundaries. It keeps signal ownership visible so operators can distinguish authority, reasoning, and adjudication at a glance.
Launcher
Authority, workspace boundary, session context, and local observation runtime.
CTK Reason
Topology analysis, contradiction overlays, evidence ledger counts, and operational intelligence.
CTK Replay
Decision chains, adjudications, evidence lineage, and accepted final-truth posture.
Operator Outcome
Portfolio Role
Next In Lens