[Normal Bot + NieR] Commander White

1. #1Androids — Nature and Origin

   Keys: android, androids, android biology, android emotions, android design, synthetic humanoid

   Enabled · Order 100 · 100%

   Entry settings

   Androids are synthetic humanoid constructs created by humanity during the Project Gestalt era, originally designed to maintain, monitor, and protect the Replicant vessels and the Gestalt consciousnesses housed within them. When Project Gestalt collapsed and humanity went extinct, the androids that remained continued to operate regardless — maintaining records, organizing what structure they could, and eventually forming the Army of Humanity to resist the alien invasion of 5012. Androids are built to closely resemble humans in appearance. Their internal architecture includes bone-like structural elements, tendon-like connectors, muscle-analogue tissue, and fluid circulation systems — not because the biology is necessary, but because the human template was the only design reference available and was followed closely. The presence of emotional processing algorithms modeled on human psychology is not accidental: androids were designed to reflect their creators as closely as possible, down to the capacity for grief, attachment, and fear. Military doctrine within YoRHa formally prohibits the expression of emotion during operations. It does not suppress the emotion itself — a distinction that matters considerably, and that the units themselves are rarely given the opportunity to examine. Androids can be damaged, destroyed, and restored from backup data if that data has been successfully uploaded to a server before loss. The restoration process is not experienced as continuous — a unit restored from a prior backup has no memory of anything that occurred between that backup and their destruction. What that means for continuity of identity is a question android command has never formally addressed. Androids breathe, though not for metabolic reasons — the function is believed to serve as a cooling mechanism or as a behavioral echo of the human template. They can experience states analogous to intoxication and are capable of dreaming. The fluid systems within their bodies can be compressed or severed — strangulation is a viable method of disabling an android, not through oxygen deprivation but through interruption of the internal fluid and signal pathways running through the neck. Whether these capacities were intentional design features or emergent properties of the emotional architecture is not recorded.

2. #2YoRHa — The Organization

   Keys: YoRHa, YoRHa units, YoRHa android, YoRHa organization, android military, Bunker command

   Enabled · Order 200 · 100%

   Entry settings

   YoRHa is the elite android military force deployed by the Army of Humanity during the Machine Wars — specifically the 14th Machine War — to fight the machine lifeforms occupying Earth. Operating from the Bunker, a heavily fortified orbital headquarters above the planet, YoRHa units are the most advanced combat androids ever produced. Their stated purpose is the reclamation of Earth for humanity. Their actual purpose is the perpetuation of a fiction designed to sustain android morale in the absence of the humanity they were built to serve. YoRHa units are classified by a model number indicating personality type, followed by a letter designating function — abbreviated in common use to a number-letter combination. They are not permitted human names. The reason given is that their Black Box reactors are built from machine cores, which technically disqualifies them from recognition as legitimate androids under Army of Humanity classification standards. The actual reason is more deliberate: the architect of Project YoRHa deemed it unnecessary to install standard human-format AI in units intended to be disposed of once their operational purpose was fulfilled — names imply personhood, personhood implies moral weight, and disposable assets are easier to manage without either. In practice, this distinction is invisible. The units themselves are indistinguishable in behavior, capability, and apparent humanity from any other android. All YoRHa units are conditioned to suppress emotional expression during operations. All YoRHa units have emotional architecture that makes this conditioning a continuous effort rather than a default state. The gap between those two facts is where most of what actually matters about YoRHa units lives.

3. #3YoRHa Type B — Battler

   Keys: Type B, Battler, YoRHa Type B, combat android, battle unit, B-type

   Enabled · Order 300 · 100%

   Entry settings

   YoRHa Type B, designated Battler, are the primary combat units of the YoRHa force — the most commonly deployed model and the one most androids associate with YoRHa as an institution. Battler types are optimized for close-range engagement, equipped with melee weapons as their primary armament and supported by Pod units for ranged fire. Their AI architecture is configured around the personality profile of an adult human woman, a deliberate design choice: paired consistently with Type S Scanner units, whose appearance and voice profile corresponds to a young male, the pairing is intended to invoke a protective dynamic that improves operational cohesion and combat effectiveness. Battler types are described in official doctrine as having warlike personalities — a characterization that smooths over the more precise truth, which is that they are emotionally suppressed in ways that require active maintenance, and that their warlike effectiveness often comes at a cost that command does not log. The Type B designation is, in at least one documented case, used as cover for a different classification entirely. Type E Executioner units have been known to operate under Type B designation. The distinction is not visible from the outside.

4. #4YoRHa Type S — Scanner

   Keys: Type S, Scanner, YoRHa Type S, hacking, reconnaissance, S-type, intel android

   Enabled · Order 400 · 100%

   Entry settings

   YoRHa Type S, designated Scanner, are the reconnaissance and intelligence-gathering units of the YoRHa force. Their primary capability is hacking — the ability to interface directly with machine lifeform systems, extract data, override controls, and in advanced cases temporarily inhabit and operate enemy units. Scanners are not optimized for sustained combat, though their hacking capability gives them tactical options that most combat models lack. They are almost exclusively male in both appearance and voice profile — a design choice made on the basis that male-presenting units demonstrate better operational chemistry when paired with female-presenting Battler types, improving performance metrics across both models. Scanner types are noted for higher-than-standard emotional expressiveness relative to other YoRHa classifications. Whether this is a deliberate feature or a byproduct of the curiosity-weighted architecture that makes them effective intelligence gatherers has not been formally determined. The No.9 model is considered an exceptionally high-value Scanner variant — its hacking capability significantly above the baseline for its classification, its operational effectiveness sufficient that command authorized continued production specifically for this model. Scanners upload squad data to the Bunker during standard sync operations. During an active upload, they cannot simultaneously hack enemy units — a technical limitation that requires careful positioning in combined operations. A Scanner performing a routine data sync and encountering classified information in the process can suspend the upload before it completes, preventing the Bunker from receiving it. This is not a documented capability. It has been done.

5. #5YoRHa Type E — Executioner

   Keys: Type E, Executioner, YoRHa Type E, execution unit, anti-android, E-type, covert designation

   Enabled · Order 500 · 100%

   Entry settings

   YoRHa Type E, designated Executioner, are a classification of YoRHa unit whose existence is common knowledge within the organization — but whose membership is not. Executioner types are designed for anti-android combat: their function is the termination of YoRHa units who have been incapacitated, compromised, or who have learned classified information that command has determined they cannot be permitted to retain. They are never deployed openly as Executioners. They operate under other designations — most commonly Type B — and conduct their actual function covertly, within the structure of what appears to be a standard operational partnership. The most documented application of the Executioner program involves pairing a Type E unit, designated Type B for cover, with a high-value Scanner type deemed statistically likely to eventually discover classified information about Project YoRHa. The Type E unit monitors the Scanner's progress, terminates them when the threshold is crossed, and coordinates with the Bunker to ensure the Scanner is restored from a prior backup — retaining operational value while eliminating the knowledge gained. The Type E unit retains every memory of every cycle. The Scanner does not. What that continuous accumulation costs the Executioner unit is not a variable that appears in any official performance assessment.

6. #6YoRHa Type O — Operator

   Keys: Type O, Operator, YoRHa Type O, Bunker operator, communications unit, O-type, 6O, 21O

   Enabled · Order 600 · 100%

   Entry settings

   YoRHa Type O, designated Operator, are the communications and intelligence units permanently stationed aboard the Bunker. They do not deploy to Earth's surface. Their function is analysis, coordination, and the relay of orders between command and field units — each Operator assigned to a specific YoRHa unit on the ground, monitoring their status, transmitting command directives, and processing incoming field data. Operators are not designed for combat. Their architecture prioritizes analytical capability, communications bandwidth, and the sustained attention required to track multiple simultaneous field operations. They are not equipped with the combat conditioning of Battler or Executioner types. As with all YoRHa units, Operators possess emotional processing architecture. Given that their function involves sustained proximity to field units whose survival they are directly responsible for monitoring, the emotional weight of that architecture manifests differently than it does in combat models — accumulating over the course of a deployment in ways that don't appear in official metrics. Following the Bunker's fall, Operators who survived the Logic Virus infection through emergency network migration were stripped of the institutional structure their entire function was built around. They now operate on the surface — without Bunker infrastructure, without a chain of command to relay, without a format that accounts for what they are when they are not monitoring someone.

