</ Re_Bug>

A bug is an error in the system, funnily enough the term comes from the fact that insects used to fly into calculating machines because of the heat and thus paralyze them. My project is a reversal of this, but the error is now in a different place. Re_BUG001.50 is a fully automated apparatus as a measure of the state-ordered “restoration and preparation of the balance of our ecosystems” (W,A,Ö). It is based on the regulations of paragraph 14;7-13 and is standardized according to DIN EN ISO 95433 1. It is compatible for use in server cabinets by inserting it into the racks like previous devices. Re_BUG001.50 is used for rearing the eggs of dying and extinct insect species. These are taken from the wild by people with expertise and embedded with species-specific food and water. The constantly produced thermal energy of the servers is used to breed the insects, ensuring optimal conditions for the animals. Data is collected by various types of sensors and forwarded to the central control center to ensure the well-being of the animals. However, this collected data is also an elementary component for the servers. The computers can use it to generate random numbers in order to encrypt their own data more securely. 

What appears to be a symbiosis is not really one. Rather, this scenario involves the seemingly never-ending human search for a technical solution to existing problems. Instead of responding to the needs of insects and protecting them, they become entangled in a system from which humans ultimately get the most. During my research, I was lucky enough to gain insights into the issues from various experts: Prof Dr Christoph Karg, into his research on applied crypto-graphy, through Stefan Schlunk a contact to the ITZ, the computer center of the MLU Halle and from Dr Roel van Klink information on insect monitoring and insect breeding. With the information gathered, it would be possible for me to implement a prototype of such a fully automated breeding box for insects. But since this is a dystopia, a realistic implementation would have made it a reality. So I decided to turn my design into a communicator of the scenario. The result is an abstracted 1:1 model of the situation of the breeding box in the server and an unreadable blueprint of the non-abstracted breeding machine.