Capability Readiness Map

A flag requests exposure; server-side readiness decides whether work can start

Capability Readiness Map A flag requests exposure; server-side readiness decides whether work can start 01 / Operator Intent 02 / Server Decision 03 / Runtime Prerequisites 04 / Member Experience EX / Unavailable Path Request Prove readiness Expose or hold Enable · flag or allow-list · Operator Intent › Request Enable flag or allow-list Validate Config · dependency order · Server Decision › Request Validate Config dependency order One Decision · server-owned · Server Decision › Prove readiness · never browser-derived One Decision server-owned never browser-derived Prove Prerequisites · authority + capacity + policy · Runtime Prerequisites › Prove readiness · complete set Prove Prerequisites authority + capacity + policy complete set Expose Surface · route + tool + rail · Member Experience › Expose or hold Expose Surface route + tool + rail Start New Work · recheck at effects · Member Experience › Expose or hold Start New Work recheck at effects Hold New Work · history stays readable · Unavailable Path › Expose or hold Hold New Work history stays readable ready Legend User UI Agent logic Policy Cloud service External system

Tasks

  • • TASKS_ENABLED requests rollout
  • • All 20 capability families and attestation must be healthy
  • • Readiness loss closes new work immediately

Browser Sessions

  • • Flag, signed egress, Chromium, capacity, and TURN must agree
  • • A missing prerequisite refuses the session

External Tools

  • • Feature, egress, signing key, source consent, and exact operation policy combine
  • • Narrow risk flags remain independent

Rollback

  • • Disable dependencies in reverse order
  • • Stopping new work does not delete retained evidence