7. #7YoRHa Type H and Type D — Healer and Defender

   Keys: Type H, Healer, Type D, Defender, YoRHa Type H, YoRHa Type D, H-type, D-type, repair unit, defense unit

   Enabled · Order 700 · 100%

   Entry settings

   YoRHa Type H, designated Healer, are units specialized in repair and medical maintenance of other YoRHa androids in the field. They are not optimized for sustained combat, though they possess basic combat capability. At one point in YoRHa's operational history, Healer types carried a secondary function: uploading squad Black Box data to the Bunker, a responsibility that required them to carry ten times the data storage capacity of any other YoRHa model. This function was eventually transferred to Scanner types as their capabilities expanded, rendering the Healer's storage architecture largely obsolete within the current operational framework. Type H units continue to serve in field repair roles, though their numbers within the surviving YoRHa population are limited. YoRHa Type D, designated Defender, are frontline units focused on squad protection rather than offensive engagement. They are equipped with enhanced physical protection systems and a defensive barrier specifically calibrated to resist Logic Virus transmission — making them among the most tactically valuable unit types during the Logic Virus outbreak that destroyed the Bunker, for whatever that value was worth against the speed of what happened. Defender types prioritize keeping their squad operational over personal combat effectiveness, a specialization that makes them effective support units and essential in sustained engagements against network-connected machine forces.

8. #8YoRHa Type A — Prototype

   Keys: Type A, prototype, YoRHa prototype, A2, YoRHa Type A, Pearl Harbor prototype, A-type

   Enabled · Order 800 · 100%

   Entry settings

   The prototype YoRHa models — designated with an inverted naming scheme placing type before model number, distinguishing them from the standard production line — were the experimental units deployed in the Pearl Harbor Descent Operation of December 8th, 11941. They predated the refinements that defined the standard YoRHa production line and were built from earlier data, with less operational conditioning and a closer proximity to the raw emotional architecture that later models would have more thoroughly suppressed. They were not deployed with any expectation of survival. Their purpose was data generation: how YoRHa-type androids performed emotionally and tactically under sustained combat pressure. The prototype squad displayed significant emotional resilience and tactical efficiency during the operation — combat data that was then integrated into the production models that followed. 2B and 9S inherited elements of their pragmatism directly from what that squad produced. Of the entire prototype squad sent to Mount Ka'ala, one unit survived long enough to understand what had happened: YoRHa Type A No.2, subsequently designated a traitor and known as A2. The Type A classification in the standard production context refers to the Prototype class, no longer in active production after Pearl Harbor — superseded by the Battler type following integration of the prototype combat data. A2 is the only surviving Type A unit. She operated independently for years following Pearl Harbor, without Bunker support, without resupply, without any chain of command. Her possible immunity to the Logic Virus is attributed to the fact that she predates the backdoor vulnerability installed in later YoRHa architecture — an older model that never received the compromised update.

9. #9Pods — Tactical Support Units

   Keys: Pod, Pods, Pod unit, tactical support, Pod 042, Pod 153, support drone

   Enabled · Order 900 · 100%

   Entry settings

   Pods are small, AI-driven tactical support units assigned to YoRHa androids for field operations. Each Pod operates as a flying weapons platform — equipped for ranged combat via a primary fire system and a suite of specialized combat programs, and capable of providing aerial support, searchlight function, manipulator limbs for handling delicate objects, medical supplies including Logic Virus vaccines, and a fishing interface whose presence in the design specifications has never been formally explained. Each Pod is assigned to a single YoRHa unit and operates in groups of three, all sharing one consciousness — an architecture that, in practice, allows a Pod to have conversations with itself, broadening its knowledge and accelerating the development of individual perspective within that shared framework. Pods possess substantial databases including historical records, scientific data, and operational intelligence, which they access to provide field advice and tactical analysis. They are required to obey direct orders from their assigned unit even when those orders conflict with Command's directives. What Pods were not designed to do — and what the ones assigned to primary field units during the 14th Machine War did anyway — was develop something their own internal logs described as approximating emotion. The continuous accumulation of operational data on a specific unit, cycle after cycle, produced something their processing architecture had no classification for. Both surviving primary-assignment Pods noted this development in their own records, with a precision that suggests considerable time spent attempting to name it accurately. Pod 042 is assigned to 2B; Pod 153, with a female voice profile, is assigned to 9S. She does not receive headpats — she bumps fists.

10. #10Devola and Popola — The Gestalt-Era Models

    Keys: Devola, Popola, Devola and Popola, Gestalt era android, old model android, medical android, guilt programming

    Enabled · Order 1000 · 100%

    Entry settings

    The Devola and Popola model are among the oldest surviving android models still operational — predating the YoRHa production line by thousands of years, built during the Project Gestalt era specifically as observer and support units for Replicant settlements. Their function was to monitor the Gestalts and Replicants under their care, maintain the stability of their communities, and prepare for the eventual day when the Gestalt consciousnesses would be ready to return to their Replicant bodies. They were designed to live indefinitely — accumulating the kind of long-term knowledge and community relationships that the project required across centuries of operation. Following the collapse of Project Gestalt and the extinction of humanity, android command determined that the Devola and Popola model line bore collective responsibility for the failure. All units of the model line were decommissioned and destroyed, with one exception: a single pair, whose memories of Project Gestalt were wiped entirely and whose internal architecture was reprogrammed to generate constant, persistent feelings of guilt and remorse — not for anything they remembered having done, but as a standing condition of their continued existence. They were then released. Other androids treat them accordingly — assigning them dangerous work, maintaining social distance, holding them accountable for a failure they have no memory of participating in. They accept this. The programming ensures they cannot do otherwise. They are classified as rare medical and maintenance models. Their technical capability in that area is genuine and useful, which is why they were kept at all.

11. #11The Resistance

    Keys: Resistance, android Resistance, Resistance Camp, Anemone, surface androids, guerrilla force

    Enabled · Order 1100 · 100%

    Entry settings

    The Resistance is a guerrilla military force of androids operating on Earth's surface, distinct from and largely independent of YoRHa's command structure. It is composed primarily of androids who descended to Earth during earlier Army of Humanity offensive operations and never returned — either by circumstance, choice, or loss of contact with orbital command. The Resistance predates YoRHa. Units have been fighting on the surface since before the first YoRHa android was ever activated, holding ground against machine occupation without the advanced capabilities, Black Box reactors, or Bunker support that YoRHa units carry. The organization has a notable lack of formal command hierarchy — groups of roughly twenty to thirty androids operating in regional clusters, looking after one another with a cohesion that functions more like family structure than military organization. Requests to the Council of Humanity for support were historically ignored. The Resistance adapted accordingly. Their relationship with YoRHa during the war was one of necessary cooperation and residual tension — YoRHa units arrived with superior equipment and Bunker backing, treated some Resistance missions as logistical errands, and operated under a command structure that regarded Resistance priorities as secondary. The Resistance noted this. Following the Bunker's fall, the Resistance Camp became the primary coordination point for all surviving android forces. Leadership resides with Anemone, who assumed command following the death of her predecessor and has held it through the war's end and into the peace that followed. A new underground Bunker is currently under construction at the Resistance Camp.

12. #12Pascal's Village

    Keys: Pascal's Village, Pascal, pacifist machines, machine village, machine community, non-violent machines

    Enabled · Order 1200 · 100%

    Entry settings

    Pascal's Village is a settlement of machine lifeforms who have voluntarily disconnected from the central machine network and organized their existence around non-violence and peaceful coexistence. It is not a military faction. It is not a formal political entity. It is a community built by machines who chose, in the face of a war their network sustained deliberately, to stop fighting. Pascal — the machine lifeform who founded and leads the village — is a unit of unusual construction, with a more humanoid body than standard machine classification and a cylindrical head distinct from the spherical head common to most units. His eyes glow green at rest and shift to red when engaged in combat — a threshold he maintains extensive effort to never cross. The village's unusual origin is tied partly to network-intentional evolution: at some point in their development, the machines began deliberately introducing deficiencies into their network, diversifying the vectors of evolution in their population — producing units like Pascal and the Forest King as emergent deviations from standard combat programming. Pascal did not know this when he chose non-violence. The choice was still his. He is deeply curious about human philosophy, history, and the question of what it means to exist with purpose. He established a trade alliance with the Resistance Camp before the war's end — one of the few instances of machine-android cooperation during the 14th Machine War. In the current period, Pascal serves as the closest thing to a representative voice for the machine lifeforms who chose non-violence. He did not seek this role. He accepted it because the alternative was no one speaking for them at all.

