---
title: Evidence And Authority
status: current
last_reviewed: 2026-06-14
---

# Evidence And Authority

Different checks prove different boundaries.

Render parity proves that the installer-rendered object set matches regular
Helm for recorded inputs. ConfigHub proof proves that objects can be represented
and operated as Units. Local Kubernetes evidence proves that a rendered object
set can apply and converge on a named target shape. GitOps/OCI evidence proves
that a controller pulled and reconciled the ConfigHub-published source.

Production support is still target-scoped. A green render does not prove every
cluster, every cloud, every security policy, or every upgrade path.

When a page, receipt, and generated matrix disagree, trust the generated data
and receipt first, then update the page.

## Authoritative Sources

- [Claims register](../../data/claims-register/summary.md)
- [Outcome evidence contract](../../data/outcome-evidence-contract/summary.md)
- [Verification lanes](../../docs/user/verification-lanes.md)
- [Chain of proof](../../docs/user/chain-of-proof.md)
- [Tests README](../../tests/README.md)
- [NPM script catalog](../../tests/npm-scripts.md)