Core Trail Labs
Core Trail Kit
CTK Replay
CTK Replay is the replay-first desktop product for evidence changes, contradiction pressure, confidence movement, adjudication, and final truth. It turns operational sequences into an explainable chain instead of a pile of disconnected runtime signals.
Replay Views
View 1
Executive Brief
View 2
Operational Timeline
View 3
Decision Ledger
View 4
Evidence Ledger
View 5
Truth Studio
Why it exists
Replay is for the moment after runtime intelligence exists and before operators are willing to trust it blindly. It explains how the current conclusion formed, what changed confidence, and where unresolved contradictions still remain.
Evidence linked to chains
100%
Contradictions kept explicit
Always
Outcome posture
Readable
Replay Window
Replay becomes valuable when a serious operational question is already on the table. It makes the current window legible: what triggered review, which evidence supports or weakens the story, and why truth was accepted, downgraded, or left unresolved.
Chain Trigger
runtime contradictionReplay starts from a serious workspace marker instead of asking the operator to stitch events together manually.
Evidence Weight
12 recordsSupporting, stale, and contested evidence stay in one sequence so trust posture remains inspectable.
Truth State
awaiting reviewFinal truth can remain open until adjudication is strong enough to defend operational action.
Product Boundary
CTK Replay is intentionally not the authority for login, workspace selection, source modes, provider selection, or observation setup. CTK Launcher owns those choices; Replay consumes validated context and turns it into a replayable operational model.
Core Surfaces
Operational Timeline
Reconstruct serious intelligence markers, contradictions, and adjudications as one chronological sequence.
Decision Ledger
Follow evidence, contradiction pressure, and truth shifts that shaped the current operational conclusion.
Evidence Explorer
Inspect replayable evidence records, chain scope, and subject-level provenance before accepting a conclusion.
Final Truth Summary
Surface the current truth posture, unresolved gaps, and the next actions that still need operator review.
How Replay Works
Replay works through explicit contracts: launch context, session bootstrap, and workspace reads. It then derives evidence, contradictions, confidence snapshots, decision chains, and final-truth summaries from that control-plane and operational input.
1. Launch
CTK Launcher authenticates the operator, selects the active workspace, and issues the wake context for Replay.
2. Bootstrap
Replay validates launch context, restores session bootstrap, and reads workspace signals through explicit contracts.
3. Derive
Signals become replay evidence, contradictions, confidence snapshots, decision chains, and final-truth summaries.
4. Publish
Replay can publish adjudication outputs back into the wider CTL ecosystem so Lens and other surfaces stay aligned.
Replay Readiness
Replay is designed to say when the story is strong, when the chain is partial, and when the workspace is not yet ready for trustworthy reconstruction. Operators should know whether they are reading a complete narrative or a shallow window.
Ready
Enough operational evidence exists to reconstruct replay chains with confidence.
Limited Fidelity
Signals exist, but the replay window is still too shallow for a complete operational story.
Unavailable
The workspace is connected, but replayable intelligence is not yet rich enough to support trustworthy reconstruction.
Operator Outcome
Portfolio Role
What Improves With Replay