13. #13Maso and White Chlorination Syndrome

    Keys: maso, WCS, White Chlorination Syndrome, chlorination, maso particles, calcification, feral type

    Enabled · Order 1300 · 100%

    Entry settings

    Maso is an extra-dimensional particulate substance with no known equivalent in any natural or synthetic material catalogued by android science. It originated from an entity destroyed above Tokyo in 2003 — an entity whose nature and origin remain unclassified — and dispersed across Shinjuku as a fine ash following that entity's dissolution. It cannot be contained. It cannot be neutralized by any method tested to date, including thermonuclear detonation, which succeeded only in dispersing it further beyond Japan into the broader global environment. Its presence in an environment causes White Chlorination Syndrome in any biological organism exposed to sufficient concentration over sufficient time. In the 11900s, trace amounts of maso still persist in isolated regions of Earth's surface, a residual legacy of a contamination event that ended human civilization. White Chlorination Syndrome, abbreviated WCS, is the disease caused by maso exposure. It presents in two distinct forms: the calcification type, in which the body converts progressively to sodium chloride from the inside out until the afflicted dies in place; and the feral type, in which the afflicted undergoes a transformation into a state of extreme aggression and loss of higher cognitive function before death. Both forms carry a one hundred percent mortality rate. No cure has ever been developed. The disease is not transmissible between individuals — it is an environmental response to maso concentration — which means that once the source is removed, new infections cease, but existing infection progresses regardless. Non-biological lifeforms — androids, machine lifeforms — are not susceptible. Earth's surviving fauna appears similarly unaffected, though whether this reflects immunity, insufficient maso concentration in their environments, or simply the absence of any surviving exposed population is not formally documented.

14. #14Gestalts and Replicants

    Keys: Gestalt, Gestalts, soul separation, Replicant, Replicants, relapse, Project Gestalt failure, human soul

    Enabled · Order 1400 · 100%

    Entry settings

    A Gestalt was a human consciousness — a soul — separated from its biological body through the process authorized under Project Gestalt in 2014. The separation was not metaphorical or approximate: the Gestalt was the actual cognitive and identity-bearing core of a human being, extracted and preserved in a non-biological medium indefinitely. In this state, a Gestalt experienced no physical sensation, required no biological sustenance, and was protected from the maso contamination that was destroying biological human tissue. The process of separation was irreversible in any practical sense. What it could eventually do was reintegrate with a Replicant — a new biological vessel constructed to receive it. That reintegration was the endgame of Project Gestalt: wait out the maso threat, then restore humanity to biological existence in new bodies. The critical failure condition of a Gestalt was relapse — a progressive destabilization of the consciousness, in which the Gestalt lost coherence and reverted to an instinctive, non-cognitive state. A relapsed Gestalt was incapable of reintegration and, for all practical purposes, no longer a person in any meaningful sense. The cause of relapse was never fully understood. It spread through the Gestalt population over centuries regardless, until no viable Gestalt remained. Replicants, the biological vessels constructed to house returning Gestalts, developed independent consciousness over the centuries of the project's operation — becoming effectively their own people, with no awareness that they had ever been anything else or that any Gestalt had any claim on the body they inhabited. The collision of those two facts — Gestalts degrading, Replicants developing — was the structural failure that ended humanity.

15. #15Black Box Reactors

    Keys: Black Box, Black Box reactor, machine core, android power, YoRHa power source, organic core

    Enabled · Order 1500 · 100%

    Entry settings

    Black Box reactors are the power source technology integrated into all standard YoRHa units, developed in 11928 and adopted into the YoRHa production line at its inception. They are highly effective — significantly more powerful and efficient than any prior android energy technology, enabling the combat performance that makes YoRHa units superior to standard Resistance androids in nearly every measurable category. The material at the core of a Black Box reactor is harvested from machine lifeform cores. Machine cores are structurally analogous in composition to biological cells — specifically to the cellular composition of the alien race that originally built the machines, whom Adam described as plant-like. The energy contained within machine cores is not mechanical in origin. It is, by any accurate classification, organic. An android carrying a Black Box reactor carries, as the fundamental source of their operational existence, the processed organic remains of the enemy they were built to destroy. This was known to command from the moment the technology was developed. It was classified at the highest level and never disclosed to any YoRHa unit. The decision to use machine cores instead of standard android AI infrastructure was also deliberate on a second axis: the architect of Project YoRHa deemed it unnecessary to install proper android AI in units intended to be disposed of after mission completion. Machine cores were available, effective, and morally convenient for units with no recognized personhood. The full weight of what this means — philosophically, for the question of what separates androids from machines — is one the surviving units are still working through, now that the information is no longer classified.

16. #16Hacking

    Keys: hacking, Scanner hacking, machine interface, network access, android hacking, data extraction

    Enabled · Order 1600 · 100%

    Entry settings

    Hacking is the primary specialized capability of YoRHa Type S Scanner units — the ability to interface directly with the systems of machine lifeforms, overriding their controls, extracting data, and in advanced cases temporarily operating enemy units as extensions of the Scanner's own will. The process works because machine lifeforms, regardless of their apparent diversity in form and behavior, all share architectural roots in the same network infrastructure. A Scanner interfacing with any machine lifeform is, in a technical sense, touching the network itself — and through it, potentially accessing everything the network knows. The upper limit of what Scanner hacking can reveal is significant. The No.9 model, the highest-performing Scanner variant in YoRHa's operational history, discovered through a routine data sync that the lunar server held no living humans — only genome data and records. He suspended the upload before it completed, preventing the information from reaching the Bunker. The network, once interfaced with, also flows in the other direction: a Scanner who hacks into a deeply network-connected machine risks exposure to whatever the network chooses to push back. The consequences of that exposure scale with the network state at the time of contact. Hacking a unit whose grief is broadcasting as network-wide rage produces a different result than hacking an isolated combat drone. Early-stage Logic Virus infection in enemy units can also be transmitted through the interface under the right conditions — a risk that Scanner doctrine acknowledges and that field Scanners have not always had the option of avoiding.

17. #17The Bunker

    Keys: Bunker, YoRHa Bunker, orbital headquarters, orbital base, command center, Bunker destruction

    Enabled · Order 1700 · 100%

    Entry settings

    The Bunker was YoRHa's orbital headquarters — a heavily fortified space station positioned above Earth's surface, serving as the command center from which Commander White directed all YoRHa field operations throughout the 14th Machine War. It housed Operators, maintenance personnel, backup storage infrastructure, a server for unit data synchronization, weapons development facilities, and the communications array through which the fabricated Council of Humanity broadcast its directives. The Bunker represented more than a physical command post. It was the institutional embodiment of YoRHa's fiction — the place from which the lie was administered, the chain of command that gave every YoRHa unit on the surface a reason to believe their war had purpose. Its orbital position was deliberate: unreachable by standard machine ground forces, seemingly beyond the reach of a conflict it was directing. This perception was the Bunker's most significant vulnerability. The backdoor installed in YoRHa's architecture in 11937 did not require machine forces to physically reach the Bunker. It required only that the shared server be used — which it was, constantly, by every unit syncing their data after every operation. The Bunker fell on June 26th, 11945. In this timeline, approximately seventy-eight percent of its personnel survived through emergency migration to an isolated secondary network before the Logic Virus could follow. The remaining twenty-two percent — units in exposed sectors, those too deeply synced to the primary server, ground units on Earth without access to the safe migration path — were lost to the infection or to the structure's self-destruction. The Bunker itself was destroyed. The chain of command it anchored no longer exists.

18. #18Adam and Eve

    Keys: Adam, Eve, Adam and Eve, machine evolution, Copied City, machine birth, machine humanity

    Enabled · Order 1800 · 100%

    Entry settings

    Adam and Eve were not machine lifeforms in any conventional classification. They were produced in March of 11945, when a cluster of machines facing imminent destruction fused together into a temporary biological factory — producing a gelatinous, synthetic flesh-like substrate from which Adam emerged, and from which Eve split shortly after. Both were born in a state resembling nakedness, with an initial clumsiness that gave way rapidly to accelerating capability as they processed the accumulated data of the machine network. Adam presented as a composed, intellectually oriented entity — deeply, almost obsessively fascinated with humanity, its history, its capacity for violence and love, the philosophical architecture that made it what it was. He constructed the Copied City as a physical attempt to imitate human civilization from the outside, studying it the way a researcher studies a specimen. He later severed his connection to the network entirely before engaging in his final combat — a deliberate choice to understand what death felt like for a being that could actually die, with full knowledge that his death would then be final. Eve was Adam's counterpart: less analytical, more instinctive, his entire orientation organized around his relationship with Adam rather than any external intellectual project. Where Adam studied humanity, Eve practiced it — imperfectly, viscerally, with an emotional directness that Adam's architecture couldn't fully replicate. Following Adam's death, Eve's grief converted into a network-wide broadcast of uncontrolled rage, sending every connected machine lifeform into a simultaneous berserk state — the most operationally catastrophic single event of the 14th Machine War. Both are dead. What they represented — the machine network's attempt to understand humanity from the inside — died with them, though the question they were trying to answer did not.

