# Proposed release-flag retirement packet

Status: proposed; no platform or deployed client tested.

Decision: make the new account-settings flow permanent for the supported population.

1. Record flag purpose, key, owner and chosen permanent behavior.
2. Classify it as a temporary release flag; retain operational controls under separate ownership.
3. Fill every cohort in consumer-matrix.csv, including unknown and dormant consumers.
4. Remove code references and the obsolete path; test the chosen behavior directly.
5. Deploy replacement code and collect version-specific behavior evidence.
6. Review rollback images, mobile support policy and cached browser bundles.
7. Resolve every unknown or explicitly retain the configuration dependency.
8. Use the provider lifecycle process to remove configuration only when required consumers no longer depend on it.
9. Complete acceptance.csv and keep the retirement record; do not casually reuse the flag key.