01 / A request
Something has been asked.
A request tells you about an intended action. It does not by itself establish the result. Keep the acknowledgement of a request distinguishable from the evidence that the work completed.
States / Interfaces / Feedback
A clear signal
needs a clear meaning.
Separate what is wanted, what was requested and what the available evidence actually establishes. A readable interface begins with those distinctions.
Open the state and feedback guide →02 / An observation
Something can be established.
An observation supports a statement about what happened or what is now available. Name the source and its limit so the label does not imply more certainty than the signal provides.
| Term | What it describes | Question to ask |
|---|---|---|
| Intent | The outcome someone wants. | Which question or need does the action address? |
| Request | An instruction to begin or change something. | What confirms that the request was received? |
| State | The condition the system is understood to be in. | Which source establishes this condition? |
| Feedback | Information returned about the action or state. | What does the signal allow the reader to conclude? |
04 / A worked state description
A refresh has
more than one moment.
Consider a view that requests updated information. Describe the stages before deciding which message belongs in each one.
-
Requested
The instruction has been made. Identify the acknowledgement that supports this label.
-
In progress
The expected result is not yet established. Describe what is known without using completion language.
-
Observed result
The agreed evidence is available. State what it confirms and which context belongs with it.
-
Unknown or interrupted
The available signal does not establish the expected result. Keep that condition distinct from success and name the next useful question.
05 / Read the difficult signal
Follow the meaning
back to its source.
A label can look precise while its source remains unclear. Use the questions to locate the missing distinction.
The label changes before the result is known.
Identify which event changes the label and which event would support the conclusion a reader might draw. Keep those events separate in the working record.
Different views show different states.
Record which source each view uses and the context of the observation. Do not assume that the most prominent display is the authoritative one.
The response does not answer the request.
Return to the intended outcome and the meaning of the signal. A response can be valid information while leaving the original question open.