installation-fallback.svg
INSTALLATION-BOUND ANSWERS A fallback answers less, and says so Every path runs outside this process; the shortfall travels with the result instead of being hidden. what the machine allows one square = one entry the registry could return A console command exists Typo3Cli::run() answeredBy: installation No command — boot the runtime Typo3Runtime::ask() answeredBy: installation Failsafe mode, or unreachable package files, read not executed answeredBy: packages dynamic registrations, never read A partial registry never looks complete: source, reason and the unread files travel with the result. The two full paths differ in cost, not in what they know — which is why they are drawn identically.
What the rules had to survive here: a fallback chain is naturally a flowchart — decision diamond, two branches, four arrows. Redrawn, the sequence is the reading order and the registry itself is drawn: one square per entry it could return. The gap in the third row is the shortfall, at its real size.
Where status colour replaces the accent. This drawing is about a degraded answer, so the gap carries --status-warn and orange stays out of the chart entirely. A diagram gets one emphasis, never two.