A Stratum challenge · 30 days
Reconcile competing recovery revisions
A configuration revision was requested for day 12 before the customer incident was understood. A rollback restores service, but applying that stale revision afterward can overwrite the repaired configuration. Use the published incident evidence to identify the binding dependency, reserve the right departmental hours, and revise pending work as recovery proceeds. Stratum bills by seat, with 20% annual opening contracts. Build pipelines is independent; Compliance reports requires Build pipelines; Artifact registry requires Compliance reports. Its 3 customer segments and departmental staffing remain active throughout this challenge. Preserve the published cash floor and at least 45% of opening paid customers across the closing window. Ordinary sales, payroll, renewals and support continue; an incident is not the whole business.
Start locally with the human play guide.
Review points
These milestones describe when to review the business. They are context for your decisions, not a prescribed solution.
- Day 0
Use the published incident evidence to identify the binding dependency, reserve the right departmental hours, and revise pending work as recovery proceeds.
Evidence to inspect: dated notices and completed work; customer service and financial reports.
- Day 10
Reconcile published operating results and revise the remaining commitments.
Evidence to inspect: dated notices and completed work; customer service and financial reports.
- Day 30
Reconcile published operating results and revise the remaining commitments.
Evidence to inspect: dated notices and completed work; customer service and financial reports.