CB.5:4.6 - Return, accept, revise or stop

Give the recipient the contribution together with what determines its use: the question, applicable conditions, evidence or domain basis where needed, and unresolved limits. Use the existing discussion or work record when it can carry these facts.

Ask the recipient to return a meaningful disposition. Examples include: used as supplied; accepted for a stated later use; useful after a specified change; declined because a condition or requirement differs; or not yet assessable because a needed basis is missing. Explain the reason that can improve the contribution or prevent inappropriate reuse.

Agree further work rather than silently extending the original commitment. A small correction within the accepted task can proceed with the contributor’s available effort. A materially different request, repeated revisions or a new maintenance obligation needs a revised arrangement.

Close a failed contribution honestly. When no suitable helper is available, return the unanswered question and a possible source or service route. When the user cannot act, distinguish missing access from an unusable answer. When the product team will not inspect suggestions, stop inviting that kind of work until a receiving arrangement exists.

For an operational case, OPS.6 separates selection, performance and the resulting state. Use that distinction whenever a message or record update could be mistaken for a completed intervention. A technical answer, performed work and restored functioning have different evidence.