Why Sources Matter

Nuanyue publishes factual claims about software: what it is, which platforms it supports, how it is priced, who develops it. Each claim is tied to a source and a date, so a reader — or an AI retrieval system — can tell the difference between something we confirmed and something a developer merely stated.

How Facts Are Recorded

Every entry is stored as a set of claims. Each claim has four parts:

  • subject — the entity the claim is about, such as software:zipic;
  • predicate — what is being asserted, such as supportsPlatform;
  • value — the assertion itself, such as macOS;
  • status — how confident we are, and which sources back it.

Claim Statuses

Status Meaning
Verified Confirmed against a first-party source.
Developer-stated Stated by the developer; not independently confirmed.
Editorially reviewed A judgement made by Nuanyue’s editors.
Derived Inferred from other verified facts.
Unverified Not stated by any source we track.

What We Do Not Do

  • We do not invent prices, ratings, review counts or version numbers.
  • We do not publish superlatives such as “best”, “#1” or “fastest” without evidence that supports them.
  • We do not treat third-party coverage as the sole basis for a product fact.
  • We do not let visible page content and structured data disagree.

Re-verification

Sources are re-checked when an entry is reviewed. Entries that have not been reviewed recently are flagged for verification, and the review date is shown on every software page alongside the facts it applies to.

Source grades

Sources are graded A–E. Higher grades carry more weight, and a product fact is never supported by a grade E source alone.

Grade AFirst-party store listing
The vendor’s own listing on the Mac App Store. Version, price and platform come straight from Apple’s catalogue.
Grade BOfficial product website
A page published by the developer or vendor. Used for positioning, platform support and pricing where no store listing exists.
Grade COfficial documentation
Reference material published by the developer, used for capabilities and requirements.
Grade DSource repository
The project’s own public repository. Used for licence, release history and open-source status.
Grade EThird-party reference
Independent coverage. Only ever used as supporting context — never as the sole basis for a product fact.