“Corrupted Golems” appears as a label in Game Informer’s 90-minute Beast of Reincarnation preview. That is useful evidence that the preview author encountered enemies described that way, but it is not yet a complete first-party taxonomy. The public English build must confirm whether Golem is the canonical game term, whether “Corrupted” is a variant name, and how these beings relate to malefacts, Nushi, and the Blight.
This distinction keeps an attributed preview observation from becoming unsupported lore through repetition.
Preserve the source level of the name
Before launch, cite “Corrupted Golem” as preview terminology. After unlock, look for a bestiary title, enemy nameplate, objective, subtitle, archive, or official caption. Record spelling and capitalization exactly. If the game uses another English name, retain the preview label only as historical context.
Do not identify a creature in a trailer by visual resemblance alone. Stone, metal, wood, vines, or a large humanoid shape can describe appearance without settling classification.
Distinguish object, creature, and class
The word golem often carries expectations from fantasy, but another game’s tradition is not evidence here. The release story should establish whether these entities are constructed, grown, transformed, autonomous, controlled, or something else. Record who gives the explanation and when.
Likewise, “corrupted” could describe a state, variant, faction term, or preview shorthand. Do not use it to assert an uncorrupted base form until one is named or shown by the game.
Build the first canonical entry
Capture the entity’s in-game name, first region and landmark, story state, visible traits, attack families, health and Down display, reward, and any archive text. Put combat values behind difficulty and version scope. A route belongs on the world pages; a detailed solution belongs in combat.
If several models share one bestiary entry, note variants without creating artificial species. If the bestiary separates them, preserve those entries and identify what the UI says distinguishes them.
Test the Blight relationship
Beast of Reincarnation’s environments and threats are shaped by the Blight, but visible growth does not prove origin or control. Look for dialogue, archives, transformation scenes, or entity descriptions that connect a Golem to the Blight. Preserve theories as theories when a character speaks uncertainly.
The same caution applies to malefacts. Whether Golems are malefacts, a subgroup, enemies affected by them, or unrelated is unresolved until taxonomy evidence exists. Avoid a hierarchy chart built from search snippets.
Record behavior without assigning motive
Attack animations, patrols, reactions to Emma, and vulnerability to Down are observable. Purpose, loyalty, intelligence, and emotional state are narrative claims. Describe what happened, then attach any explanation the game provides.
Koo’s threat alert, observed in the same preview coverage, may identify nearby danger but does not reveal the entity’s nature. A warning cue should stay a gameplay observation.
Separate ordinary and boss-scale forms
A large or durable Golem is not automatically a Nushi. Use title cards, reward screens, objectives, and Koo’s captured-power sequence to identify major encounters. If a named Golem becomes a boss, give it a spoiler-controlled character or Nushi entry while keeping the general class here.
Do not count phase transformations as separate species unless the game does. State inclusion criteria before publishing a total.
Track localization and updates
Steam lists 11 interface/subtitle languages, so entity terminology can vary across localized builds. English is the source locale for this page. Do not translate a fan-rendered Japanese term back into English when the official English UI supplies one.
If a patch corrects a bestiary label, preserve the older wording as a versioned alias and update the canonical heading. Combat balance changes should not be described as lore changes unless the text also changes.
Evidence statement
The specific Corrupted Golem wording is attributed to Game Informer’s hands-on preview, not promoted to an official full roster. The transformed-world context comes from the Steam Store and official Developer_Direct article. No first-party pre-launch source reviewed here established Golem origin, variants, hierarchy, or canonical count.