AI policy
Where automation is allowed in the PhonePlayers workflow, where it is not, and who is accountable for every published page.
Last reviewed
Automation is a tool in this workflow, and pretending otherwise would be its own kind of dishonesty. What matters is where it is allowed to operate and where a person has to stand behind the result.
What automation may assist with
- Organising research and gathering primary sources for a person to read.
- Transcription.
- Formatting, structuring and copy-editing.
- Comparing datasets and spotting inconsistencies for a person to check.
- Preparing drafts that a person then verifies, rewrites and takes responsibility for.
- Quality checks — broken links, missing alt text, stale dates, schema violations.
What automation cannot do here
- Verify a code. A code is verified by a person redeeming it. There is no other route to the word.
- Establish a gameplay fact. If it is not in a primary source or something a person here observed, it is not published.
- Confirm device compatibility or performance. That requires the device.
- Manufacture firsthand experience. A review requires a person who played the game.
- Decide a tier placement without a person able to explain it.
Accountability
A person is accountable for every page on this site. Where an article is published under the editorial team byline, that means a named editor within the team; where it depends on firsthand play, it carries an individual byline. There is no circumstance in which a page appears here that no person has read.