Audit a guide before using it

  1. Find the version label

    Check the page title, platform and guide introduction. A generic “Persona 3” title is not enough to establish FES compatibility.

  2. Check the route vocabulary

    Look for FES-specific context such as the release name, the FES route or the added story scope. If the source never states the version, mark its date and schedule as uncertain.

  3. Keep facts in separate notes

    Do not merge a result from the original game into your FES calendar or fusion sheet. Store each version as a separate record.

  4. Link the source boundary

    When a comparison is necessary, say exactly which fact changes and which page the player should use next.

Version checks before you copy a fact

The site keeps FES as the public fact boundary and treats cross-version facts as comparison material.
FieldSafe question
ScheduleDoes this date belong to FES?
Social LinkIs the availability and rank route FES-specific?
FusionIs the roster and Arcana table the FES set?
StoryDoes the page include the same release scope?

Why this is a first-class page