A contextual release checklist instead of one giant document. Pick a preset, toggle the components actually involved, clear blockers, export the evidence and keep the state locally in your browser.
Queries and references suggested automatically from the selected component packs.
Local history
Archived snapshots
Stored only in this browser via localStorage.
Why this exists
Deployment memory should not live in adrenaline.
The checklist intentionally combines platform mechanics, data-contract checks and post-deploy evidence. If a failure teaches a reusable lesson, it should become a checklist item, runbook or production bite.
Contextual
Only show what applies
A Journey + Automation deployment gets different checks from a CloudPage or API integration.
Evidence
Post-deploy is part of deploy
Activation is not completion. First run, first contact, first send and health signals are explicit checklist phases.