Enumeration

Cuts a vague mass into discrete items on their own lines, so the set can be counted, worked, ordered, and closed.

You tell a friend the article is nearly finished, and you believe it. Then you sit down and it is not finished, and you cannot say what is left. The work is one lump in your head, and a lump has no edges. You cannot count it, you cannot close it, and you cannot tell whether the thing you keep forgetting is a small task or the whole ending.

Enumeration cuts the lump into items and puts one per line. That is the whole mechanism, and it does three things at once. It makes each item discrete, so it can be named, ticked, moved, or deleted on its own. It makes the set countable, so "nearly finished" becomes "two of six". And it closes the set, which is the part people skip past: once the list exists, whatever is not on it is visibly not on it. The gap you kept walking around gets a row of its own.

There are four renderers and they add capability in order. A plain list is membership only, and the order of the rows carries no claim. A checklist adds state to each item, so the list can be worked rather than read. Numbered steps add order that means something, where item three fails if item two has not run. A ranked list adds one stated dimension, and it is honest only as long as that dimension stays written down.

Reach for it when the question is what are all of them, or which of them is done, or what order do I do them in. It is weak at everything between the items. A list of nine reasons the same argument keeps happening tells you nothing about which reason feeds which, and if you keep staring at the rows waiting for the relationship to appear, you have picked the wrong form and the list will not tell you so.