Biological / Shriekbat, Elysian
- Name
- Shriekbat, Elysian
- Taxonomic Class
- Elysian Mimetic Dive Drone / Shriekbat-Pattern Volatile Construct
- Homeworld
- Elysia
- Known Range
- Elysia hovering facilities, exposed platforms, old aerial routes, small flock patrol spaces, and abandoned exterior structures
- Power Source
- Internal machine power, proximity logic, mimetic flock behavior, detonation charge, and long-duration facility patrol routines
- Threat Response
- Shriekbat-pattern dive-bombing, contact detonation, flock movement, proximity response, and machine persistence in aerial facilities
- Origin / Development
- Ancient Elysian machine manufacture; purpose unknown, with current behavior preserving shriekbat mimicry and patrol logic
- Physiological Summary
- The Shriekbat, Elysian is not a living shriekbat but a machine built to mimic one. It patrols Elysia's hovering facilities in small flocks, diving toward nearby bodies and detonating on contact in the manner of the biological model. Its origin remains uncertain, but the design preserves a deliberate act of biomimicry within old Elysian infrastructure.

Overview
The Shriekbat, Elysian is an artificial organism in the archive sense: a machine built to behave like a small volatile animal. The old record states plainly that these are not living shriekbats, even though their dive-bombing and contact detonation closely mimic the biological pattern. That distinction keeps the entry grounded in infrastructure rather than zoology.
Their original purpose remains uncertain, which makes the mimicry especially important. A designer chose a shriekbat-like body and behavior for an aerial machine in Elysia's floating facilities. The design may have been defensive, deterrent, experimental, or symbolic, but the surviving record shows a construct whose function depends on being read as animal-like before it detonates.
The units often move in small flocks. Flocking gives the machine hazard value beyond a single dive because multiple small bodies can occupy approach lanes, clutter external platforms, and make old facility routes feel biologically active. Their presence is therefore part of Elysian site ecology, even though the bodies themselves are manufactured.
Anatomy And Physiology
The chassis appears built around compact flight, proximity sensing, and a contact charge. A biological shriekbat can use muscle, instinct, and self-preserving flight, but the Elysian machine has no need to survive after impact. Its body can therefore be optimized for approach, target confirmation, and controlled rupture rather than feeding or recovery.
Mimetic features likely include wing-like stabilizers, bat-like silhouette, and flock spacing behavior. These traits may not be mechanically necessary in strict engineering terms, which suggests the shape was chosen for behavioral resemblance. The machine imitates an ecological warning pattern: small body, sudden descent, and immediate consequence for crossing a threshold.
The detonation system should be studied as part of the anatomy, not simply as a weapon. Charge placement, casing fragmentation, and sensor position reveal how the unit converts flight into impact. A clean record should preserve damaged casing, signal residue, and nearby scorch distribution together, because the explosion is the final expression of the body plan.
Habitat And Range
Shriekbat, Elysians inhabit old hovering facilities and exposed aerial structures on Elysia. These sites provide open descent space, ceiling or underside perches, and approach lanes where small flying constructs can remain unnoticed until a target moves too close. Their range follows architecture rather than natural nesting requirements. This makes vertical placement and approach geometry essential evidence, not background scenery around the machine.
Small flocks are most meaningful near platforms, suspended corridors, and exterior maintenance routes. A lone unit may be a residual hazard, but a cluster suggests an active patrol logic or a designed deterrent zone. Facility surveys should map perch points, dive angles, and detonation scars across the same vertical space.
Because their purpose is unknown, habitat context is the strongest evidence. Units found near sensitive machinery may indicate defense, while units clustered around transit routes may indicate crowd control or old access denial. Their persistence also suggests durable power management, dormant wake states, or low-energy patrol cycles suited to long-abandoned structures.
Behavior And Ecology
The machine's behavior is simple but effective. It waits or patrols in aerial space, detects a nearby body, dives directly, and detonates on contact. The pattern resembles shriekbat defense or panic behavior, but in the construct it is a programmed terminal action rather than a living stress response. That simplicity is precisely why the units remain dangerous after long abandonment and partial system decay.
Flock behavior changes the risk profile. One unit diving can draw attention while others remain above or behind, and multiple proximity responses can make a narrow platform dangerous even when each individual body is fragile. The group therefore functions like a distributed trap disguised as wildlife movement. That simplicity is precisely why the units remain dangerous after long abandonment and partial system decay.
Ecologically, Shriekbat, Elysians blur the boundary between animal sign and machine hazard. Other organisms may avoid their patrol spaces as if avoiding living shriekbats, while survey teams must treat them as evidence of ancient design. Their behavior preserves a manufactured imitation of predation without hunger, reproduction, or ordinary survival pressure.
Origin And Development
The Shriekbat, Elysian has no biological reproduction. Its origin is machine manufacture, apparently centuries old, by an unknown Elysian or Elysia-associated engineering authority. The surviving bodies preserve a deliberate design decision to imitate a living dive-bombing animal within built aerial space. Manufacturing traces, charge chemistry, and flock-signal hardware should be preserved together to reconstruct that design history.
Development after manufacture would involve charge installation, flight calibration, proximity logic, flock coordination, and facility assignment. Long survival implies either durable internal power, docking access, or a dormant mode that allows units to remain present long after their builders stopped supervising the system. Manufacturing traces, charge chemistry, and flock-signal hardware should be preserved together to reconstruct that design history.
Future records should compare inactive units, detonated fragments, and perch-site residue. The central question is whether these machines were built as defense, maintenance deterrents, behavioral experiments, or symbolic guardians. Until that is resolved, the archive should preserve both the mechanical evidence and the mimetic pattern that defines the unit. Manufacturing traces, charge chemistry, and flock-signal hardware should be preserved together to reconstruct that design history.