Optional M.D. injury and near-fatal survival subsystem

[StreamDemon]

Goal

Implement the optional near-fatal Mega-Damage survival rules only after Issue #51 establishes deterministic core M.D.C. combat and death outcomes.

Rendered source

Rifts Ultimate Edition pp.358-359, especially:

• Surviving Mega-Damage Attacks;
• Beating the Odds;
• First, Determine the Mega-Damage; and
• Second, Immediate Medical Attention Required!.

Re-render and transcribe the complete optional procedure before design. Do not infer injury results or medical timing from remembered Palladium rules.

Intended scope

• Explicit opt-in policy for the optional subsystem.
• Eligibility rules, including the printed called-shot-to-the-head exclusion.
• Hit-location and catastrophic-injury determination.
• Limb loss, internal-organ damage, scarring, bionic reconstruction needs, and other lasting consequences.
• Immediate treatment deadline and qualifying medical, psychic, or magical care.
• First stabilization check, follow-up surgical check, treatment duration, and failure outcomes.
• Coma, stabilization, survival, death, and recovery-state persistence.
• The printed near-death trauma/insanity procedure.
• Pure deterministic rules with every roll and elapsed duration supplied as inputs.
• Atomic backend persistence and a live SolidJS treatment/injury presentation.
• Compatibility with Issue Full M.D.C. combat: tier interaction, armor ablation, and unprotected outcomes #51 combat history and fatal routes.

Dependencies and boundaries

• Depends on Full M.D.C. combat: tier interaction, armor ablation, and unprotected outcomes #51.
• This is a concrete rules subsystem that may later inform Generic page-stamped rules effect pipeline #53, but must not wait for or prematurely implement the generic effect pipeline.
• Called shots are included only where the optional survival eligibility rule requires them; a general called-shot combat system should be separately designed or linked if one exists.
• No invented anatomy, prosthetic catalog, medical economy, or generalized condition engine.

Delivery requirements

• Page-stamped content and contradiction-rejecting schemas.
• Printed-value tests for every table range, deadline, roll, and outcome.
• Write-time rederivation so illegal or stale treatment states cannot be stored.
• Live-browser verification of injury creation, stabilization, surgery, route changes, and late-result ownership.