01 // Archive Summary
Priority Verified Record
Devil Hell is one of four specimens maintained as an active Priority Signal in the Meridian Archive. Portal Command has verified its identity, Devil lineage, power classification and repeatable encounter pattern. Current lineage record: Devil Hell → Devil Bat → Devil Hades.
02 // Signal Provenance
Priority Meridian Record
Devil Hell carries a stable resonance signature repeatedly identified by Portal Command. The signal is strong enough for active Archive observation and is consistently linked to the Devil lineage.
03 // Encounter Behavior
Verified Encounter Pattern
Repeated observation confirms a stable action sequence built around aerial movement, a close-range bite, a casting action, a projectile attack, and a return to flight. Guardian protocol continues to prioritize controlled stabilization and capture rather than destruction.
04 // Observed Ability Profile
Verified Encounter Sequence
Portal Command has verified a repeatable encounter sequence for Devil Hell. The recorded cycle is Flight → Bite → Cast → Projectile → Flight.
05 // Resonance Profile
Portal Command Index
06 // Portal Signature
Featured Meridian Signal
Devil Hell is one of the four active Featured Signals currently maintained by Portal Command. Its verified resonance and encounter record make this specimen a priority reference within the Meridian Archive.
07 // Evolution Lineage
Devil Family
The currently indexed Devil evolution line progresses through three recorded forms.
Devil Hell
Starter form // current dossier.
Devil Bat
Second recorded form // linked dossier.
#015 // STAGE IIIDevil Hades
Third recorded form // linked 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.