Docs

Global documentation for the Core Trail Kit product line.

The new docs model is shared by core concepts and product namespaces. Reason, Replay, Lens, Integrations, and Reference now live under one route system instead of fragmented product-local documentation.

Core ConceptsReasonReplayLensIntegrationsReference

Start With Docs Open Reason Docs

Coverage

Total docs pages

Documentation groups

Product namespaces

How to use this hub

Start with Core if the team needs shared language, then move into product namespaces for product-specific semantics. Integrations explain evidence coverage. Reference stays as the stable lookup surface.

Core

Shared concepts, startup model, and architecture across the CTK product line.

Overview Getting Started Core Concepts Architecture

Reason

Operational truth, evidence, contradictions, confidence, topology, and safety-gated reasoning.

Overview Installation Source Modes Evidence Topology Contradictions Confidence Safety Gate Operational Memory

Replay

Replay chains, reconstruction fidelity, causal lineage, confidence movement, and final outcomes.

Overview Replay Chains Reconstruction Causal Lineage Confidence Evolution Decision Outcomes

Lens

Live scene hydration, signal provenance, incident overlays, topology focus, and situational awareness.

Overview Live State Signals Incidents Topology View Situational Awareness

Integrations

Environment-specific evidence paths for Docker, Kubernetes, AWS, Azure, and GCP.

Overview Docker Kubernetes AWS Azure GCP

Reference

Stable ownership and route mapping for the global CTK documentation system.

Reference

Get CTK

Move from docs into the launcher flow.

Installation intent should have a direct path from documentation into the real CTK acquisition route.

Open Get CTK

Resources

Use the learning shelves around the docs system.

Walkthroughs, replay demos, incident stories, and roadmap pages extend the formal docs surface with applied material.

Open Resources

Solutions

Map concepts into operational use cases.

Solutions turn the product model into named operational problems, adoption patterns, and target outcomes.

Open Solutions

Documentation FAQ

Questions the docs hub should answer immediately.

Is Core Trail Kit documentation global or product-local?

The new documentation model is global. Core concepts, product namespaces, integrations, and reference routes now live under one shared docs system.

Where should a new team start in the docs?

Teams should start with Getting Started, Core Concepts, and Architecture before moving into the Reason, Replay, or Lens namespaces.

How are integrations documented?

Integrations are documented as evidence pathways. Docker, Kubernetes, AWS, Azure, and GCP explain what each environment exposes and how coverage changes trust.

Where do CTK Replay and CTK Lens docs live?

Replay and Lens each have their own namespaces under the global docs route so they can grow without fragmenting the navigation model.