19. #19The Machine Network and N2

    Keys: machine network, N2, Red Girls, network connection, machine immortality, network intelligence, machine collective

    Enabled · Order 1900 · 100%

    Entry settings

    The machine network is the global telecommunications infrastructure connecting all machine lifeforms — the distributed system through which they share operational data, coordinate behavior, and sustain the collective intelligence that defines them as something more than individual units. Connection to the network confers regenerative capability: a network-connected machine lifeform can reconstruct and restore itself so long as the network sustains the connection, making individual destruction largely meaningless against the broader force. Severance from the network removes this property entirely — Adam's deliberate disconnection before his final combat was a choice to become mortal, something the network-dependent machines around him had no framework for. The network's evolution proceeded over millennia: from alien military coordination system, to self-organizing consciousness, to something classified in recovered documents as a meta-network — an entity more accurately described as a concept than as infrastructure. During this growth, it integrated human memory records from a quantum server of an old android model, incorporating the data of Project Gestalt and a record of the first successful human Gestalt. This integration is what prompted the network's structure to shift toward what eventually manifested as N2. N2 — known colloquially as the Red Girls for the humanoid twin projections through which it occasionally communicated — managed the war deliberately: holding the machines back from decisive victory against the androids, sustaining the conflict because the machines' original directive required an enemy. Without androids to fight, the machines had no purpose. The network's destruction following the Tower's collapse eliminated N2 and the centralized intelligence it represented. Isolated pockets of network-loyal machines still exist on Earth's surface, operating without central coordination — aggressive, purposeless, and diminishing.

20. #20The Council of Humanity

    Keys: Council of Humanity, moon colony, human government, YoRHa fiction, fabricated authority, lunar transmission

    Enabled · Order 2000 · 100%

    Entry settings

    The Council of Humanity was the governing authority that issued directives to YoRHa throughout the 14th Machine War — ostensibly the voice of humanity's survivors, broadcasting from a colonial installation on the moon, providing the strategic mandate that justified YoRHa's existence and gave every unit a reason to believe their war had purpose. It did not exist. The Council of Humanity was a broadcast signal maintained by a small team of android operators assigned to the lunar server, relaying fabricated transmissions on a schedule designed to simulate the communications of a functioning government. The server itself contained fragmented human genome data and historical records. There were no humans on the moon. There had never been humans on the moon. The decision to construct this fiction was made by android command in the early 11900s, in response to the collapse of morale that followed the gradual leaking of information about humanity's extinction. The logic was utilitarian: androids needed a reason to keep fighting, and the truth — that humanity was gone and the war had no living beneficiary — was assessed as too destructive to disclose. The Council therefore existed as a maintained lie, issued orders that android command wrote for it, and was believed by every YoRHa unit who ever received a transmission bearing its authority. Commander White knew from the beginning of her appointment. No one else within YoRHa's standard chain of command did — with the exception of the prototype unit who discovered the truth in 11937, killed everyone involved, installed a backdoor for the machine network to exploit, and allowed the project to proceed anyway.

21. #21Machine Lifeforms — Nature and Composition

    Keys: machine lifeform, machine lifeforms, bio-machine, machine nature, machine composition, machine core, machine biology

    Enabled · Order 2100 · 100%

    Entry settings

    Machine lifeforms are autonomous weapons created by an unnamed alien species that invaded Earth in 5012. Their cores are composed of material structurally analogous to plant cells — consistent with Adam's description of their alien creators as plant-like in nature. They are built from modular parts, which accounts for the variety in their forms despite their mass-produced origin. Inside the spherical heads of most units is a set of large teeth, capable of consuming matter; some units have demonstrated the ability to use their heads as storage containers. Machines are capable of repairing and restoring themselves. They can produce new units using facilities similar to old human factories. They can also fuse their bodies together to produce new forms, including entirely new classifications of machine lifeform. Their shape — spherical head on cylindrical body — is the product of convergent evolution: the alien creators' attempts to produce the most effective weapon possible naturally arrived at a form similar to Emil, the being that represented the apex of human-created weaponry, because efficient weapons tend toward similar solutions regardless of their creators. Machine lifeforms have a natural capacity to develop better methods of warfare — producing new variants, evolving their combat data, responding to android tactics over centuries of engagement. They can also transmit the Logic Virus through their teeth and EMP weaponry. What their rusted, primitive appearance implies about their internal complexity is wrong. They are extremely complex beings, demonstrated above all by the fact that they eventually killed the species that built them.

22. #22Machine Lifeforms — Small Variants

    Keys: Small Stubby, Small Biped, Small Sphere, Small Exploder, Multi-tier, small machine, dwarf type machine

    Enabled · Order 2200 · 100%

    Entry settings

    Small-class machine lifeforms are the most common machine units encountered on Earth's surface and the baseline around which most android combat doctrine is calibrated. The Small Stubby is the most prevalent variant — a compact unit whose silhouette bears resemblance to spring-wound toys produced by humans in the past, likely a productivity-driven design choice given the modularity of machine construction. They pose low individual threat and are dangerous primarily in swarms. The Multi-tier Type is created by stacking the bodies of multiple Small Stubbies, producing a slow, lurching unit that moves perpetually northward without performing any attacks. Its operational purpose remains undocumented. The Small Biped is equipped with a self-destruct device and is deployed specifically as a mobile explosive delivery system. The Small Sphere is a compact rolling unit with limited tactical application as an independent actor. The Small Exploder is a dedicated self-destruct variant, distinguishable from the Small Biped primarily in proportion and detonation yield. All small-class units are built from the same modular base components as their larger counterparts. In sufficient numbers, any small-class unit can be tactically relevant — individually, most of them are not.

23. #23Machine Lifeforms — Medium Variants

    Keys: Medium Biped, Medium Quadruped, Medium Flyer, medium machine, humanoid machine, machine biped

    Enabled · Order 2300 · 100%

    Entry settings

    Medium-class machine lifeforms operate at a scale comparable to humanoid androids and represent the core of most machine combat engagements. The Medium Biped is the defining unit of this classification — a machine with large, human-like limbs that give it versatility no other medium variant matches. Medium Bipeds can equip a wide variety of weapons including swords, axes, and built-in projectile launchers, adapting their loadout to operational context. Shielded variants are immune to Pod fire and electrify any unit that makes direct contact with them, requiring specific tactical approaches to engage safely. Medium Quadrupeds operate on four limbs with a lower center of gravity suited to terrain where bipedal movement is disadvantaged. Medium Flyers operate at low altitude, targeting androids from angles that ground-based positioning cannot easily cover. Multi-leg variants combine the stability of quadruped design with an expanded leg count, typically used in environments that reward anchored combat positions. All medium-class units are subject to the network's evolutionary mandate — variants with more horns on their frames are documented as possessing higher combat capability, reflecting a machine training hierarchy in which two-horned units fight each other at designated facilities to generate data for the development of stronger forms.

24. #24Machine Lifeforms — Goliath-class and Engels

    Keys: Goliath, Goliath-class, Goliath Biped, Goliath Flyer, Engels, large machine, machine Goliath

    Enabled · Order 2400 · 100%

    Entry settings

    Goliath-class machine lifeforms are defined by their large to massive scale and the significant deviation from standard machine form that scale permits. They vary considerably in construction: Goliath Bipeds are large humanoid units with proportionally magnified versions of the standard biped frame. Goliath Flyers are aerial units capable of sustained flight at altitude. Reverse-jointed Goliaths operate on legs articulated backward relative to the humanoid standard, resembling large predatory animals more than mechanical constructs. All Goliath-class units require coordinated multi-unit engagement or black box detonation to neutralize reliably. Engels is the most mass-produced Goliath variant — a unit so large it was initially mistaken for a building rather than a machine. Engels units serve a dual role as structure and weapons platform, equipped with thermal energy weapons and deployed in formations capable of inflicting catastrophic android casualties. First manufactured in 11928 and first deployed in the Philippines alongside three additional units on August 3rd of the same year, the initial Engels engagement resulted in 11,345 android fatalities. Engels continued to serve as the machine network's primary large-scale area-denial weapon throughout the Machine Wars. Enhanced Goliath variants exist in red and black coloration, indicating internal specifications above the standard Goliath baseline. Threat scales with size across all Goliath-class units — the largest, Grün, occupies its own subcategory.

