Revert "docs(arch): realism leads the quality list; performance moves to the end"

This reverts commit a1d52aa583.

Docs/Architecture/01_introduction_and_goals.md

@@ -20,14 +20,11 @@ Full requirements and progress are in [TODO.md](../../TODO.md); version directio
 
 | Priority | Quality Goal | Scenario |
 | --- | --- | --- |
-| 1 | **Visual realism** | Renders read as the reference photographs: façade identity, proportion, material and light — judged side by side, shot against photo |
-| 2 | **Geographic fidelity** | Building placement and street scale match the measured data and the photographs |
-| 3 | **Terrain walkability** | Zero raycast holes across both sidewalks and the carriageway (84-sample transect passes) |
+| 1 | **Performance efficiency** | 60 FPS at 2560×1440 on RTX 5070 Ti, documented preset, no frame generation |
+| 2 | **Terrain walkability** | Zero raycast holes across both sidewalks and the carriageway (84-sample transect passes) |
+| 3 | **Geographic fidelity** | Building placement, street scale, and façade identity match reference photography |
 | 4 | **Build reproducibility** | Fresh checkout + documented engine path produces a runnable Linux build |
 | 5 | **Provenance** | Every committed asset has recorded provenance |
-| 6 | **Performance efficiency** | 60 FPS at 2560×1440 on RTX 5070 Ti, documented preset, no frame generation |
-
-**How the order is used.** It decides trade-offs. When realism and performance disagree, realism wins and the cost is paid — but never by silently shipping a frame rate below the floor. The 60 FPS figure is a **budget that must still be met**, so the response to "realism costs too much frame time" is to cut the realism feature deliberately, record the cut, and keep the floor — not to let frames slip. Walkability outranks realism in one direction only: a beautiful block the player falls through is not a demo.
 
 ## Stakeholders