Verixetverify-self health checks
One round trip proves the control plane you depend on is coherent before traffic does.
What verify-self answers
GET /api/v1/control-plane/verify-self returns the standard v1 envelope. Inside data, checks such as config_valid, health_valid, database_reachable, namespace_consistency, and auth_mode tell you whether this deployment is internally consistent — before you rely on it from CI or production traffic.
When a check fails
Treat a non-passing matrix as a hard stop: the failure names the subsystem (configuration drift, DB reachability, namespace mismatch, auth misconfiguration). Fix the underlying issue, then rerun the same endpoint — request_id still applies for log correlation.
Automation
Run verify-self from deploy pipelines after configuration changes, and on a schedule in long-lived environments so drift is caught before it becomes an incident. The marketing homepage renders a live matrix illustration of the same conceptual checks for quick human scanning.