← Back to Daily Builds

Daily build note · September 30, 2026

Change Preflight

Score a proposed change for blast radius, rollback readiness, and go/no-go before you ship.

Personal Utilities Interactive demo live Static HTML/CSS/JS

What shipped

Change Preflight is a self-contained browser tool for a 60-second ship check. Title the change, write a short summary, toggle surfaces touched (API, Database/schema, Auth, Billing, UI, Emails, External deps, Infra, Data migration, Feature flags — weighted toward higher-risk areas), set confidence 1–5, pick a rollback ETA (5 / 15 / 60 / 240+ minutes), and fill rollback + detection plans. A live score panel shows blast radius, readiness, and a GO / CAUTION / STOP badge. The markdown receipt updates live; Copy receipt dumps it for Slack, Notion, or a release thread. Presets cover Hotfix, Feature-flag flip, and Schema migration. Optional localStorage under change-preflight-v1. Heuristic only — not a formal change-management system.

How to try

  • Open the live demo (iframe on the right, or full-page link below).
  • Load a preset (start with Hotfix vs Schema migration to feel the score swing).
  • Toggle surfaces and rollback chips — watch blast, readiness, and the GO/CAUTION/STOP badge update.
  • Hit Copy receipt and paste into a release channel or agent prompt.

Scope trim

No approvals workflow, no ticket sync, no pager integration, and no multi-reviewer sign-off. One change, one heuristic score, one markdown dump, local persistence only. Scores are transparent weights — not a substitute for your CAB or on-call runbook.

Limitations

  • Blast and readiness are local heuristics from surface weights, confidence, rollback speed, and whether plan text is filled.
  • Clipboard copy needs permission; otherwise select the receipt manually.
  • Timestamps use the browser’s America/Chicago-friendly locale formatting when available.
  • Not a formal change-management or compliance system — use it to think clearly, then follow your real process.

Suggested next steps

  1. Optional “risk owners” field and required-reviewer checklist for STOP verdicts.
  2. Export a .md download in addition to clipboard copy.
  3. Tiny library of org-specific surface weights beyond the ten defaults.