Trust model

How SFE DB handles evidence

A published name does not make every value verified. Every public claim carries its own source level, review, freshness, unit, context, and limitation.

Official facts

Identity and high-level mechanics read directly from a first-party game page or API. An official description without numbers cannot prove individual rates.

Gameplay observations

A retained capture can prove what its UI showed in that session. It does not automatically prove a universal base value or probability.

Community reports

A correct-game secondary page may supply a provisional name, visible label, zone, or reported mapping after review. It is displayed as a community report and remains replaceable; it cannot supply calculator presets, odds, income, multipliers, timers, schedules, codes, or asset rights without stronger evidence.

Player inputs and tests

Your values calculate only your scenario and are not uploaded. Fictional fixtures are isolated under tests and must never enter public JSON, pages, search, or sitemap.

Calculator eligibility

A preset needs approved, current evidence with a clear unit and precision. Secondary-only claims are excluded. Derived values need a complete, acyclic dependency chain, and the recorded context must match the player's selection.

See the current gates or prepare a local evidence record.