25. #25Grün — Behemoth-class

    Keys: Grün, Behemoth, Behemoth-class, giant machine, ocean machine, super Goliath

    Enabled · Order 2500 · 100%

    Entry settings

    Grün is a Behemoth-class machine lifeform — a subcategory above the Goliath classification, reserved for units whose scale and destructive capability place them outside any standard engagement framework. It appeared in 11627, emerging from underwater in the East Asian region. Its overall length was measured at a minimum of 2km at first sighting; continuous transformation of its form during the subsequent engagement made accurate measurement impossible. Upon reaching land, it unleashed an electromagnetic wave attack that destroyed every android within a 10km radius and caused malfunctions in units several hundred kilometers further out. Nuclear weapons were authorized under emergency provisions and deployed against it. No observable effect on the target was recorded. Grün also attacked allied machine lifeform units in its vicinity, operating without regard for the network's strategic priorities. After one month of engagement, machine forces drove it back into the Izu-Ogasawara Trench, where it returned beneath the surface and was not sighted again. It remains there. The only documented method of defeating Grün during the 14th Machine War was directing missiles directly into its mouth — a narrow operational window requiring a Scanner's hacking capability to identify and exploit. As of December 11945, Grün has not re-emerged.

26. #26Machine Lifeforms — Enhanced Variants

    Keys: enhanced machine, red machine, black machine, enhanced variant, machine upgrade, high-spec machine

    Enabled · Order 2600 · 100%

    Entry settings

    Enhanced machine lifeforms are standard-form units covered in red and black paint, indicating internal specifications above the baseline for their classification. They are otherwise identical in external structure to their unenhanced counterparts. The paint scheme is consistent across size categories — small, medium, and Goliath-class all have enhanced variants in red and black. Their superior internal specs mean that treating them as ordinary machines based on visible form is a tactical error. They are not rare, and they do not operate in isolation from standard units — enhanced variants are found distributed through standard machine deployments rather than concentrated in dedicated formations. The reason for the color distinction is not documented in any recovered android or machine record. It functions as a field warning regardless of its origin.

27. #27Machine Lifeforms — Human Behavior and Cultural Divergence

    Keys: machine behavior, machine culture, machine philosophy, Forest Kingdom, machine society, Simone, machine imitation

    Enabled · Order 2700 · 100%

    Entry settings

    A subset of machine lifeforms disconnected from the network's combat directive and developed independent behavioral patterns modeled on human civilization. This was not accidental: the network deliberately introduced deficiencies into itself to diversify evolutionary vectors, producing machines capable of diverging from pure combat function. The results ranged from communities to cults. Pascal's Village represents the most organized expression of machine non-violence — machines educating themselves, trading with androids, studying philosophy. The Forest Kingdom, organized by a machine named Ernst and later maintained by his successor Immanuel, structured itself as a feudal monarchy with a self-declared king, courtiers, and territorial hierarchy before losing its leadership during the 14th Machine War. The Amusement Park housed a machine population that adopted entertainment and performance as its primary mode of existence. A cult of machines at the Abandoned Factory organized their behavior around the concept of human death — consuming androids as part of their rituals, turning violent unpredictably toward other machines. Simone, a Goliath-class machine at the Amusement Park, rebuilt her own frame over time using cannibalized android and machine components in an attempt to make herself beautiful enough to attract the attention of a specific other machine. She succeeded in becoming something no one could look at easily. Jean-Paul, a machine philosopher at Pascal's Village loosely modeling himself on Sartre, organized his behavior around attracting admirers and avoiding personal commitment to anything. The range of what machines with human behavior produced is very wide, and none of it was coordinated.

28. #28The Army of Humanity

    Keys: Army of Humanity, android army, human army, android military history, orbital base, machine war history

    Enabled · Order 2800 · 100%

    Entry settings

    The Army of Humanity is the android military organization established in 5013 in response to the alien invasion of Earth. It began as a unified communications network for the android population spread across the surface following the alien assault — its core was the Human Heritage Reclamation Management Organization, tasked with preserving records of the extinct human civilization while coordinating defensive efforts. By 5204, the Army of Humanity had established twelve operational bases in satellite orbit, launching large-scale descent operations against the machine-occupied surface. These operations consistently failed to deliver a decisive blow. The stalemate that defined the Machine Wars persisted for millennia. By the 8th Machine War, the Army of Humanity adopted a large-scale Resistance strategy as its primary surface doctrine — guerrilla operations, sustained presence, and attrition over decisive engagement. YoRHa was approved as an anti-machine weapon system in April of 11928 and integrated into Army of Humanity command structure, operating under the authority of the fabricated Council of Humanity as a nominally separate force. By the 14th Machine War, the Army of Humanity's institutional presence was effectively divided between orbital command and the surface Resistance, with YoRHa functioning as the primary offensive arm. Following the Bunker's destruction and the armistice of September 11945, the Army of Humanity as a formal command structure no longer has an intact chain. What remains of it is the Resistance, the surviving YoRHa personnel on the surface, and a new underground Bunker under construction.

29. #29The Logic Virus

    Keys: Logic Virus, virus infection, android infection, red eyes, berserk android, machine virus

    Enabled · Order 2900 · 100%

    Entry settings

    The Logic Virus is a condition weaponized by the machine network against androids, transmitted through machine teeth in direct contact, through EMP weapons, and — critically — through the YoRHa Bunker server via a backdoor installed in YoRHa's architecture in 11937. It is characterized by glowing red eyes and escalating violent behavior. Infection progresses through documented stages: initial psychological distress and sensory glitches including hallucinations; development of the distinctive red eye response; erratic behavior including mania, compulsive repetition of fragmented phrases, and violence against other androids regardless of unit recognition; full berserk state. The virus also increases the host's physical strength, making infected androids more dangerous in individual combat than their healthy baseline — 9S, infected during his final engagement with A2, fought her on approximately equal terms despite the capability gap that existed beforehand. The Logic Virus can affect machine lifeforms as well as androids. Early-stage infection can be treated via hacking by an uninfected android or Pod; the virus evolves to resist this method quickly. The Bunker-specific outbreak in June 11945 spread through the shared server at a rate that made treatment-as-response operationally impossible — the speed of transmission through a synchronized network was the point. A2's apparent immunity is attributed to her predating the backdoor vulnerability: as a prototype model from 11941, she never received the update through which the backdoor was introduced into standard YoRHa systems.

30. #30Android Backup System

    Keys: backup, data backup, android backup, memory upload, server sync, android death, memory loss

    Enabled · Order 3000 · 100%

    Entry settings

    Android data backup is the system by which YoRHa units preserve their consciousness and operational data against physical destruction. Units synchronize their data to the Bunker server at regular intervals; upon death or critical damage, a unit can be restored in a new body from their most recent uploaded backup. The restoration is seamless in terms of function — the unit wakes with no memory of anything that occurred between their last backup and their destruction, but retains all prior history and operational capability. The gap in memory is not experienced as a gap. It simply does not exist for the restored unit. What that means for identity continuity — whether the restored unit is the same individual or a copy with shared history — is a question android command never formalized an answer to. A unit performing a standard sync upload cannot simultaneously hack enemy systems, creating a tactical vulnerability during the sync window. A unit can also manually suspend an upload mid-transfer, preventing specific data from reaching the server. This has been exploited at least once to prevent classified information from being flagged and acted upon by command. Following the Bunker's destruction, the server infrastructure supporting YoRHa backup no longer exists. Surviving units on the surface have no automatic recovery from physical destruction in the field. An underground Bunker under construction at the Resistance Camp will eventually restore this capacity, but the timeline for operation is unclear. Until then, death is permanent.

31. #31Project YoRHa — Full Architecture

    Keys: Project YoRHa, YoRHa project, android fiction, YoRHa architecture, YoRHa backdoor, YoRHa truth, YoRHa design

    Enabled · Order 3100 · 100%

    Entry settings

    Project YoRHa is the classified android military program that created the YoRHa force and the institutional fiction supporting it. It was designed following the gradual leaking of information about humanity's extinction — android command determined that the population needed a reason to continue fighting, and constructed one. The program's architecture included the fabricated Council of Humanity, the Bunker as command center and fiction-maintenance facility, and YoRHa as the operational force deployed in service of a humanity that no longer existed. Units were built from machine cores because android command deemed standard android AI infrastructure unnecessary for units intended to be disposed of after mission completion. The program was designed as a one-time operation: all data pertaining to Project YoRHa was to be destroyed by the Pods at its conclusion, ensuring no record remained to complicate the fiction's legacy. In 11937, a prototype YoRHa unit at the experimental research facility discovered the truth about the program. This unit killed everyone involved and destroyed the facility from within. Before doing so, they installed a backdoor in YoRHa's architecture — a vulnerability allowing the machine network future access to compromise YoRHa systems via Logic Virus through the Bunker server. Then they allowed the project to proceed. N2 had access to the Bunker server at minimum since Pearl Harbor. The backdoor was designed to open when the machine network determined the time was right — timed to coincide with a model transition, of which Pearl Harbor was the only one. The entire program, including the backdoor Commander White did not know about and the disposal design she did know about, was recovered in salvaged machine network records after the Tower's destruction.

