Methodology

Stated plainly: this is a fan reference for a fictional character. Here's how it's built and what the rules are.

What this site is

This is a fan-made reference for a fictional character — Niko Raal, an original sci-fi hero from the Vizlings character concept (“star blue male”). It is not an encyclopedia of a real person. It is not journalism. It is an act of imaginative fandom: taking a one-line character description and building a consistent, detailed fictional world around it, the way fans have always done.

The honesty rules

Because fiction presented carelessly can mislead, this site follows five rules on every page:

1. Fiction is labeled as fiction. Every page carries a note stating that Niko Raal is a fictional character and the lore is invented. No page presents lore as history or biography of a real person.
2. Dialogue is labeled as dialogue. The sayings page and all quoted lines are marked fictional character dialogue — never presented as real quotes from real people.
3. Art is labeled as art. Every image is captioned “AI-generated dramatization art.” No image is presented as a photograph, and no real person’s likeness is depicted anywhere.
4. Dates are in-fiction. The timeline uses the invented Halcyon cycle calendar. “Cycle 447” is a story date, not a claim about the real world.
5. Gaps are admitted. Where the owner hasn’t supplied material — the app bio, the real character art, the live stream — the site says so plainly instead of inventing a cover story. Placeholders are labeled as placeholders.

How the lore was built

• Seed: the Vizlings character card — name “Niko Raal,” category “StarTeam,” description “star blue male.” Everything else is invention.
• Design brief: give Niko a distinct persona among StarTeam heroes — the quiet cryo/ice specialist, defined by patience, precision, and restraint, in deliberate contrast to louder archetypes.
• Consistency pass: names, dates, places, and abilities were cross-checked across all pages so the fiction holds together — the same crew, the same ship, the same rules for the frostcell gift.
• Uncertainty policy: where the fiction is deliberately vague (the Ashen Signal, Kade’s plans), the site says the story is ongoing rather than inventing false certainty. Fan references should leave room for the canon to grow.

How consistency is maintained

Fiction this detailed only works if it holds together. The build used a simple continuity system:

• The rulebook: the frostcell gift’s mechanics (moving heat, forty-meter sightline range, venting as aurora-light, the emotion link, thawshock) were fixed before any story was written, and every page obeys them.
• The bible: names, dates, places, and relationships were tracked in a single continuity pass — the same crew, the same ship, the same Halcyon cycle dates on every page.
• The voice check: Niko’s dialogue was written against a fixed voice profile (dry, precise, quiet, warm underneath) so twelve different “sayings” still sound like one person.
• The honesty sweep: every page was re-read for the five rules above — fiction labeled, dialogue labeled, art labeled, dates in-fiction, gaps admitted.

What would change this

If the character’s owner supplies official art, bio, or canon lore, this reference will be updated to reflect it — and any invented lore that conflicts will be revised or retired, with the change noted. Fan fiction serves the character; it doesn’t compete with the owner.

Source notes

This methodology governs a fictional fan reference. For the materials it governs, see sources.