Are production changes staying stable?
See whether production changes stay stable through the agreed observation window, without claiming that a nearby incident was caused by the change.
A recipe turns questions into decisions.
First it agrees what the question means, then connects only the data it needs, and only then keeps a live answer.
- QuestionThe team agrees what it needs to know.
- Agreed definitionClarifies what counts, the expected level, and who decides.
- Data it needsOnly the minimum data needed to answer is connected.
- Live answerThe answer stays up to date.
- DecisionAct, stay the course, or wait.
What you'll do with the answer
The answer makes the next move clear—and is just as clear when the right move is to wait.
Continue the rollout
Completed changes are staying stable at the rate Platform agreed.
Pause or revert
Too many completed changes have rolled back or failed, so Platform needs to respond.
Keep observing
Changes still inside the observation window do not count as stable or failed.
What Soltura needs
Follow every production change through the observation window agreed by Platform. Record stability, rollback, or failure without assigning incident cause.
Change deployed
The release system confirms when a production change begins.
Observation window
Platform defines how long the change must remain under observation.
Stable result
The window ends with the change still operating as expected.
Rollback or failure
The release system explicitly records that the change was reverted or failed.
After at least 20 changes have completed their observation window or reached a clear rollback or failure result
Where it fits
A good fit when
- Platform agrees the observation window before the rollout.
- The release system clearly records rollback or failure.
- Platform owns the continue, pause, or revert decision.
Choose another approach when
- The observation window or included production changes are not clearly defined.
- A nearby incident is being used to claim that the change caused it.
- Missing monitoring would be treated as a stable result.
- You need deployment frequency, lead time, or individual engineering productivity.
- The release system cannot provide a clear stable, rollback, or failure result.
Bring this answer into your project
Give every rollout a clear continue, pause, or revert decision.
Soltura prepares the question, observation window, decision level, and deployment result your release system needs to send. Your project checks the complete change before anything happens.
Nothing changes until your project reviews and approves the proposal.