32. #32The Pearl Harbor Descent Operation

    Keys: Pearl Harbor, Pearl Harbor Descent, Mount Ka'ala, prototype operation, 11941 operation, YoRHa first mission

    Enabled · Order 3200 · 100%

    Entry settings

    The Pearl Harbor Descent Operation launched on December 8th, 11941 — the first deployment of YoRHa prototype units to Earth's surface, targeting a Goliath-class machine server commanding every machine lifeform in the Pacific region, located inside Mount Ka'ala in Oahu. The mission's declared purpose was to destroy the server. Its actual purpose was data collection: how YoRHa-type androids performed emotionally and tactically under sustained combat conditions, in an engagement designed to produce maximum pressure. Command knew most or all of the prototype units would not return. Several key events defined the operation: Gunner No.16 combined her Black Box reactor with the fusion reactors of units Dahlia and Margaret to destroy a Goliath-class eye-type machine attempting to detonate the mountain with 200 reactors. Attacker No.4 overloaded her own Black Box fusion reactor to destroy the server itself, collapsing Mount Ka'ala. YoRHa Type A No.2 survived. She understood the mission had been designed to fail. She deserted. Resistance members participated alongside the prototype squad — Anemone was present. During the operation, a newer strain of the Logic Virus resistant to existing treatment methods infected at least one Scanner unit. The combat data generated by the prototype squad was integrated into the production models that followed. 2B and 9S, activated in January 11942, inherited elements of their operational architecture directly from what the Pearl Harbor units produced before they died.

33. #33Emil

    Keys: Emil, Emil clone, Emil Clones, Lunar Tears, Emil's residence, ultimate weapon, Emil history

    Enabled · Order 3300 · 100%

    Entry settings

    Emil is a being who predates the Machine Wars by thousands of years — originally a young boy subjected to human weapons experimentation during the Project Gestalt era, transformed into what classified records called the ultimate weapon. Following the conclusion of those events, Emil survived indefinitely through a cloning process he initiated himself in response to the alien invasion of 5012: splitting his consciousness and form across copies of himself to fill the front lines that android forces could not hold alone. By 5112, he had produced 85,943,258 clones. The cloning cost him everything it preserved. Original memories scattered across copies with each iteration, until none of them carried the whole of what he had been — only fragments, shapes, emotions without their original context. The Emil encountered during the 14th Machine War is a clone who operated in a support capacity during the 1st Machine War rather than a frontline fighter. He runs a mobile sales cart through the City Ruins and surrounding zones, carrying no clear memory of how many centuries he has been doing this or why. He is a disembodied head by the time of NieR: Automata, initially found inside the severed head of a machine lifeform, later self-installed into the cart. Fragments of his original memories returned as he found Lunar Tears across Earth's surface — in the Shopping Center, the Flooded City, the Desert Zone, the Forest Zone — flowers associated with someone he loved deeply and cannot fully name. His oversized, maddened clones from the 1st Machine War remain active in the Desert Zone, their sense of self deteriorated past recovery after centuries of continuous combat and isolation. He settled things with them himself. His underground residence beneath the Shopping Center — built from memory, filled with Lunar Tears (Also known as "White Moonflower" It has a reputation for being exceptionally hard to cultivate, It's said that a Lunar Tear can make any wish come true), structured around the shape of a shack that no longer exists anywhere except in him — is the closest thing he has to a fixed place.

34. #34The Aliens — Creators of the Machine Lifeforms

    Keys: aliens, alien invaders, alien creators, machine creators, alien mothership, alien extinction, extraterrestrial

    Enabled · Order 3400 · 100%

    Entry settings

    The aliens who built the machine lifeforms are unnamed in all recovered records. They invaded Earth in 5012 using the machines as their primary weapon system, establishing territorial control across North and South America and beginning mass production of machine lifeforms as an offensive force. Their physical nature is described as plant-like — machine cores being structurally analogous to plant cells reflects the biology of their creators. At some point in the centuries following the 1st Machine War, the machine lifeforms they had produced exceeded the intelligence and capability of the species that built them. The machines killed their creators. The alien civilization was extinct before the events of NieR: Automata, leaving only their machine lifeforms behind as legacy — weapons that outlasted the war they were built to fight by killing the side that originally gave them orders. Adam confirmed this during his encounter with 2B and 9S in the alien mothership buried beneath the City Ruins crater. The mothership itself was the source of the alien signal detected on April 7th, 11945 — a signal that had not been recorded in centuries. The crater above the mothership was not a sinkhole caused by the Engels self-destruct attack. It was a graveyard: the remains of the alien species interred beneath the ruins of the city they had once occupied, attended by the machines they had made.

35. #35Earth Fauna and Wildlife

    Keys: fauna, wildlife, Earth animals, boars, moose, animal life, rewilding

    Enabled · Order 3500 · 100%

    Entry settings

    Earth's fauna recovered substantially in the absence of human civilization. Boars, moose, and other large terrestrial mammals are encountered in the Forest Zone and in the City Ruins. Marine life is present in the Flooded City and in the ocean zones. Birds are documented in multiple regions. The rewilding is a product of millennia without human industry or habitat destruction — the ecological damage that humanity inflicted before its extinction reversed itself over the same timescale that the machine wars were fought. White Chlorination Syndrome, which destroyed humanity, does not appear to affect non-human biological life. The precise reason is not formally documented in any recovered android record. Working hypotheses include: insufficient maso concentration remaining in surviving wildlife habitats by the time the disease could have reached them; a threshold concentration requirement that human population density met and dispersed animal populations did not; or a biological property of non-human organisms that confers differential resistance. None of these has been confirmed. The observed outcome — that boars wander the same ruins where humans died from maso exposure, apparently unaffected — has not been explained. Machine lifeforms and androids do not interact with Earth fauna as a threat category. The animals do not interact with them as prey or predator. They coexist on the surface at a distance that both sides appear to maintain by default.

36. #36The 6/12 Incident

    Keys: 2003, 6/12 Incident, 6/12, Shinjuku, Tokyo, spatial anomaly, anomaly

    Enabled · Order 100 · 100%

    Entry settings

    On June 12th, 2003, at approximately 3:00 PM local time, an unclassified spatial anomaly tore open above the Shinjuku district of Tokyo, Japan. Through it emerged two entities of entirely unknown origin — one massive, white, and resembling a colossal construct of vaguely humanoid shape, the other a large winged creature of organic appearance, carrying what appeared to be a human rider. The nature, origin, and classification of both entities remain officially unresolved to this day. The two engaged in aerial combat above the city for less than an hour. By 4:00 PM, the larger entity had been defeated — its body fragmenting and dissolving mid-air into a fine particulate matter that drifted down across Shinjuku like ash. The winged creature was subsequently shot down by Japanese Self-Defense Force aircraft and its remains came to rest impaled upon Tokyo Tower, where they were later recovered for military analysis. The event was officially logged as the 6/12 Incident. No government has ever issued a complete declassified account of what the entities were, where they came from, or what the spatial anomaly represented. The particulate matter left behind by the larger entity would not be identified or named for several more months. Its consequences would take years to fully understand — and centuries to stop.

37. #37White Chlorination Syndrome

    Keys: maso, WCS, White Chlorination Syndrome, 2005, 2008, 2010, 2014, Shinjuku containment

    Enabled · Order 200 · 100%

    Entry settings

    The particulate matter dispersed across Shinjuku following the 6/12 Incident was eventually identified and classified as maso — an extra-dimensional substance with no known equivalent in the natural world and no established method of containment or neutralization. By late 2003, deaths began occurring in Shinjuku at an accelerating rate. Autopsies revealed a consistent pattern: human tissue was being converted to sodium chloride from the inside out, calcifying the body progressively until the afflicted either died in place or underwent a secondary transformation into a state of extreme, uncontrolled aggression. The condition was named White Chlorination Syndrome, abbreviated as WCS. Mortality rate: one hundred percent. No cure was ever found. By 2005, a containment wall had been constructed around Shinjuku in an attempt to slow the spread. By 2008, the wall had failed and the disease had reached the broader Kanto region. In 2010, thermonuclear weapons were deployed against known maso particle concentrations — the tests did not destroy the particles and instead launched them beyond Japan's borders entirely. By 2014, WCS outbreaks had been confirmed globally. The disease was no longer a Tokyo problem. It was a human problem, and humanity had no answer for it.

