Trust and corrections

Gakuran source policy: a report is not a verification.

The site is designed for a game whose public pages conflict. Every important claim needs a source, a checked date, and a visible confidence label.

Direct answer

This Gakuran source policy uses Official, Cross-Checked, Community Reported, Unverified, and Outdated labels. Claims without a checkable source stay draft or out of the index.

The labels used on this Gakuran wiki

The Gakuran source policy is the page to read when a report and an official page disagree.

Official means the claim appears on a Roblox, developer, publisher, or directly attributable official destination. The official Gakuran Roblox page is the current source for the game description and availability observation.

Cross-Checked means two reliable sources agree on a narrow claim, with dates recorded. Agreement does not override an official contradiction, and it does not turn a guide report into an in-game test.

Community Reported means a player or guide says something happened. This is useful for discovering tasks and deciding what to recheck. It is not a guarantee.

Unverified means a claim is plausible or repeated but could not be confirmed in the current check. Outdated means an older claim conflicts with a newer source or lacks a current date.

How Gakuran codes are handled

Current guide pages report six or five code entries depending on the publication date. This site lists the names and reported rewards, but it does not call them Working or Verified In-Game while the official Roblox page/API availability signals conflict. No vote counts, success percentages, or “tested today” badges are invented.

How gameplay pages are handled

Public pages discuss styles, height, controls, maps, combos, and rerolls. Those topics are real search tasks, but a search task is not evidence. A style tier list or build finder needs current mechanics, a readable source, or hands-on testing. Until then, the page stays draft or the homepage describes the evidence gap instead.

Correction path

When a source changes, the page gets a new checked date and a note explaining what changed. A player report can trigger a recheck. An official announcement or in-game test can promote a claim. Codex judgment is still required before a published page, schema, navigation link, or homepage module changes.

What this policy refuses to do

It refuses fake codes, copied screenshots, invented developers, private Discord claims, unsupported drop rates, fabricated map routes, and rankings that hide their test version. This approach may leave fewer pages live, but each live Gakuran answer has a clear reason to exist. The Gakuran source policy is the place to recheck that boundary. This Gakuran source policy remains the correction path.

Return to the Gakuran source policy before promoting a report to a published fact.