Core Trail Kit logo

Core Trail Labs

Core Trail Kit

Understanding Decisions

How CTK explains every blocked, allowed, and downgraded decision.

Use these pages whenever you ask: "Why did CTK decide this?" Each explanation follows one deterministic frame: Scenario, Evidence, Contradiction, Confidence Shift, Decision Outcome, Operator Meaning, and Replay Summary.

Why did CTK block this action?

Scenario: Operators attempted a restart during high incident pressure.

Evidence

  • Health checks remained green
  • Runtime latency spikes persisted
  • Log stream freshness degraded
  • Contradiction remained unresolved

Contradiction: External health and runtime behavior confidence diverged.

Confidence shift: 0.71 -> 0.43

Decision outcome: Safety Gate blocked restart and required fresh evidence before retry.

Operator meaning: A blocked action means risk posture is not yet safe for high-impact mutation.

Replay summary: Replay chain shows contradiction + freshness penalty crossing block threshold.

Why did confidence drop?

Scenario: Runtime anomalies continued while corroborating evidence streams slowed.

Evidence

  • Active incidents increased
  • Runtime status oscillated
  • One key log source became stale

Contradiction: Signal quality diverged from expected runtime stability.

Confidence shift: 0.82 -> 0.56

Decision outcome: Recommendations moved from allowed to review state.

Operator meaning: Confidence drop is a trust signal; slow down disruptive remediation.

Replay summary: Replay timeline links each confidence decrement to contradiction persistence.

Why was this recommendation allowed?

Scenario: Consumer lag fell after scaling and fresh logs restored evidence quality.

Evidence

  • Fresh logs resumed
  • Lag trend reversed
  • Throughput stabilized
  • Contradiction cleared

Contradiction: No active contradiction remained in impacted service path.

Confidence shift: 0.59 -> 0.86

Decision outcome: Recommendation moved to allowed under policy threshold.

Operator meaning: Allowed means trust threshold is met, not blind auto-execution.

Replay summary: Replay chain highlights confidence recovery after corroborated evidence alignment.

Why was evidence marked stale?

Scenario: Mapped provider logs stopped updating while incidents remained active.

Evidence

  • Last log update exceeded freshness window
  • Incidents still open
  • Health probes unchanged

Contradiction: Stable status claims conflicted with missing diagnostic freshness.

Confidence shift: 0.68 -> 0.49

Decision outcome: Freshness penalty triggered review/blocked actions.

Operator meaning: Stale evidence means trust is decaying even if one signal stream is calm.

Replay summary: Replay graph shows freshness degradation as a direct confidence penalty.

Why did topology confidence collapse?

Scenario: A dependency edge disappeared after deploy while request failures increased.

Evidence

  • Topology delta removed edge
  • Request retries climbed
  • Fallback route logs increased

Contradiction: Expected relation map and observed runtime path diverged.

Confidence shift: 0.77 -> 0.51

Decision outcome: CTK downgraded relation trust and gated broad rollback path.

Operator meaning: Topology confidence collapse indicates dependency-level incident risk.

Replay summary: Replay chain maps edge removal moment to confidence degradation timing.

Why was a contradiction created?

Scenario: Status looked healthy while throughput and consumer behavior degraded.

Evidence

  • Green health probes
  • Queue lag increase
  • Throughput decline
  • Runtime warning events

Contradiction: Health posture and behavior posture could not both be true operationally.

Confidence shift: High -> Medium

Decision outcome: CTK created contradiction state and fed it into adjudication and safety policy.

Operator meaning: Contradiction is explicit conflict modeling, not anomaly noise.

Replay summary: Replay chain shows exactly which evidence branches produced the contradiction node.

See this in product context

Docs to Trial Path

Turn concepts into live operational reasoning

1. Replay first

Open a deterministic replay to see evidence, contradiction, confidence, and gate state in one chain.

Open Replay Demo

2. Install desktop

Download CTK Desktop and run local-first observation for your workspace runtime boundaries.

Download Desktop

3. Initialize workspace

Connect repo + source mode, then start deterministic timeline and contradiction-aware recommendations.

Initialize Workspace