RPReleasePilot

Flowwright 2.0

Flowwright Controlled Target Routes

Replaces demo:// URLs with controlled internal demo target pages.

completed

Risk assessment

What this is: A weighted score from release attributes (blast radius, migrations, auth/billing touchpoints). Higher means more review before deploy.

medium
Risk score48/ 100

Complete checklist, confirm rollback readiness, and use extended monitoring.

  • Production deployment+18
  • Multiple modules affected (3)+9
  • Medium test coverage signal+5
  • Medium blast radius+6

Context

Environment
production
Migration
No
Rollback
full

Checklist

Required checks: Gates that must be green before you can queue this release in the simulator.

  • Preview sandbox sign-offRequired

Approvals

  • Chris Vega (Platform)Approved

Affected modules

  • Demo Sites
  • Plan Generator
  • Browser Preview

Rollback plan

Revert routing config and demo host map.

  1. Restore config map fw-demo-targets prior revision

Deployment simulation

Deterministic state machine — advances only when you click. Nothing provisions or deploys in the real world.

Current state: The timeline below reflects this run. After a rollback completes, use status updates and postmortem to document what happened.

Pipeline overview

Pipeline phases (simulator). Current phase highlighted.

  1. Queued
  2. Preflight
  3. Deploying
  4. Verifying
  5. Monitoring
  6. Spike
  7. Rollback rec.
  8. Rolling back
  9. Restored
Current stateidle

Step detail

  1. Queue releasepending
  2. Verify approvalspending
  3. Check rollback planpending
  4. Run testspending
  5. Apply migration (if applicable)pending
  6. Deploy buildpending
  7. Verify health checkspending
  8. Monitor error ratepending
  9. Complete or escalatepending

Verification checks

Synthetic signals: Mock pass / warn / fail used to drive the story (e.g. error-rate spike). Not connected to live monitoring.

  • Preview iframe originpass

Status updates

Template-generated — internal, customer-facing, and executive variants from current release context.

What this does: Fills three comms drafts you can copy — useful after rollback or during an incident.

No status update generated yet. Use "Generate status update" after an incident or deployment event.

Audit trail (this session)