confighub-source-truth

Compare ConfigHub, GitOps controller, and Kubernetes runtime for strategy conformance.

14|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/confighub/cub-scout --skill confighub-source-truth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: confighub-source-truth
Source: https://github.com/confighub/cub-scout/tree/main/skills/confighub-source-truth
Command: npx skills add https://github.com/confighub/cub-scout --skill confighub-source-truth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produces a deterministic source-truth verdict for a declared delivery strategy by checking whether ConfigHub, the controller, and the live cluster agree on the same facts.

Core Features & Use Cases

  • Strategy-typed verdicts: Enforces that the user provides an explicit delivery strategy and compares surfaces accordingly, never inferring the strategy.
  • Evidence-grade comparison: Generates structured evidence with status and verdict (PASS/WATCH/BLOCK/ASK and AGREED/MISMATCH/INCOMPLETE/BLOCKED/UNKNOWN) plus proof gaps and a safe next action.
  • Receipt persistence for acceptance: Optionally verifies and saves a fingerprinted receipt artifact for audit or Pilot-acceptance kernels.

Use case: Gate a release or Pilot acceptance by asking, for example, whether a specific deploy/api resource matches the required git-argo or confighub-oci-flux strategy before approving promotion.

Quick Start

Ask the system to compare source-truth for deploy/api in namespace prod under strategy git-argo and return JSON evidence.

Frequently Asked Questions about confighub-source-truth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify GitOps controller and Kubernetes live state conformance?

You can verify GitOps source-truth by comparing ConfigHub, the controller, and the live cluster against an explicitly declared delivery strategy to generate a deterministic source-truth verdict.

What is a source-truth verdict in a GitOps delivery pipeline?

A source-truth verdict determines whether ConfigHub, the GitOps controller, and the live Kubernetes runtime agree on the same facts under a declared delivery strategy, returning statuses like AGREED or MISMATCH.

How do I check if ArgoCD or Flux matches the declared ConfigHub strategy?

To check if ArgoCD or Flux matches your declared ConfigHub strategy, run an acceptance-style check in connected mode with a mandatory selected strategy to return structured evidence and proof gaps.

Can I gate a release by checking Kubernetes configuration conformance?

You can gate a release or pilot acceptance by verifying if a specific deploy/api resource matches a required git-argo or confighub-oci-flux strategy before approving promotion.

Does verifying GitOps strategy conformance require a specific environment?

Verifying GitOps strategy conformance requires connected mode and mandates selecting an explicit delivery strategy, ensuring the system never infers the strategy during the source-truth comparison.

How do I save an audit receipt for a Kubernetes delivery strategy check?

You can save an audit receipt for a Kubernetes delivery strategy check by enabling optional receipt verification, which persists a fingerprinted artifact for audit or pilot-acceptance kernels.