Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-10-14 19:58:00 UTC · snapshot created 2026-10-14 19:58:38 UTC · last check 2026-10-15 05:30:05 UTC

B.5.SD:4.1 - Name the receiving question and the kind of answer needed

Identify who will use the result and what that person or agent needs to settle or do. Ask for a representative use: a release decision, a revised explanation, an architecture choice, a research design, or a next action in a difficult task.

Distinguish the result required. An explanation relates what is known and why; a proposal states what could be done and on which grounds; an inquiry proposal identifies an unresolved question and a way to answer it; an agreement records accepted contributions. A discussion can produce more than one, but one does not substitute for another. Use LDR.2 when the unresolved result is acceptance of contributions rather than subject understanding.

Set a useful completion condition. For a configuration review, the receiver may need to know which claim is supported for the current configuration, which remains unsupported and which observation would settle the gap. “Everyone understands the issue” is not enough if the receiver still cannot distinguish those claims.

Recover an adequate existing answer before assembling new work. If the relevant model already supplies the needed explanation under current conditions, explain its application and stop. If the receiving use differs, identify the difference that changes the inference instead of rejecting the whole earlier result.