01At a glance
- Content
- Methodology; rating changes cite builds
- Rule
- No silent promotions or drops
- Evidence
- Build + firmware + driver per run
- Use
- Audit any rating from here
02What lives here
Compatibility methodology is the normative procedure: rig, warm-up, session scope, and promotion thresholds. Every Compat rating traces to a run performed under it.
Read the methodology before disputing a rating. Disputes without build number, firmware version, and driver version are unactionable by construction.
Free build: Download Meridian. Own your library; method applies equally to all 400+ indexed titles.
03How to read rating changes
- Each change names the build that caused it. Compare runs only within a build.
- Drops indicate confirmed regressions, not opinion shifts.
- Promotions require repeated clean runs — never a single good session.
04Questions
Q.01Where is the changelog?
Build notes ship with the launcher. This shelf holds the method that makes those notes meaningful.
Q.02How do I dispute a rating?
Reproduce under the published methodology, then report build, firmware, driver, and warmed-cache runs.
Q.03Why publish the method at all?
So ratings are auditable. A rating without a method is marketing; Meridian publishes the method.