Provider readiness schema
READYExpected schema v40.
Provider Production Readiness + QA Surface Lockdown Foundation
This gate binds the exact approved activation plan back through provider selection, deployed adapter artifact, observability profile, emergency-stop drill and rollback drill into one immutable readiness manifest. Staging can prove the evidence contract only. It cannot claim the production runtime, production evidence source, public-QA lockdown, production readiness, or live network traffic.
Readiness + lockdown self-test
READYRuns the server-owned evidence-binding, source-impersonation, QA-lockdown and live-traffic attack matrix.
Exercise the readiness boundary
GREEN means the QA preflight contract was accepted. EXPECTED BLOCK means Clara stopped a fake production claim. RED means something unexpected happened.
READYSafe flow should bind a real v0.12.40 QA activation plan into a preflight manifest while production readiness remains NO, QA remains public, and network remains NO.
PolicyLoad state after starting QA.
Readiness claims that must be blocked
Actions staging must never be allowed to prove
Readiness manifests
No evidence loaded yet.
Immutable readiness events
No evidence loaded yet.
Production readiness gates — do not fake these green
Leave these open until the exact real provider/deployment/monitoring/recovery/change-window evidence exists and the production deployment actually removes public QA controls. This page intentionally cannot turn on provider traffic.
Recent provider readiness QA runs
No QA runs recorded yet.
Evidence tools
Clearing browser evidence never rewrites server-owned readiness manifests or immutable readiness events.