Esports information changes quickly. Players transfer, organizations rebrand, tournament pages are updated, and older records may remain online long after a newer source replaces them. NEXUS is designed around the principle that a useful directory should not simply collect data; it should preserve enough context to explain why a record is presented.
Treat public information as evidence, not automatic truth
A public page can be useful without being current. Team announcements, league pages, tournament brackets, social posts, and historical databases may describe different moments in time. Verification therefore starts by asking what a source actually proves and when that information applied.
When several sources disagree, the newest page is not automatically the best answer. A newer post may describe a temporary lineup, while an official competition roster may define who was actually registered for an event. The source has to be interpreted in the context of the record being shown.
Separate current records from historical records
Current rosters and historical rosters answer different questions. Replacing an old lineup with a new one without preserving context can make past matches difficult to understand. A directory should therefore avoid treating every record as though it describes the present day.
Dates, seasons, competitions, and organization identities provide the context needed to keep historical information useful. This is especially important when a player changes teams or when an organization changes name while older tournament records continue to use the previous identity.
Prefer explicit uncertainty over invented precision
Not every missing detail can be reconstructed reliably. When public information is incomplete, the responsible choice is to leave a field unconfirmed rather than manufacture a precise answer from weak evidence.
This principle matters for dates, roles, transfers, team identities, and older competition records. A directory becomes more trustworthy when users can distinguish known information from information that still needs review.
Corrections are part of maintaining a directory
A structured esports reference is never finished. New official sources appear, organizations publish corrections, and tournament operators revise their records. A maintainable directory needs a process for revisiting entries instead of assuming the first version will always remain correct.
NEXUS is intended to make those revisions understandable rather than hide the fact that data changes. The objective is not to claim perfect knowledge. It is to maintain useful records while being clear about evidence, dates, and corrections.