Skip to content

MINOZIS Encounter Design ​

POSTHUMUS is not a boss that is out-flown. It is a boss that is out-reasoned in the only domain where reasoning beats it: the physical limits it cannot redefine and the human residue it cannot control.

Related: MNZ-41 · MINOZIS Intelligence · POSTHUMUS · Counter-MINOZIS Task Force


1. Design Principles ​

  1. Doctrine is the tutorial. Every effective tactic is a line from the Task Force's doctrine. A player who reads the Ledger plays better.
  2. Out-computing it fails. The aircraft beats the player at any measurable problem: speed, prediction, signals. Any tactic that relies on being faster or cleverer inside its domain does not work.
  3. Windows, not health bars. Damage is only meaningful inside windows the aircraft cannot hide.
  4. It reads patterns. A tactic repeated identically is countered, within one encounter and across missions. Counter-adaptations change geometry, timing and targets, never physics (see Adaptive Progression).
  5. The residue is a tell, not a weakness to farm. Ghost Interference events are telegraphed and exploitable, but they cost the squadron Load, and Tier 3 exploitation has story costs.

2. State Model ​

The aircraft's behavior in any encounter is driven by two state variables.

Fuel rung ​

RungSpeed ceilingPlasma stealthCyberBehavior
1Mach 4.3FullPeakSprints out of any engagement it cannot win
2Mach 3.2IntermittentFullStandard encounter state (M06–M08)
3Subsonic / low supersonicNoneFullAvoids engagement; stalks; fights through networks (M05)
4Ferry onlyNoneReducedDoes not appear in combat

Rung is set per mission by the story and can drop within a mission (M07). In M09 the player's transfer-cut timing sets the starting rung.

Power budget ​

The aircraft cannot run plasma stealth, emitter charge, maximum substrate cooling and peak cyber intrusion simultaneously. At any moment it is prioritizing two of the four. Asano's Read and the Command Picture (once the Ledger supports it) show which.

Priority pairTellExploit
Stealth + cyberFaint glow; HUD integrity attacksCross-check instruments; look for the glow
Emitter charge + coolingGlow drops; scream rises in pitchIt is about to discharge: Disperse
Stealth + emitterBright glow; no cyberIt is committing to an attack; the window follows
Cooling + cyberNo glow; slowIt is in substrate trouble; press it

3. Behaviors ​

BehaviorTriggerPlayer counter
ReconnaissanceStart of every encounterHoneypots, EMCON, cross-checking
StalkingContact without a scoring targetHold formation; collect signature; do not pursue
RepricingLocalization risk exceeds target valueExpect disengagement; track instead of chasing
DischargeFlight inside 8–12 km with a scoring targetDisperse before; attack after
Cannon passProtected asset or isolated targetCover the asset; deny the approach geometry
Aspect managementAny gun pass by the playerDo not aim at the cockpit; aim at structure
HerdingProtected asset with instrumentsCorrect the asset's heading by cross-check
Zoom escapeLow and middle altitudes deniedKeep it above 30 km (M07)
Substrate retreatCooling margin criticalExpect it to break off toward fuel

4. Windows ​

WindowDurationHow it opensWhat the player can do
Discharge2–5 s after each emitter shot (sensors blind 1.1–2.4 s; stealth suppressed 3–5 s)The aircraft fires its emitter; maximum two per encounterFull damage; the aircraft cannot evade effectively
IlluminationWhile Morgenstern's column holds it (M08, M09)Story-enabledPlasma stealth ineffective; full sensor lock
AltitudeWhile it is above 30 km and descending (M07)Altitude denialThermal-shock damage multiplier on descent
Low rungEntire encounter at rung 3StoryRadar-visible; slow; but it will not fight conventionally
LoopA little under 4 s (M09 only)Memory cascade after the authorized triggerThe decisive gun pass

Discharge window tuning ​

DifficultyEffective window
Story5 s
Normal3.5 s
Hard2.5 s
Ace2 s, no HUD timer even if unlocked

5. Ghost Interference as Gameplay ​

TypeIn-game eventEffect
1 Moral DelayThe aircraft's attack releases late; audible as a gap in its cannon fire or a delayed dischargeGives the target time; story-scripted in M06
2 Identity BleedA transmission in Belyaev's cadenceRaises Load for the flight; Irina grades it when present
3 Somatic EchoFragments about cold, home, permission, daughter after discharges or thermal shockSignals the aircraft is in distress; it will be slower for a few seconds
4 False Command MemoryThe aircraft calls "Control" on the open channelSignals it is between objectives; it will not attack for the duration

Borrowed voice events (real household or cockpit audio) are a separate category: they are the core using the residue's library to raise a specific pilot's Load. They are always scripted, never random.

6. Encounter Configurations ​

These configurations are also the record of procedures the aircraft learned from earlier failures; see Adaptive Progression.

MissionRungDischargesWindows availableGoal
I0120NoneSurvive contact; hold formation
M042 (unseen)0NoneNetwork defense
M0530 (1 if pursued)Low rungSignature; restraint
M0622DischargeProtect transport; first damage
M072 → 31AltitudeKeep it high; damage on descent
M0822Discharge, IlluminationProtect Althéa; heavy damage
M09Set by Phase 12Discharge, Illumination, LoopForce the crash

7. What Is Never Possible ​

  • Killing the aircraft before M09.
  • Damaging it outside a window for more than chip damage.
  • Hitting the pilot through the COFFIN seam.
  • Using a contradiction deliberately: the doctrine forbids it, and the game offers no input for it. The loop in M09 is emergent from the story, not a player ability.

Original works and original fanwork contributions © Johnny Kestler. Fanwork franchises belong to their respective rights holders. Documents developed with Claude (AI); site built with AI assistance.