Methodology

How a fan reference for a fictional character gets built — and what it refuses to claim.

The starting point

This site is a fan reference for a fictional character: Aeron Skyrift, a StarTeam original from the Vizlings app whose entire official description is the card text “Space Hero Military.” There is no novel, no film, no historical record to research. The method, therefore, is not research but world-building under constraints — and the constraints are stated plainly here.

The rules the lore was written under

1. Fiction is labeled as fiction, everywhere. Every content page carries a fiction note. The Sayings page labels its lines as fictional character dialogue and explicitly states they are not real quotations. The footer of every page states the character is fictional. Nothing on this site may be mistaken for a claim about a real person.
2. The card is canon; the rest is fanon. The only official facts are the name, the StarTeam category, and the “Space Hero Military” description. Everything else is invented for this site and could be contradicted by future official material — which would then take precedence.
3. Internal consistency is the quality bar. With no canon to check against, the standard is whether the lore contradicts itself: ranks progress in order, dates sequence correctly, the same ship has the same name on every page, and the character’s voice stays steady.
4. The archetype is the brief. “Space Hero Military” plus the tactician role determined the design: strategy over brawling, fleet operations, rank structure, logistics as a superpower. Every lore choice serves that archetype.
5. No real people, no real history. Names, battles, and worlds are invented. Any resemblance to real military figures or events is coincidental and unintended.

Image policy

Uncertainty policy

Where the fan lore is deliberately vague — the Maw’s origins, what drove them from the dark, Aeron’s life after the Veyra Evacuation — the site says so rather than inventing answers for completeness’ sake. Gaps are part of the design; a reference that fills every gap with invention stops being a reference and starts being a novel.

What this site is for

Fans of the character, fan-fiction writers who want a consistent continuity to write in, and anyone curious what a “complete reference” looks like for an original app character. It is a love letter with footnotes — the footnotes just happen to point at itself.

Consistency checking

The lore bible is checked the way editors check continuity: every page’s claims were cross-read against the bible before publication. Ranks progress in order (Ensign 1190 through Fleet Admiral 1211), dates sequence correctly, the flagship keeps one name, the team keeps eight members, and the character’s voice stays steady from Lore to Sayings. Where a page needed a fact the bible didn’t have — a ship name, a minor character — the fact was added to the bible first, then used. The bible is the single source of truth; the pages are its expressions.

The result is a reference you can argue with but not catch contradicting itself — which is the highest compliment a fan-built continuity can earn.

Source notes

This methodology governs a fan reference for a fictional character from the Vizlings app. The site’s source basis is documented in Sources.