Characters and familiars: what is actually known

The public premise identifies the player as the Recursor and introduces a mysterious familiar named Chu. That is enough to explain the story relationship, but not enough to publish a complete character database.

Names, roles, skills, progression, balance, and team recommendations should be treated as unverified until they are supported by an official roster or repeatable public-build evidence.

A useful roster page needs more than a list of names. Each future entry should identify where the information came from, which build it describes, and whether the detail is still present in the current public version.

• Character or familiar name and the source where it first appears.
• Story role or relationship only when the source states it clearly.
• Combat abilities and progression data only after they can be checked against a build.
• No tier rankings, pull advice, or team meta until the underlying roster is stable.

A tier list would imply a stable, comparable set of characters and a known combat environment. Neither is established by the current public record, so publishing one now would create false confidence rather than help players.