The missing requirement that was not missing
In the collected Hades specification, the operating-system label is written as "OS *". In the Counter-Strike 2 specification, it is "OS". A literal comparison of the labels placed them on different rows and made each game appear to lack the other field. The source values were present; the comparison was wrong.
We now match the semantic field and keep the original publisher values. In this example, Windows 7 SP1 and Windows 10 appear on one operating-system row. The marker is still retained in the underlying source-labelled record. Removing a display mismatch must not become permission to rewrite the requirement itself.
Unknown means unknown, not copied from the neighbouring column
Counter-Strike 2 does not provide a recommended specification in the collected record. The workbench reports that absence. It does not copy the minimum into the recommended column or invent a higher processor and call that the recommendation.
The same rule applies when comparing a processor name, memory amount or graphics requirement. A missing field is not a zero requirement. An older API response, an unusual publisher label or unstructured prose may explain the absence. The right next step is to inspect the current publisher listing, rather than treat the empty cell as evidence that the hardware is unnecessary.
A model name is not a benchmark result
Minimum and recommended requirements describe targets selected by a publisher. Unless the publisher states the resolution, settings and performance target, the labels do not supply those details on their own. Comparing a GPU name with another GPU name cannot establish a frame rate for the reader’s computer.
Our tool therefore does not generate green "will run at 60 FPS" badges from model-name matching. Processor generations, memory configuration, graphics power limits, drivers and the game version can all matter. None has been measured merely because a database contains a model string. We have not benchmarked the listed games on the reader’s hardware.
Use the workbench to identify the next verification
Start with the correct game edition and the current source listing. Compare operating-system support, installed memory, graphics requirements, storage and any explicit API requirement. If a field is unclear, record the exact publisher wording and verify that specific point.
If you need a performance conclusion, seek a benchmark whose hardware, settings and game version match the question. Keep that benchmark distinct from this specification comparison. The value of a transparent table is that it helps identify the unknowns; it should not conceal them behind a simplified score.
Sources and verification notes
Steam store — verify the current regional price and edition
Source attribution is not independent gameplay verification. Original reporting is credited to its publisher.