Readiness Gates — Platform Health and Launch Criteria

readiness gates are the set of binary green/yellow/red probes that determine whether a service or feature is fit for production traffic. OpenVibe runs readiness checks offline, against live infrastructure, and as part of CI.

Green gates: all required functionality works correctly with no known regressions. Yellow gates: deferred or partial — feature is implemented but not fully wired or tested under production conditions. Red gates: blocking — the feature is broken, missing, or actively harmful.

The readiness report is generated by `npm run readiness` from the openvibe monorepo root. It probes each service, checks schema parity, and outputs a JSON report with per-gate status.

Gates are intentionally honest: do not flip a gate to green by silencing a check. Yellow is acceptable for deferred features. Red is always a blocker.