Core

Architecture

The architecture is deliberately opinionated. CTK Launcher is authoritative, products remain scoped, and no product silently takes over a responsibility that belongs somewhere else.

Authority stays in LauncherReason structures intelligenceReplay explains truth formationLens projects the scene

Back To Docs Hub

Page Focus

See how CTK Launcher, Reason, Replay, Lens, and integrations divide responsibility across authority, intelligence, replay, and scene projection.

Authority stays in Launcher

Identity, workspace selection, access, and runtime launch boundaries remain centralized in CTK Launcher.

Reason structures intelligence

Reason observes runtime and topology context, builds evidence, resolves contradictions, and emits confidence-aware truth.

Replay explains truth formation

Replay reconstructs the causal sequence from evidence and contradictions to adjudication and current outcome.

Lens projects the scene

Lens turns shared product state into a read-only visual workspace model with provenance and freshness still attached.

Questions This Page Answers

Why is Launcher authoritative?

Which product should own truth, replay, or visualization?

How do integrations feed the global model?

Move across the shared CTK documentation model.

Getting Started

/docs/getting-started

Integrations

/docs/integrations

Reference

/docs/reference