A small domain model for keeping feedback status, roadmap visibility, release events, and customer notifications consistent.
Product feedback looks like a list until people begin making decisions about it.
A new request is reviewed. A reviewed problem may be planned, declined, or left open for more evidence. Planned work becomes active. A shipped change needs a release note and a notification to the people who cared about it.
If these transitions are implemented as arbitrary string updates, contradictory states appear quickly:
a declined request remains on the “In Progress” roadmap;
