Tab 4. Version, who wrote Issie, and what it is written in. Fourth because nobody opened this window for it. Takes the version because that is a fact about the build, not text.

Tab 3. What to send when reporting a bug, in the order it is useful to collect it. What a bug report has to tell us that Issie cannot work out for itself. **Data rather than prose, because they are needed in two places**: read here, and again as a form to fill in inside the report the Copy button produces. Written once so the two cannot come apart - the same reason the keyboard shortcut table is generated from the dispatch table rather than written out. Everything a machine can answer - version, platform, what Issie complained about - is collected automatically and is deliberately not asked for here.

Tab 1, and what the window opens on. The first five minutes in order, then what happens when something is wrong, then the two facts about Issie that cannot be worked out by looking at the screen. It says what to DO before it says what Issie is: somebody who has just launched an application wants to get somewhere.

Tab 2. The things people most often do not find. A table so that the name of each is scannable down the left without reading the explanations.