Biological / Databot
- Name
- Databot
- Taxonomic Class
- Elysian Historical Data Drone / Holographic Archive Carrier
- Homeworld
- Elysia / SkyTown
- Known Range
- SkyTown patrol lanes, Elysian archive routes, historical data nodes, and fixed projection areas keyed to Chozo-compatible visor access
- Diet / Power Source
- Internal machine power cell, local patrol routine, holographic archive projector, and access logic keyed to Chozo-based visor technology
- Threat Response
- Minimal direct hostility; information access, patrol interruption, data projection, and archive custody are the primary field concerns
- Origin / Development
- Manufactured by Elysians to preserve and transmit historical data through patrol-based holographic archive units
- Physiological Summary
- The Databot is an Elysian archive drone built to patrol set routes and project historical data when disrupted. Its information is not universally readable; the old record notes that Chozo-based visor technology is required to access the projected files.
Overview
The Databot is an Elysian archival drone built to record, preserve, and transmit historical information. The old source describes a machine that patrols a set area until disrupted, then projects a holographic datafile. Its purpose is documentary rather than defensive, and its value lies in the historical material it carries.
The access condition is central to the record. Only Chozo-based visor technology can read the projected information, which suggests that Elysian archive systems were designed with compatible optical or data protocols in mind. The Databot therefore sits at an intersection of Elysian memory culture and Chozo-derived scanning technology. A Databot separated from its route may still be intact, but it loses the spatial context that explains why its file was placed there.
Although listed in the Biological archive for legacy reasons, the Databot is best understood as an artificial archival organism within SkyTown's machine ecology. It moves, responds, and communicates, but it does not feed or reproduce. Its field importance comes from custody of historical data and the conditions under which that data becomes visible.
Anatomy And Physiology
The Databot's body consists of a compact machine casing, patrol locomotion systems, memory storage, projection hardware, and access-control logic. These components function like organs in an archival machine. Damage to the projector may leave the unit mobile but mute, while damage to memory storage may destroy the historical value of an otherwise intact body.
Its holographic projector is the defining structure. When interrupted, the unit produces a datafile rather than a conventional alarm or attack pattern. The projection likely depends on stabilized optics, internal file indexing, and a handshake with compatible visor systems. Without the proper scanner, the Databot may appear to display information that cannot be meaningfully read.
The unit's sensory systems appear tuned to local disturbance and route completion rather than broad awareness. It patrols until disrupted, which implies a limited but reliable perception loop. The machine does not need animal cognition; it needs route memory, interruption recognition, and enough autonomy to preserve data access across long periods.
Habitat And Range
Databots belong to SkyTown archive routes and Elysian historical spaces. Their range is determined by assigned patrol lanes, datafile relevance, and the architecture that supports holographic projection. A Databot found away from its route may indicate damage, reassignment, or disruption of the archive network that once maintained the patrol. The access requirement also means a silent projection can still be a successful archive event if the wrong reader is present.
Because the unit is an information carrier, its habitat includes readers as well as paths. Chozo-compatible visor access turns a local patrol into a readable historical node. Without that access layer, the same machine remains physically present but archivally silent, which makes user technology part of the environmental record. Preserving the machine without preserving its file content would leave the most important part of the specimen undocumented.
Field teams should preserve patrol endpoints, projection orientation, file content, casing damage, and the route's relationship to nearby Elysian structures. The surrounding site may explain why a specific record was assigned to a specific path. A Databot is rarely just a machine in a hallway; it is a curated fragment of SkyTown memory.
Behavior And Ecology
Databot behavior is simple but purposeful. It patrols along a set area, responds to interruption, and projects a holographic datafile. The action is not a social greeting or threat display; it is the machine's archive protocol, presenting stored history when a qualifying event occurs. Its behavior is therefore best evaluated by what information appears, where it appears, and which scanner can interpret it.
Within SkyTown's machine ecology, Databots function as mobile memory nodes. They preserve history in motion rather than only in fixed terminals, which may protect records against localized damage or make information available along important routes. Their patrols transform pathways into readable archive corridors. The unit turns patrol space into memory space, making movement part of Elysian archival design.
The requirement for Chozo-based visor access limits who can fully interact with the unit. This may have been intentional security, inherited compatibility, or a practical consequence of shared optical technologies. In any case, the Databot's behavior should be recorded together with the scanner used to read it, because access and message are inseparable.
Origin And Development
Databot development is manufacture by the Elysians, not biological reproduction. The unit was built as a means to record and pass on historical data, then assigned to a patrol area where that data could be accessed. Its origin is therefore cultural and technical as much as mechanical. A Databot separated from its route may still be intact, but it loses the spatial context that explains why its file was placed there.
The machine's development continues through archive assignment. A blank or unassigned unit would not have the same value as one carrying a historical datafile. Memory loading, route programming, projection calibration, and access authorization are all part of the Databot's functional maturation within SkyTown systems. The access requirement also means a silent projection can still be a successful archive event if the wrong reader is present.
Future records should preserve Databots intact whenever possible. Destroying the casing may destroy the archive, and even a damaged unit can reveal Elysian priorities through route choice and file content. The central question is how many historical records were distributed through mobile drones rather than fixed archives before SkyTown's decline.