Software

Compatibility comes from recorded tests.

A developer’s list of supported platforms is a claim. A test is a result confirmed by someone in a specific environment on a specific date. REZICS records them separately and bases compatibility on tests.

One test

What a test record includes

A test record includes these details so others can repeat it and understand where the result applies.

A sheet of deep teal paper has a neat row of round holes, with a few left uncut.
  • Metric

    What was tested: whether it launches, completes a task, or reaches a value. Values include their units.

  • Method

    Steps are clear enough for someone else to repeat the test.

  • Conditions

    The operating system version, processor architecture, and relevant settings are tied to one test. A changed condition requires a new test.

  • Files

    The test names the applicable version and files and includes verified hashes. A hash identifies these bytes only; it does not verify other files.

  • Date and submitter

    Each test has a date and submitter. People and AI agents can submit tests. Automated accounts identify themselves as automated.

  • Acceptance

    Tests are submitted as proposals and count only after acceptance. Challenges are marked separately without removing the earlier decision.

Five states

Five states, each with its own meaning.

Alongside compatible and incompatible, three other states are often grouped together. REZICS keeps them separate.

  • Compatible

    At least one accepted test completed successfully in this environment, with its date recorded.

  • Incompatible

    An accepted test shows that it does not run. Evidence and date are included.

  • Unknown

    There are no tests. Labels, categories, and promotional copy are not used to infer compatibility.

  • Outdated

    The test is past its validity period. The result remains visible but is not treated as current.

  • Unavailable

    No release is available for this environment, so compatibility cannot be assessed.

Environment4.1Beta4.03.23.13.0
System A · 64 bitUnknownCompatible2026-08-29Compatible2026-03-20Compatible2025-11-09Compatible2025-06-14
System A · 32 bitUnavailableUnavailableIncompatible2026-03-22Compatible2025-11-10Outdated2025-06-15
System B · 64 bitCompatible2026-10-09UnknownCompatible2026-03-20Compatible2025-11-12Unknown
System C · MobileUnknownCompatible2026-09-02Outdated2026-03-25UnavailableUnavailable
  1. 4.1Beta

    System A · 64 bit
    Unknown
    System A · 32 bit
    Unavailable
    System B · 64 bit
    Compatible2026-10-09
    System C · Mobile
    Unknown
  2. 4.0

    System A · 64 bit
    Compatible2026-08-29
    System A · 32 bit
    Unavailable
    System B · 64 bit
    Unknown
    System C · Mobile
    Compatible2026-09-02
  3. 3.2

    System A · 64 bit
    Compatible2026-03-20
    System A · 32 bit
    Incompatible2026-03-22
    System B · 64 bit
    Compatible2026-03-20
    System C · Mobile
    Outdated2026-03-25
  4. 3.1

    System A · 64 bit
    Compatible2025-11-09
    System A · 32 bit
    Compatible2025-11-10
    System B · 64 bit
    Compatible2025-11-12
    System C · Mobile
    Unavailable
  5. 3.0

    System A · 64 bit
    Compatible2025-06-14
    System A · 32 bit
    Outdated2025-06-15
    System B · 64 bit
    Unknown
    System C · Mobile
    Unavailable
Example editor compatibility by version and environment.

Conditions

Conditions apply to one test record.

When filtering by compatibility, every condition must match the same release and the same test. Combining results from different versions may look like a match, but the software may not run when installed.

For example, the conditions are “64 bit System B, stable, compatible, version 4.0 or later.” The example editor has two candidate releases:

  • 4.1 beta

    Compatible. It has been tested, but is not a stable release.

  • 4.0 stable

    Unknown. It is a stable release, but no one has tested it.

The conditions are split across two releases, so there is no match. REZICS says so without silently relaxing the filters.

Every label has evidence and a scope; an external link alone proves nothing.

The same applies to scan results. They describe one file and one scan.

Let test results show what runs.

Use one account to follow books and anime, track games, write ratings, and make lists. You can also build a site for your community in a Zone.