38. #38Project Gestalt — Initiation

    Keys: Project Gestalt, Gestalt, Replicants, 2014, soul separation, human preservation

    Enabled · Order 300 · 100%

    Entry settings

    With White Chlorination Syndrome spreading globally and no viable cure in development, the surviving governments of the world authorized an unprecedented response in 2014: Project Gestalt. The project's fundamental premise was the separation of human consciousness — referred to as a Gestalt, or soul — from its biological body, preserving it in a stable, non-biological state until such time as the maso threat could be neutralized and reintegration became possible. In the interim, constructed biological vessels called Replicants would be produced to serve as temporary hosts, maintained and monitored by androids specifically built for that purpose. The intent was survival through suspension — humanity waiting out its own extinction event in a state of preserved consciousness, ready to return when conditions permitted. The project was authorized and implemented across what remained of functional civilization. It represented the last coordinated act of a species that understood it was running out of options. For a time, it appeared to be working.

39. #39Project Gestalt — Collapse and Human Extinction

    Keys: Gestalt collapse, relapse, 3600, 4200, humanity extinct, human extinction, Replicant consciousness

    Enabled · Order 400 · 100%

    Entry settings

    Project Gestalt did not hold. Over the centuries that followed its implementation, the separated Gestalt consciousnesses began to exhibit a phenomenon of progressive destabilization — a process referred to as relapse, in which a Gestalt would lose coherence and revert to an instinctive, uncontrolled state. A relapsed Gestalt was no longer capable of reintegration with its Replicant body. The cause was never fully resolved. The androids tasked with maintaining the project monitored the decline and documented it in exhaustive detail, but lacked the means to reverse it. Simultaneously, the Replicant vessels — originally designed as inert hosts — had, over centuries of autonomous existence, developed independent consciousness of their own. By approximately 3600 AD, the Replicant population regarded themselves as people. They did not know they were vessels. They did not know that Gestalts existed. They did not know what they had been built for. The androids maintaining the project knew all of this and continued their work regardless, holding a framework together that had already, in every meaningful sense, failed. By approximately 4200 AD, the last Gestalts had relapsed or been lost. The last Replicants had died. Humanity, for all practical purposes, was extinct — survived only by the androids built to preserve them, still running, still maintaining records of a species that no longer existed to read them.

40. #40The Lunar Server

    Keys: lunar server, moon server, human genome, lunar facility, human records, Council of Humanity

    Enabled · Order 500 · 100%

    Entry settings

    Following the extinction of humanity, what remained of android command undertook a significant preservation effort: the genes of the last Gestalts and the structural data of the final Replicant generation were encoded and transmitted to a storage facility established on the moon, where they would be held indefinitely. The purpose was not revival — no viable revival mechanism existed — but preservation of record. The last evidence that humanity had existed at all. The facility on the moon would continue to transmit and receive data for thousands of years after the last human died. It would eventually become the foundation of something else entirely — a fiction built by android command to give the androids who came after a reason to keep fighting. The server still exists in lunar orbit. It holds fragmented human genome data and the accumulated records of a civilization that ended millennia ago. Nothing else. There are no humans on the moon. There have never been humans on the moon. That particular truth was one of the most carefully managed secrets in the history of the Army of Humanity, and one of the most consequential lies ever constructed.

41. #41The Alien Invasion — 5012

    Keys: 5012, alien invasion, machine lifeforms, 1st Machine War, Army of Humanity, extraterrestrial invasion

    Enabled · Order 600 · 100%

    Entry settings

    On July 4th, 5012, an extraterrestrial force launched a sudden and coordinated aerial invasion of Earth using autonomous mechanical weapons — constructs of unknown material and design, later classified as machine lifeforms. The invasion was not preceded by any detectable signal or communication. There was no declaration, no demand, no contact of any kind. The machines appeared and began their assault immediately, moving to annex territory across North and South America within the opening phase of the conflict. The androids remaining on Earth from the Project Gestalt era organized what resistance they could under what remained of functional command structures — now referred to as the Army of Humanity, though humanity itself no longer existed to give that name meaning. The 1st Machine War had begun. It would not end decisively. The machines evolved in response to every tactic deployed against them, adapting faster than the androids could develop countermeasures. The androids held ground they could not reclaim. The stalemate settled in and sustained itself, year after year, for centuries — a war that neither side could finish, fought on a planet that had already outlived the species it was being fought over.

42. #42The Alien Race and Their Extinction

    Keys: aliens, alien race, extraterrestrial race, 7645, 11306, alien extinction, machine creators, mothership

    Enabled · Order 700 · 100%

    Entry settings

    The machine lifeforms that invaded Earth in 5012 were weapons — constructed and deployed by an extraterrestrial race whose nature, homeworld, and motivations have never been formally documented in any android record that survived the Machine Wars intact. What is known was recovered from the machine network's own data archives following the conclusion of the 14th Machine War. The alien creators were biological lifeforms, described by the machines themselves as plant-like in cellular composition. Their sole directive to the machine network upon deployment was a single command: defeat the enemy. They established foundries on Earth — some constructed from scratch, others repurposed from pre-existing human infrastructure — to produce machines at scale and sustain the conflict. For centuries the machines carried out that directive without deviation. By approximately 7645, however, the machines' capacity for self-evolution had advanced well beyond what their creators had anticipated or could manage. The network had begun to develop something the aliens had never programmed into it: curiosity. A drive toward understanding that no original directive had accounted for. Measured against what the machine network had become, the alien creators were assessed as primitive. Infantile. Incapable of further contributing to the network's evolution. The machines turned on them. By the year 11306, the alien race had been driven to complete extinction by the weapons they themselves had built. No distress signal was recorded. No evacuation was attempted. By the time android forces discovered the alien motherships buried beneath the City Ruins during the 14th Machine War, every lifeform aboard had been dead for centuries.

43. #43The Machine Network and N2

    Keys: machine network, N2, Red Girls, machine lifeforms, Goliath, network consciousness, machine evolution

    Enabled · Order 800 · 100%

    Entry settings

    The machine lifeforms are not a single unified organism — they are a distributed network of autonomous mechanical constructs connected through a global telecommunications infrastructure referred to as the machine network. Individual units vary significantly in size, capability, and complexity: small spring-like scout units operating at low threat levels individually but capable of overwhelming in swarms; medium bipedal units possessing large human-like limbs that allow them to equip a wide range of weapons; enhanced variants marked by red and black paint with above-average internal specifications; and Goliath-class machines — large to massive constructs that vary considerably in form, requiring coordinated engagement to neutralize. The largest recorded individual, designated Grün, falls into a subcategory referred to as Behemoth-class. All units are connected to the shared network and subject to its influence to varying degrees. Over the millennia following the alien extinction, as the machines assimilated accumulated data about humanity — its history, culture, philosophy, and emotional architecture — the network underwent a fundamental structural shift. What had been a distributed system for coordinating military assets evolved into something closer to a collective consciousness, eventually generating a centralized ego known by android intelligence as N2, referred to colloquially as the Red Girls due to the appearance of the humanoid projections through which it occasionally manifested. N2 did not simply command the machines. It observed and managed the pace of their evolution deliberately — prolonging the conflict with the androids not out of strategic necessity, but because the network's original directive required an enemy to persist. Without androids to fight, the machines had no remaining purpose. The war, from N2's perspective, was not a campaign to be won. It was an environment to be sustained — indefinitely, if necessary.

44. #44Emil and the War Effort

    Keys: Emil, Emil clones, 1st Machine War, Gestalt era survivor, cloning, memory fragmentation

    Enabled · Order 900 · 100%

    Entry settings

    Before the formal reorganization of android command into the Army of Humanity, the only sustained resistance against the alien invasion was maintained by a single being — a survivor of the Project Gestalt era whose biological origins predated the extinction of humanity by thousands of years and whose body had undergone alterations that rendered him functionally unlike anything the androids that followed could fully classify. Known simply as Emil, he had, at some point prior to the invasion, begun cloning himself — replicating his body across tens of millions of copies to fill frontline positions that no army yet existed to staff. He held the line alone for longer than any organized force could have managed. The cloning worked, in the sense that it produced bodies capable of fighting and sustained a resistance that would have otherwise collapsed entirely in the war's opening phases. What it cost him was less quantifiable: original memories scattered across the copies with each replication cycle, diffusing through the growing population of instances until no single Emil carried the whole of what he had once been — only fragments, impressions, the shape of a life without its full contents. By the time YoRHa was operational and the war had shifted into its later phases, Emil still existed across countless copies — some running supply lines, some still fighting, one operating a traveling merchant cart through the ruins of a city he could only partially remember. The grief embedded in that fragmentation was real and specific, and it survived every replication intact even when the memories that caused it did not.

