PAPERGAMES DISCOVERY TERMINAL THE PAPERTRADE GAMES DIRECTORYPAPERTRADE ECOSYSTEM ↗
papergames_Games. Trading. Discoveries.
GUIDE 02 / 4 MIN READ

Read a project profile.

Understand availability, sources, verification labels and the dates behind a listing.

PAPERGAMES GUIDE · UPDATED
01 /

Start with the project’s actual access

The group and subcategory tell you how the project is classified. The overview explains what it does; access requirements describe known restrictions. Read the longer overview with Read more, then check the original source.

An accessible terminal does not, by itself, establish that an order, withdrawal or reward has been tested. An announcement and an available Papertrade integration are different claims. The Listing Policy sets out the evidence expected for a profile.

02 /

Ask what each label actually covers

Source Checked
A stated claim was compared with a public source. Read the named reviewer, date, scope and evidence.
Playtested
A named tester accessed the stated build and tested the described scope. It does not establish everything about the project.
Audit Report
A public technical report is documented for a stated scope or version. Read the report, including its findings and limitations.

If no documented verification label is shown, the profile is not presenting one. A source link, a rating or a Live status does not substitute for a documented check. None of these labels guarantees safety or financial outcomes.

03 /

Separate a fresh edit from a fresh check

READING EXAMPLE / TWO DATES, TWO QUESTIONS
Last Documented Check
When was a specific claim or build checked?
Publication Updated
When did the published profile change?

These labels explain how to read a profile. This example does not document a project verification.

A corrected description or new image can update the publication date without creating a new check. Audit report dates remain separate. A private draft save does not update the public publication date. When a check or date is unavailable, treat it as unknown.

04 /

Keep opinions and evidence separate

Editorial score is the team’s assessment when one has been recorded. An unrated profile is not a zero. Community ratings and reviews reflect member opinions. Profile views and upvotes measure participation, not verified performance.

Read the review text and its context. A member’s first impression is different from a report of something they personally tried. Rankings, scores and popularity do not establish a project’s security or execution quality.

05 /

Go back to the source — and help correct the record

Use the evidence and original-announcement links to check the claim in context. Project Updates & Events describes published developments; an entry saying a profile was added to PaperGames does not necessarily announce the project’s launch.

If something is wrong, select Suggest a Correction on that profile. Describe the exact issue and add a public source or reproducible explanation. Track your submission in My Corrections. A correction improves an existing record; it does not need a duplicate project proposal.

Sources & further reading

Original sources for the platform, and PaperGames policies for the way this site works.