Feedback informs the next question rather than closing the last one.
Usefulness, gaps and corrections, followed by a deliberate close, reopen or retask decision.
How it works
Feedback is bound to an actually acknowledged release package and its recipient. It can record usefulness, gaps and corrections, with controlled amendments and retained response history.
Boundaries
A response records the observed Direction outcome; it does not secretly perform that transition. A responsible user separately closes, reopens or retasks the originating requirement.
Feedback and outcomes
Element
Feedback
Versioning
Response history
Human decision
Owner decides
Status
Implemented