Release cadence cockpit

The final release rhythm is now a product surface

Flow already has the scripts. This page makes the cadence operational: what runs daily, what runs weekly, what runs before release, where evidence is archived and which proof claims remain blocked.

Evidence archiveKPI targetsExport checklist

Decision

Cadence is wired, external proof remains explicit

The run rhythm is now ready for production operations. The last open rows are still live/infra proof, not missing product surfaces.

5

cadence runs

3

release levels

5

guardrails

Runbook

Daily, weekly and release-candidate evidence flow

Daily · Platform Ops

Morning run

gate:flow:release-morning-run

scripts/flow-release-morning-run-live.ps1

Keeps the release board warm without pretending the CI ring is green.

  • release-status-board
  • blocker-snapshot
  • command-map
  • daily-brief

Weekly · Product + Revenue Ops

Executive pack

gate:flow:release-exec-pack

scripts/flow-release-exec-pack-live.ps1

Turns product depth into a board-level proof pack.

  • system-evaluation
  • competitor-gap-matrix
  • payment/integration/widget/chat/booking/ticket chains

Before planned release · Release Owner

Master release run

gate:flow:release-master-run

scripts/flow-release-master-run-live.ps1

Final operator path before release promotion.

  • exec-pack
  • unblock-plan
  • unblock-progress
  • release-cockpit

Weekly · CTO/Product

System evaluation

gate:flow:system-evaluate

scripts/flow-system-evaluate-live.ps1

Keeps readiness percentage tied to evidence instead of vibes.

  • system-evaluation
  • readiness trend

Weekly · Product Strategy

Competitor gap matrix

gate:flow:competitor-gap-matrix

scripts/flow-competitor-gap-matrix-live.ps1

Keeps competitor parity claims honest.

  • competitor-gap-matrix
  • gap closure trend

Guardrails

Prevent false green

  • Do not mark staging/production ring proof green until CI auth secrets exist.
  • Do not mark provider replay green until at least one real connector family has credentials.
  • Do not mark funnel completeness green until live traffic includes lead, booking and paid events.
  • Do not mark enterprise trust final until independent security review is complete.
  • Keep every run attached to an artifact path, owner and next action.

Next operator move

Run the cadence after secrets/provider proof exists

This page is the handoff between product development and production operations. When CI secrets, connector credentials and live traffic proof are available, these commands produce the evidence needed to close the remaining TODO rows.