Last Updated: 2026-02-24
Scope: WS18-007 post-launch stabilization sprint and top incident-class
burn-down.
Purpose#
Define a repeatable stabilization sprint artifact that prioritizes the highest incident classes and tracks week-over-week burn-down targets.
Artifacts#
docs/domains/isis/remediation-v2/ISIS_V2_POST_LAUNCH_STABILIZATION_SPRINT.jsondocs/domains/isis/remediation-v2/ISIS_V2_POST_LAUNCH_STABILIZATION_SPRINT.md
Generator#
bash
node scripts/isis/generate-v2-post-launch-stabilization-sprint.mjs
Options:
--sprint-start=YYYY-MM-DD--duration-days=<int>--top-class-count=<int>
Validator#
bash
node scripts/isis/validate-v2-post-launch-stabilization-sprint.mjs
Inputs Used for Burn-Down Ranking#
- Creative on-call triage reports:
tmp/isis-oncall/**/creative-pipeline-oncall-triage-*.json
- Release failure game-day reports:
tmp/isis-release-failure-gameday/**/release-failure-gameday-*.json
Operational Cadence#
- Generate stabilization sprint artifact at launch + weekly thereafter.
- Confirm top incident classes and owner assignment in sprint review.
- Track week1/week2 target counts per incident class.
- Re-run verification checks listed per class and update carry-over items.
- Attach sprint artifact to release governance evidence packet.
Related Artifacts#
scripts/isis/run_creative_pipeline_oncall_triage.shscripts/isis/run_release_failure_gameday.shdocs/domains/isis/runbooks/creative-pipeline-oncall.mddocs/domains/isis/remediation/ISIS_POST_INCIDENT_REVIEW_TEMPLATE.md