Resources

One hub for learning, proof, and operational adoption material.

Resources collect the assets that sit around the product surfaces: docs, walkthroughs, replay demos, incident narratives, solution packages, and roadmap material. The goal is simple: give teams a clear path from first understanding to trusted operational usage.

Coverage

Docs pages

31

Featured collections

6

Solution packages

6

Primary products

3

How to use this page

Start from the question you need answered. Use docs for model clarity, walkthroughs for guided learning, replay demos for proof, incident stories for realism, and solutions or roadmap for team planning.

Featured Collections

The main resource shelves around the Core Trail Kit product line.

Docs

Global documentation

Shared core concepts, product-specific namespaces, integrations, and reference material across the full Core Trail Kit model.

Open Docs

Walkthroughs

Operational walkthroughs

Scenario-first learning for contradiction handling, evidence reading, safety gates, and operator-safe decision making in CTK Reason.

Read Walkthroughs

Replay Demos

Deterministic replay demos

Explore replayable decisions, confidence transitions, contradiction pressure, and how final operational truth was formed.

Open Replay Demos

Incident Stories

Real incident narratives

Review operator-facing stories where CTK Reason, Replay, and Lens turn noisy runtime signals into explainable action paths.

Read Incident Stories

Solutions

Packaged use cases

See how recurring operational problems map into product roles across CTK Reason, CTK Replay, and CTK Lens.

Open Solutions

Roadmap

Capability roadmap

Follow the capability evolution from deterministic reasoning foundations to broader multi-environment operational intelligence.

Open Roadmap

Start From A Question

Resource navigation should match the operator’s immediate need.

I need to understand the product model first.

Start from shared concepts, architecture, and product roles before moving into a specific product namespace.

Start With Core Docs

I need proof of how a decision was formed.

Go directly to replay demos and decision-oriented docs to see confidence movement, contradictions, and outcomes.

Open Decision Proof

I need examples from real incident pressure.

Read incident stories and walkthroughs to see how operators move from contradiction to safe action.

Read Incident Examples

I need to plan adoption and team rollout.

Use solutions and roadmap material to align on target workflows, outcomes, and capability sequencing.

Plan Adoption

Why Resources Exist

Docs explain the shared model and product responsibilities.
Walkthroughs teach how to read contradictions, evidence, and confidence in sequence.
Replay demos prove that decisions remain reconstructable and inspectable.
Incident stories show what the product looks like under real pressure.
Solutions package repeatable adoption paths for teams, not just individuals.
Roadmap material aligns product expectations with capability maturity.

Product Shelves

Browse resources by product surface.

Product Entry

Resources should hand off cleanly into product access and product setup.

This hub should not trap the user in reading mode. It should let teams step directly into CTK acquisition or installation detail once they understand the operating model.

Resources FAQ

The resource hub should explain what kind of material lives here.

What belongs in Resources instead of Docs?

Resources collect applied learning assets around the formal docs system, including walkthroughs, replay demos, incident stories, solution packages, and roadmap material.

Where should a team go for incident examples?

Incident stories and replay demos live in the resource hub because they show the operating model under pressure instead of defining the model formally.

How do Resources connect to product pages?

The resource hub should hand teams into product overviews, installation docs, and solutions once they understand the material they need.

Can Resources support adoption planning?

Yes. The hub includes solution packages and roadmap material so teams can move from product understanding into rollout planning.