// Methodology
How reports are produced.
GameSpecLab turns retrieved evidence into reviewed, static hardware-class reports. The public site does not run live model calls for visitors.
1. Retrieve evidence
The local CLI gathers official requirements, benchmark coverage, patch notes, and other relevant source pages. Search fixtures are used during prompt and model testing to avoid repeated API calls.
2. Draft structured guidance
OpenRouter returns a structured draft with source-stated CPU and GPU classes, expected ranges, caveats, confidence, and citations limited to retrieved URLs.
3. Modernize hardware classes
A deterministic dated hardware ladder maps older source-stated GPU classes to modern equivalent classes. The model does not decide what counts as modern.
4. Ground and review
Citation grounding drops unsupported URLs and unsupported tiers. A human review step labels the report status, checks caveats, and commits only public-safe report files.