Define the replacement with current users before the company retires a relied-on workflow.
A product surface has a real maintenance cost or platform limit, but removing it without a replacement would transfer that cost to users.
Define the complete obligation before opening the decision.
This dossier keeps the business trigger and the expected public record in one ordered view.
Why this needs a bounded decision
A product surface has a real maintenance cost or platform limit, but removing it without a replacement would transfer that cost to users.
Ask the people who carry the consequence
Users who used the affected feature during a declared recent period. Do not ask the complete customer base when most people never used it.
State the failure the contract must prevent
The company retires a relied-on path before a supported replacement exists, while a broad vote hides the cost carried by current users.
Match the ballot to the evidence needed
Use approval so participants can mark every replacement they can accept. This shows whether one path has broad support or several paths are required.
State what the company will publish
Publish the supported replacement and retirement sequence. Keep the old path until the promised replacement reaches the stated availability level.
Show what changed after the answer
Northwind Reports chose a secure download centre, shipped it, and only then started the weekly-export retirement window.
Replace a feature before deprecation
Define an acceptable replacement, publish the decision, and keep the old path until the replacement is ready.
Review the contractInspect the outcome state in context
See how this part of the contract remains attached to the other decision states.
Open the relevant demonstration stateReplace a feature before deprecation
The template opens a reviewable Create form. It does not submit or publish automatically.