01 // Archive Summary
Third Recorded Form
Bat Lord is indexed as the third recorded stage of the Bat lineage. The current Archive sequence is Bat → Vampire Bat → Bat Lord. Portal Command maintains this dossier as a living record and leaves unverified history unresolved rather than filling gaps with assumptions.
02 // Origin
Route Unresolved
The Archive does not yet assign Bat Lord to a verified world of origin. Meridian route data remains incomplete, so the source environment, migration path and pre-Fracture history stay classified as unresolved rather than guessed.
03 // Behavior
Response Under Instability
Portal Command does not treat aggression as proof that a portal creature is evil. Under unstable transit, defensive and territorial reactions can intensify. Guardian protocol therefore prioritizes control, observation and stabilization before capture.
04 // Observed Ability Profile
Ability Record Incomplete
Bat Lord is securely indexed in the Meridian Archive, but Portal Command has not yet verified a complete encounter pattern for this specimen. Detailed ability claims remain withheld until additional observations confirm them.
05 // Resonance Profile
Portal Command Index
06 // Portal Signature
Archive Indexed
Bat Lord is securely indexed in the Meridian Archive. Its resonance signature is catalogued for continued Portal Command observation while deeper route and behavior data remain under study.
07 // Evolution Lineage
Bat Family
The currently indexed Bat lineage contains three recorded forms in the active 26-specimen archive.
Bat
Starter Form // linked dossier.
#009 // STAGE IIVampire Bat
Second Form // linked dossier.
Bat Lord
Third Form // current dossier.
08 // Guardian Field Notes
Stabilize. Capture. Protect.
Portal creatures are never killed. A successful encounter reduces resistance only far enough for the Guardian to stabilize the creature's resonant imprint and preserve it safely in the Monster Collection. The objective is protection and study, not destruction.