Follow

Campaign contracts and continuity

Public edition ·

Status

Owner direction recorded; detailed objective contracts and outcome thresholds are proposals. Review prototype only; no game runtime implementation.

Owner direction

Use protected access through Czechoslovakia to occupied Austria as the occupation pretext.

Win campaigns through specific capture/defence objectives, not accumulated victory points.

Produce graded narrative epilogues and carry actual faction/campaign results into chronologically later intros.

Summer Decision centres on the Fulda operational axis: a Soviet offensive toward Frankfurt or a coordinated Allied offensive eastward, according to the saved spring state.

Summer attack rationale changes with the complete spring history, including defeats and deliberate branch exploration. Soviet commander selection was subsequently resolved as Rokossovsky overall and Konev for summer; Zhukov is not the default.

Adopt Rokossovsky as overall German-theatre commander and Konev as commander of its summer operation. An Allied-led eastward Fulda offensive under one combined commander is a full branch when spring outcomes and readiness support it.

6 November 2026: ICNA versus CSLA replaces prior national naming. Communist guerrillas can activate on deeper US occupation of Bohemia, earlier on German combat entry. German partisan activity under Soviet advance is low in this campaign; Czech forces have limited incentive for deep Bavarian occupation. Quantitative rules remain proposals.

Strategy
Default

The Soviet Bohemian Group uses the authored campaign allocations.

Pretext

Additional protected transit to Austria: rail priority, depots, junction guards and communications. Expand coercive access into control of Prague and a western concentration.

Historical limit

The January 1946 precedent concerns Hungary. Czechoslovak application is fiction; Austria has other supply routes. Transit does not by itself explain a west-Bohemian invasion force.

Research gate
Objective contract
Identity

Stable objective ID, name, map region/bridge/railhead and geographic footprint.

Control

Owner, contested state and minimum garrison; scouting or a momentary crossing is not capture.

Completion

Capture or defend until the defined operational deadline, secure connected supply/exit route where required, and retain specified installations in usable condition.

Termination

Primary objective package secured for the authored confirmation interval; deadline; surrender; destruction/withdrawal that makes further resistance impossible. Resolve both sides simultaneously.

Grade

Judge essential objectives first, secondary achievements second, operational cost separately. No hidden sum of kill points may overturn required objectives.

Cost

Track casualties, irreplaceable equipment, readiness and ability to continue. Pyrrhic is an outcome cost, not a euphemism for defeat.

Exhaustion

If all opposition is eliminated and no reinforcement can arrive in time, resolve reachable occupation and remaining objectives without an empty-map grind. Do not award unreachable or destroyed objectives automatically.

Deadlines

Narrative operational limits must be stated in advance; time limits cannot secretly cancel a completed victory.

Stalemate

If neither faction secures its package, use an indecisive ending; never manufacture a victor from score.

Territorial control
Campaigns
First Orders
Helmstedt Corridor
Bavarian Front
Northern Front
Summer Decision
Outcomes
Major victory
Minor victory
Pyrrhic victory
Minor defeat
Major defeat
Indecisive
Pyrrhic defeat

Store result and cost separately for both factions. A losing player may have inflicted a pyrrhic victory on the enemy; the epilogue should say so. Do not assume a minor defeat always equals the opponent’s major victory.

Epilogue slides
The ground
The cost
The next operation
World state
Operation
Territory
Forces
Politics
Results
Narrative
Continuity rules

Compute results once from the final world state; prose may not change the outcome.

Apply only events completed before the next intro’s date; overlapping campaigns consume dated events, not each other’s future final result.

Keep one persistent world per linked run. Switching faction changes viewpoint on that world, not which contradictory ending is canon. Separate standalone runs do not merge automatically.

Standalone campaigns use an explicitly chosen scenario history or imported linked save. Do not call an unplayed assumed defeat the player’s result.

Destroyed formations cannot reappear intact. Reconstitution requires a dated replacement/reorganisation event with equipment, manpower, time and a revised strength.

Cross-campaign map positions, available units, supply routes and objectives change with the same state that writes the narration.

