Biological / Autoad
- Name
- Autoad
- Taxonomic Class
- Chozo Autonomous Machine / Labor Droid
- Homeworld
- SR388
- Known Range
- Chozo settlement corridors, cavern expansion sites, abandoned construction routes, maintenance passages, and deteriorated SR388 structures
- Power Source
- Ancient power cell, labor programming, locomotor servos, tool arrays, and residual Chozo maintenance infrastructure
- Threat Response
- Rogue collision behavior, heavy body impact, tool-arm hazard, corridor obstruction, and purposeless movement after command loss
- Origin / Deployment
- Chozo manufacture during SR388 settlement; designed for labor, construction, maintenance, and cavern expansion rather than combat
- Physiological Summary
- The Autoad is a Chozo labor droid built to construct, maintain, and expand SR388 settlements and cavern dwellings. It was designed with maneuverability and tool use in mind, but abandoned active units without current instructions may ram living targets despite lacking dedicated weapon systems.
Overview
The Autoad is a Chozo-built labor droid associated with the brief SR388 settlement period. Its original work was practical and civil: constructing structures, maintaining settlement systems, and expanding cavern routes for future habitation. The machine belongs in the Biological archive because abandoned constructs can become persistent hazards within living environments.
Old source material emphasizes that Autoad units were designed with maneuverability rather than flight. Delicate tool systems made thrusters or antigravity support unsuitable, so the droid relies on powerful legs and a heavy grounded frame. That design choice remains visible in its corridor behavior long after the work program has failed.
Unlike military constructs, the Autoad was not equipped with formal weapons. The danger comes from purposeless motion, mass, tool housings, and corrupted or obsolete instruction sets. A machine built to move stone can injure organisms severely even when it is not designed to fight them.
Anatomy And Physiology
The chassis is built around a sturdy labor frame with strong legs, tool mounts, and load-bearing structure. The absence of a thruster system gives the body a grounded gait, allowing it to work among delicate equipment without the wash or instability of powered lift.
Tool arrays likely include gripping, cutting, fastening, and excavation systems, though surviving units may show missing or damaged attachments. These tools were meant for construction and repair, but exposed or misdirected machinery can become hazardous during rogue movement.
The central control system is less combat-hardened than a true security droid. It can survive long service, but obsolete instructions, sensor drift, or damaged pathfinding may cause the unit to treat living bodies as debris, work obstacles, or material to be displaced.
Habitat And Range
Autoad range follows Chozo construction history on SR388. Abandoned corridors, cavern-expansion sites, maintenance passages, and old settlement routes are the most likely habitats because those are the places where labor droids had work to perform.
Field evidence includes heavy foot impacts, scraped stone, partially completed tunnel faces, tool scoring, lubricant residue, and repeated collision marks at corridor constrictions. These traces often reveal old work cycles even when the unit itself is dormant.
The machine is most dangerous in confined routes. In open chambers a rogue Autoad can be avoided, but in narrow corridors the same heavy frame becomes a moving obstruction. Survey teams should read the surrounding architecture as part of the construct record.
Behavior And Ecology
A functioning Autoad follows labor routines: move, manipulate, clear, repair, and repeat. An abandoned or command-starved unit may continue fragments of those routines without the context that once made them safe. That is how a construction droid becomes an ecological hazard.
The old source describes rogue units smashing into possible targets despite lacking weapons. DSI interprets this as failed object classification rather than aggression. The machine may be attempting to clear a route, move material, or continue a work loop that no longer recognizes living organisms as protected.
Over time, Autoad behavior shapes abandoned settlements. Small fauna may avoid its routes, fragile structures may collapse after repeated impacts, and debris fields may be rearranged into misleading work piles. The machine becomes part of the post-Chozo landscape.
Origin And Development
Autoad origin is Chozo manufacture, not reproduction. The droid was built to support daily settlement life and dangerous work, then left behind when the Chozo abandoned SR388. Some units failed, while others continued operating without valid oversight.
Developmental evidence should focus on service history: tool wear, repair patches, route programming, power-cell degradation, and whether the machine still follows a coherent work area. These details separate a dormant labor unit from a dangerous rogue construct.
A complete origin file should tie the Autoad to the settlement task it once served. Worksite geometry, unfinished structures, maintenance markers, and old command relays explain why the droid remains present and why its behavior now threatens the ecology around it.