How to read the tags
Not everything on this site is known equally well. The pages say how far a statement can be trusted, either with a tag in square brackets or in words, and they say it wherever a statement is only inferred. There are two levels.
| Tag | In words | Means |
|---|---|---|
[C] |
“confirmed”, “seen in play”, “confirmed under emulation” | We read it in the game’s own program and checked it a second, independent way, with matching results: against the running game, against a rebuild that gives the same results for the same inputs, against another part of the program, or against every row of the game’s data that it explains. |
[I] |
“inferred”, “read from the code” | We read it in the game’s own program and understood it, but have not yet checked it a second way. |
A few points help when you rely on them:
- An inferred statement is not a guess. It rests on the game’s program, not on memory or hearsay. It has just not been checked independently yet, so it is where a rebuild should be most careful.
- A confirmed statement covers what was checked. When a page says a check met only some cases, the confirmation reaches only those cases; the rest is inferred, and the page says so.
- Ideas we hold only as leads are left out. A claim from another source, or a hypothesis, appears on this site only once the game’s program has been read for it, and then as our own statement with its level; until then it is not here.
- What is not known is said. Many pages end with a What is not known yet section. It names the open points in words, so that a page is never read as more complete than it is.
- Diagrams and animations carry no tag. They illustrate the text next to them. When a picture and the text differ, the text is what counts.
The topic pages and the glossary are prose and use the words. The bracketed tags are the short form of the same two levels; they mark statements set out step by step in the project’s specifications, which are not part of this site yet.