Permadeath
The useful distinction is between the announced idea and the missing implementation detail. Injury implies a consequence that can persist; permanent loss implies that at least some outcomes can remove an operative from the campaign. Neither phrase tells us the exact trigger, whether every difficulty uses the same rules, how recovery time is calculated, or whether story-critical characters receive special handling.
Its composition makes the cost of exposure easy to imagine: each unit stands in a distinct lane and a mistake could isolate one member of the team. The still does not display an injury panel, casualty result, recovery timer, or difficulty option, so it illustrates battlefield risk without proving how permadeath is resolved.
It does not support a particular percentage chance, a fixed number of wounds, automatic save restrictions, or the claim that every downed operative is immediately lost forever.
Injury Management
Injury management changes how a sensible player evaluates a turn. Damage to one operative may affect more than the current objective if that character can become unavailable or vulnerable later. Preserving the squad can be strategically stronger than taking a flashy shot that leaves somebody exposed.
That principle does not require pretending to know the final medical system. A practical first-campaign rule is simply to keep escape routes open, avoid spending every resource before the enemy response, and treat an injured operative as a campaign asset rather than disposable damage.
Information shown after a mission will matter more than genre habit. If the game presents a recovery estimate, availability warning, or permanent-loss prompt, use that language exactly. If it offers a difficulty modifier, read the modifier rather than assuming that a familiar label such as normal or hard has the same casualty rules as another game.
A squad built around one irreplaceable role may carry more campaign risk than a roster with overlapping capabilities. Until the full systems are known, the conservative response is to develop alternatives and avoid plans that require the same operative in every mission. That is a planning consequence drawn from the stated stakes, not a claim about a confirmed bench size or recovery mechanic.
Roster Risk
Permanent loss gives roster composition emotional and tactical weight. A turn is no longer only a puzzle about maximum damage; it can become a judgment about whether an objective is worth risking a developed operative. Retreating from a poor lane, protecting a wounded specialist, or using a safer ability sequence may preserve options for later operations.
The correct choice will depend on information the game actually exposes. Threat ranges, cover, remaining actions, current health, and objective pressure are relevant battlefield observations. An imagined hidden death roll is not. Players can act carefully without inventing mechanics: identify who is exposed, ask whether another operative can cover the same task, and leave enough flexibility to respond when the enemy turn changes the position.
Roster attachment also affects whether permadeath is desirable. Some players enjoy a campaign that produces personal stories through survival and loss; others dislike having hours of development erased. The preview wording confirms that loss belongs in the conversation, but it does not settle how frequently it occurs or how much control a player has over it.
Do not confuse a customizable squad with an unlimited supply of replacements. Those unknowns are precisely why roster advice should remain conditional before release.
Death System Boundaries
It does not define a universal number of injuries before death, list every recovery route, explain whether casualty rules vary by difficulty, or state how every narrative branch reacts to a fallen operative. It also does not establish an ironman save mode.
That boundary matters because each missing detail changes the severity of the system. Frequent wounds with generous recovery create different pressure from rare but irreversible losses. Optional permadeath would serve a different audience from a rule enforced across every preset. A rescue state is not the same as immediate removal. Until those distinctions are documented, they should remain questions rather than being filled with conventions borrowed from XCOM or other squad tactics games.
For launch-day verification, check the difficulty descriptions, tutorial wording, post-mission injury screen, and any save-mode options in the actual build. Reviews are useful only when they identify the version and explain the rule they observed. A dramatic trailer shot or a reviewer saying that a mission felt punishing cannot establish the underlying thresholds.
That makes survival, positioning, and roster resilience relevant. Keeping those two sentences separate gives players a usable expectation without turning incomplete preview detail into a false manual.