If the final state makes a scripted later battle impossible, choose a compatible operation, substitute a board or omit it. Never silently erase a victory.

Coalition availability follows the established saved conditions; a victory label alone does not conjure ready German, Polish, French or Free Czechoslovak forces.

Historian voice remains dispassionate; intros contain military facts and intentions, not grade names, deck rules or score explanations.

No result-bearing clause may be played without a matching predicate. Neutral fallback may omit an unknown fact but may not contradict one.

Political rupture does not recolour an entire division automatically. Resolve battalion obedience and actual transfers without duplicating strength; later election results are not available before their date.

Chronology

First Orders is nested in Helmstedt. Southern and Northern may overlap; resolve their exact dates before allowing dependencies. Summer consumes the dated outcomes of completed spring operations. The war begins 16 April 1946; do not confuse that with every campaign’s opening.

Intro variants
Entry 1
Entry 2
Entry 3
Entry 4
Entry 5
Acceptance cases

All Soviet counters destroyed at Helmstedt: no later Allied-loss clause, no surviving duplicate Soviet unit; new threat requires a sourced new force.

Allied pyrrhic victory: ground retained, losses carried, victory acknowledged, no invented rout.

Soviet victory: Western loss and Soviet control persist in both faction viewpoints.

Contested deadline: indecisive outcome if neither primary package complete.

Overlapping north/south: future events cannot enter an earlier intro.

Successful intact-unit defection: one persistent unit changes side, no copied battalion.

Destroyed bridge: physical capture alone cannot satisfy an intact-crossing objective.

Enemy eliminated but unreachable target remains: resolve realistic movement/capture; do not teleport ownership.

Previous deep advance invalidates summer defensive board: choose compatible branch rather than resetting to April.

Standalone start: declared assumed history does not overwrite a linked-run save.

Allied wins in every spring operation: describe Soviet recovery/counterstroke only when funded forces and approach routes permit it; never claim prior Allied defeat.

Soviet wins across spring: exploitation may seek a finishing blow, but victory grades do not automatically establish Allied collapse or a usable Fulda route.

Mixed north/south results: preserve both outcomes and derive the summer opportunity from actual geography, not the majority of wins.

Pyrrhic winner versus intact defeated formation: retain ground and model the recorded relative readiness; do not swap result labels.

Player accepts or deliberately engineers defeat: persist the real result and losses without inventing the player’s intention or awarding free recovery troops.

Player restarts a campaign: no later event may remain attached to an overwritten predecessor; replay/save policy is pending implementation.

One or both forces cannot support the planned offensive: select a feasible alternative and truthful narration rather than forcing baseline Fulda.

Commander identity is changed: captions, narration, appointments, hierarchy and scene markers use the same selected identity; no residual Zhukov default.

Allied spring successes plus a funded concentration: generate the eastward Allied offensive with Konev defending; no residual claim that he opened the battle by attacking west.

Allied nominal wins but exhausted forces: do not grant an offensive merely from result labels; preserve the world and select a feasible operation.

Soviet theatre view shows one Rokossovsky command; the north has a distinct subordinate HQ and commander slot, while Konev leads the summer assigned force.

Combined Allied offensive: assigned British and American troops follow one operational command without duplicating their national parent forces.

Switching initiative changes objectives, defensive works, reserves, supply and initial placements alongside the narration; reversed arrows alone fail acceptance.

Sources
Dunn memorandum, 18 January 1946
Implementation status

Only design records, research correction and a private review prototype changed. Runtime persistence, objective evaluator, branching cinematics and save migration remain to be implemented after contracts are settled.

Authority

Game Bible Book III and this register; amend in place

Summer rationale
Status

Owner-adopted variable initiative and command roles; narrative families and exact selection conditions are design, not an implemented evaluator

Principle

The linked summer campaign consumes the full saved spring record. Both victories and defeats, including deliberately accepted defeats, are valid. Player intent is not inferred; only recorded actions and outcomes are narrated. Determine which side holds the initiative before selecting its rationale. Summer is not inherently a Soviet attack.

Inputs
Families
Selection order
Coverage

