What is ready, pending deployment.
These entries describe a verified release candidate, not generally available production behavior. Availability begins only after its deployment and post-deploy checks pass.
Canonical product contract: release candidate
Pending deployment: plan, scoring, certificate, and feature-availability copy derives from a versioned backend contract and fails when the frontend snapshot drifts.
Deterministic score authority: release candidate
Pending deployment: terminal commands and output produce bounded evidence bands; the server computes the weighted rubric score.
Certificate verification wording: release candidate
Pending proof migrations and deployment: the verifier can check an eligible server-issued record and SHA-256 evidence hash. It does not claim an external chain.
Availability labels: release candidate
Pending deployment: unverified integrations and workflows remain disabled until their configuration and runtime checks pass.
Public runtime cleanup: release candidate
Pending deployment: public routes fail closed on missing configuration and omit authentication tokens, cookies, and diagnostic breadcrumbs from browser output.