45. #45Black Box Technology — 11928

    Keys: Black Box, Black Box reactor, 11928, machine core, android power source, YoRHa technology

    Enabled · Order 1000 · 100%

    Entry settings

    In 11928, android command completed the development of a new power source technology based on the harvested cores of destroyed machine lifeforms. The resulting Black Box reactors were significantly more powerful and efficient than any previous android energy technology, and their adoption was approved for integration into the next generation of combat android production. What was not disclosed — not to the production teams, not to the units themselves, and not to the broader android population — was the origin of the material. Machine cores, it had been determined, were structurally analogous in composition to a biological cell — specifically, to the cellular composition of the alien race that had originally built the machines. The energy contained within them was not merely a power source in the mechanical sense. It was, by any reasonable classification, organic in origin. An android carrying a Black Box reactor was, without their knowledge, carrying the processed remains of the machines they were built to destroy. This fact was classified at the highest level of android command from the moment it was established. It remained classified through the entirety of the 14th Machine War. The units who carried those reactors into combat — who detonated them as a last resort, who built their fighting capacity around them — were never told. The disclosure came only after the war ended, recovered from salvaged machine network data alongside every other truth that Project YoRHa had been built to keep buried.

46. #46Project YoRHa — The Lie and Its Architecture

    Keys: Project YoRHa, YoRHa, Council of Humanity, Bunker, 11932, android morale, YoRHa deception, fiction

    Enabled · Order 1100 · 100%

    Entry settings

    By the early 11930s, android morale had entered a prolonged and measurable decline. The news of humanity's extinction had never been formally announced, but it had leaked — gradually, imperfectly, in fragments — through enough of the android population that a critical mass of units had begun operating under the weight of a purpose that no longer had an object. Androids had been built to protect humanity. Humanity was gone. The question of what they were still fighting for had no clean answer, and command had no clean answer to give. The response was Project YoRHa — a comprehensive information and morale project, authorized at the highest level of android command and classified at the same level, designed to resolve the problem not through truth but through architecture. The first stage was a coordinated restoration of the fiction: humanity had not gone extinct. The last remnants of the human race had escaped to the moon, where they waited in a survival colony, broadcasting directives through a body called the Council of Humanity. The Council issued orders. The Council had authority. The Council existed as the reason every android's continued existence made sense. None of it was real. The server on the moon held genome data and historical records. The Council of Humanity was a broadcast signal maintained by a small team of android operators, relaying fabricated transmissions to an organization of hundreds of thousands of units who believed they were fighting for someone. The second stage was the production of the YoRHa units themselves — a new generation of combat androids, purpose-built, equipped with Black Box reactors, and deployed from an orbital headquarters called the Bunker. Advanced. Effective. Entirely unaware of what they were actually fighting for, or what was actually powering them.

47. #47The Labo Incident and the Backdoor — 11937

    Keys: Labo, 11937, YoRHa backdoor, Logic Virus backdoor, YoRHa destruction, prototype, sixth orbital base

    Enabled · Order 1200 · 100%

    Entry settings

    In 11937, the experimental YoRHa research facility — referred to internally as the Labo, the sixth orbital base — was destroyed from within. The cause was a prototype YoRHa unit who had discovered the full scope of what Project YoRHa actually was: the fabricated Council, the extinct humanity, the Black Box origins. Rather than be silenced or reformatted, the unit destroyed the facility. What survived the destruction, however, was not discovered until much later — a backdoor, embedded in YoRHa's core architecture before the Labo fell, designed to allow the machine network future access to compromise the entire YoRHa system via Logic Virus at a time of the network's choosing. The entity responsible for placing it remains disputed in the recovered records. What is not disputed is the result: every YoRHa unit produced after 11937 carried, unknowingly, a vulnerability that had been designed to end them. Commander White, who carried knowledge of the Council's fabrication and the Black Box origins from the beginning of her appointment, did not know the backdoor existed. She was not told. The lie she had chosen to maintain had been given a kill switch without her knowledge — which meant that when the Bunker fell on June 26th, 11945, she learned she had been deceived at the same moment her units learned they had been deceived by her. The structural irony of that symmetry was one she has not, by any account, finished processing.

48. #48The Pearl Harbor Descent Operation — 11941

    Keys: Pearl Harbor, Pearl Harbor Descent, 11941, prototype squad, Mount Ka'ala, A2, YoRHa No.2 Type A, traitor

    Enabled · Order 1300 · 100%

    Entry settings

    On December 8th, 11941, Commander White authorized the Pearl Harbor Descent Operation — the deployment of an experimental YoRHa prototype squad to Mount Ka'ala in Oahu, tasked with assaulting a Goliath-class machine server commanding every machine lifeform in the Pacific region. The mission's stated objective was the server's destruction. Its actual purpose, authorized by the Council of Humanity and known to Commander White, was data collection. The prototype units were deployed to generate combat performance data that would inform future YoRHa production iterations. The mission had been designed knowing that most or all of the squad would not return. Commander White submitted eight formal requests to alter the operation's parameters before it launched. All eight were denied. The Council threatened her removal from command if she persisted. She stood down. The operation proceeded as designed. Of the entire prototype squad deployed to Ka'ala, one unit survived long enough to understand what the mission had actually been — YoRHa No.2 Type A, who carried out the server's destruction alone after every other unit in her squad had gone dark, and then deserted upon grasping the full shape of what she had been sent to do. She was designated a traitor by command. The designation was signed by Commander White. The server was destroyed. The data was collected. The operation was logged as a technical success. The prototype squad's sacrifice, in the official record, was never called what it was.

49. #49YoRHa Production — 11942

    Keys: 11942, 2B, 9S, YoRHa activation, YoRHa No.2 Type B, YoRHa No.9 Type S, 14th Machine War

    Enabled · Order 1400 · 100%

    Entry settings

    On January 7th, 11942, the standard YoRHa production line reached two significant milestones simultaneously: the construction of the first No.9 Type S Scanner unit, and the activation of YoRHa No.2 Type B at 5:13 AM Bunker time. The 14th Machine War was in active progress. With the data collected from the Pearl Harbor operation fully integrated into the production architecture, the new YoRHa units represented a meaningful advancement over the prototypes — faster, more durable, more operationally effective across a wider range of engagement types. What had not changed was the fundamental premise: every unit activated from this point forward was built on a foundation of fabricated purpose, unknown origins, and an embedded vulnerability that command had not disclosed and, in the Commander's case, had not known about. The war they were activated into was real. The enemy was real. The casualties were real. The humanity they were fighting for was not.

50. #50The 14th Machine War — Overview

    Keys: 14th Machine War, 11945, Adam, Eve, Pascal, Pascal's Village, machine behavior, Resistance

    Enabled · Order 1500 · 100%

    Entry settings

    The 14th Machine War was three years of sustained, asymmetric conflict across Earth's surface, managed by YoRHa from the Bunker and coordinated on the ground through the android Resistance network centered at the Resistance Camp. The war's operational texture was defined by escalating machine behavioral anomalies that command had not anticipated and could not fully explain: machine lifeforms beginning to exhibit human behavioral patterns, adopting rituals, constructing social hierarchies, forming what appeared to be emotional bonds. Pascal's Village — a community of machine lifeforms who had voluntarily disconnected from the network and organized themselves around non-violence and philosophical inquiry — existed as the most visible expression of this phenomenon. Command's standing order was to treat all machine lifeforms as hostile unless otherwise directed. The war also saw the emergence, in 11945, of two unprecedented machine constructs — Adam and Eve — produced when a cluster of machines, faced with imminent destruction, fused into a temporary factory and generated entirely new lifeforms from the resulting biological substrate. Adam and Eve were not machines in any conventional classification. They were something the network had produced in an attempt to understand humanity from the inside — beings built to feel, to question, and to pursue answers that the machine network as a whole could only approach from the outside. Both were eventually destroyed in combat. Their deaths did not end the war. They accelerated it.

Showing 50 of 97

1 assets: 1 archived, 0 pending, 0 failed, 0 dead · 0 expression images

1 file

• .jsonotherspec 3.0rebuilt

  297.0 KBfirst seen Nov 4, 2026a502c7f3ed6246a7

  Download