Every valid history must have a compatible operation and a truthful fallback. Enumerate all supported prior-outcome combinations, then cover geographic, force, logistics, allegiance and chronology boundary cases. Outcome combinations alone are not exhaustive world-state coverage.

Restarts

Proposed: a restart forks from the pre-campaign checkpoint and invalidates later dependent results in that branch. Preserve the abandoned run separately; never combine its losses, gains or unlocks with the replay. Final save UI/ironman policy remains open.

Scenario access

Proposed: offer alternate starting histories in standalone scenario selection so players can explore branches without intentionally losing a linked run. Assumed histories must be labelled and must not overwrite linked progress.

Anti exploit

A recorded defeat keeps its actual costs. A different later mission is not an automatic grant of superior troops, replacements or political support.

Command reference

forces.json: command_structure

Prewar escalation
Status

Owner-directed escalation and Czechoslovak civil-war framework; specific motives, sequence windows and orders remain working proposals

General war outbreak

1946-04-16

Historical baseline rule

Use historical disbandments and postings as comparisons; credible prior crisis decisions may delay them. Record effective dates and actual retained strengths.

Proposed sequence
Belief and response

Proposed Soviet overconfidence confuses domestic Communist strength and wartime gratitude with consent to renewed foreign military control. That coercion can alienate otherwise friendly or neutral citizens.

Chronology guards
Open decisions
Sources
Adopted political direction

See forces.json czechoslovak_political_settlement: Beneš civilian authority in US Bavaria; Democratic Independent Czechoslovak National Army (ICNA); Communist-backed Prague authority; separate German rearmament under American control.

Retained formation reference

forces.json/retained_formation_ledger; adopted theatre identities, no automatic opening stock

Bohemian resistance
Date

2026-11-06

Status

Asymmetric resistance direction adopted; numerical triggers, caps and effects proposed, not implemented.

Political boundary

Communist networks are a minority organized actor, not a synonym for Czech civilians or all anti-German resistance. Nationality/ethnicity alone does not assign allegiance.

Opening
Unit profile

forces.json/czechoslovak_force_design/templates/communist-cell

Triggers
Activation constraints
Operational effect proposal
Opposite direction
Acceptance cases
Implementation status

No runtime spawn, infiltration, occupation, TO&E migration or linked-world behavior changed.

French participation contract
Reference

forces.json/french_southern_toe

Milestones

Amberg, Regensburg and Cham–Furth supplied and usable for two complete campaign turns; open Nuremberg supply and French entry route. National authorization unlocks six formations; each complete formation costs its own RP and arrives next own turn.

Status

Authored conditions; current dossier/review contract, not a playable Bavarian campaign.

Formation requisitions

forces.json / formation_requisitions: 32 independently requisitionable complete formations under parent divisions/groups; tactical units are their finite roster.

Berlin exploration
Status

Historical feasibility baseline retained; city-services/RTS systems now owner-adopted. Dated OOB and implementation remain unapproved.

Research reference

forces.json/berlin_feasibility_research

Book reference

books/03-campaigns.md#berlin-feasibility-study-6-november-2026

Source reference

sources.json/berlin

Existing campaign transfer authorizations
Rules reference

berlin_command_rules

Berlin command rules
Recorded

2026-11-06

Status

Owner-adopted design rules; not implemented. Exact dated scenario, OOB, numerical tuning and release scope remain unresolved.

Working title

Omega War: Berlin Command

Title status

Owner selected Berlin Command. Placement under Unthinkable, full product-title styling and commercial packaging remain open.

Format

Berlin and immediate surrounding area operational campaign with persistent civilian services and RTS engagements; supports a self-contained campaign without assuming linked-world transfers.

Historical setting

Fictional 1946 war; established general outbreak remains 16 April. Exact Berlin opening and duration require scenario authorship.

Scope

Adopts the systems and conditional assistance families discussed by the owner; allocates no formations, equipment, aircraft, shipping or new national commitments.

Rules
Open before implementation
Implementation status

Design/data documentation only; no runtime, production media, showcase or public release.

Book reference

books/04-operational-rules.md#berlin-command-city-services-and-combat

Research reference

forces.json/berlin_feasibility_research

Name

Berlin Command