Source and Data Policy

Source and data policy

How MMB Guide collects, normalizes, conflicts, refreshes, and publishes Minecraft mod data.

DIRECT ANSWER

The data pipeline keeps raw evidence, normalized facts, decision rules, and page presentation separate. A page can only use facts that pass identity, current release, compatibility, source, and conflict gates.

Evidence checked July 18, 2026 · How verification works

Source priority

Maintainer project and release pages; official platform/runtime documentation; our recorded tests; then community reports as leads. Search snippets and competitor pages are discovery inputs, not authority.

Completeness

For a supported project we collect identity, current files, edition, game version, loader, environment, dependencies, license/redistribution state, installation requirements, known issues, and checked time. Unknown is permitted; omission disguised as certainty is not.

Staleness and conflicts

Failed refreshes retain the last valid snapshot and show staleness. Conflicting primary sources block a unique tool answer. Rejected claims are recorded so automated drafting does not reintroduce them.