Follow

Book VII Product implementation and production

Public edition ·

The Bible states intended game behaviour. Implementation status is supported by source inspection, dated test results and release evidence, each identified separately.

Product and platforms

The browser game is the main development line. The Windows desktop edition packages the shared browser game for offline use and local playtesting. Native mobile scope, source and validation are tracked separately; web parity requires platform-specific evidence.

Single-player tactical and operational play is the foundation. Standalone and campaign multiplayer rules are design work; their presence in the Bible does not establish shipped networking. Wider theatres and later-era equipment remain roadmap scope.

Commercial direction — approved November 2, 2026

Offer one complete introductory campaign free; its exact identity remains open. A permanent core purchase covers the defined core Unthinkable campaigns, skirmish and multiplayer when implemented. Publish the exact core campaign list before sale. Promised core scope remains in that purchase even when delivered later; substantial new theaters are separate paid expansions. Existing free access and saves stay intact. Fixes, balance, accessibility and improvements to shared systems remain free updates; do not sell competitive power.

EXPLe Arcade membership is the intended primary recurring revenue offer across the portfolio. Released expansions are included while membership is active, alongside permanent individual purchases. George confirmed membership also covers Omega's paid core campaigns, skirmish and multiplayer when implemented. Independent permanent core ownership survives membership expiry; paid base-app download rights are a separate open decision. Expiry/refunds remove only their own access source, preserving independent ownership and saves. Purchase origin is separate from the apps/content unlocked; use the shared account/entitlement service.

A battle pass is a future possibility only, with no approved product, rewards, season, price or implementation. Membership overlap needs an explicit later decision. No prices, release date, paid activation or shipped multiplayer are established by this direction. Shared commercial record: EXPLe handoff.

Implementation observations at consolidation

SystemObserved source or reportCurrent interpretation
Helmstedt boardsrc/data/campaigns/operational.ts13×9 schematic board, eight half-day turns; Brunswick is off-board.
Operational outcomesrc/campaign/rules.tsFinal landmark-VP comparison still exists; the new objective/result contract is not fully implemented here.
Finite establishmentssrc/data/campaigns/helmstedtForces.ts and helmstedtForcesV2.tsv3 establishment and preserved legacy stock; no free migration top-up.
Deckssrc/data/decks.ts45 AP and current category validation exist; values are tuning.
Refitsrc/campaign/refit.tsPolitical Points and finite survivor/refit rules exist; not a campaign victory score.
Movementsrc/campaign/movement.tsAP, supply, hostile control and route checks exist; enlarged-map scale needs validation.
Tactical systemsTransport, towing, urban, fieldwork, doctrine and intelligence reportsHistorical implementation evidence; no new full-game regression run in this consolidation.
CinematicsBible compiler, operational map painter and measured narrationFive introductions and six explicitly selected summer studies are in the current production pass; see current film delivery below. Saved-result selection remains unimplemented.
Ending prototypeArchived campaign-continuity reviewSeven fixtures passed in that review; it is not runtime linked-campaign implementation.
Other campaign dossiersReviewed map and roster proposalsPlanned content, not proof that all five strategic campaigns are playable.

Concurrent runtime/UI changes were left untouched during consolidation. Exact source paths and hashes in the evidence inventory describe the inspected state, not a commit or release claim.

Feature production contract

Each unit or feature needs its rule, data, model/animation, crew behaviour, weapon/ammunition, sound, interface, persistence and relevant tests to agree. Initial card integration does not complete an equipment family. Missing cards and national-release gates should reject materialisation rather than silently substituting another unit.

Use tests appropriate to the change. The repository’s quick suite is not the full release gate; full seeded battles and campaign continuation are required before shipping the relevant game changes. Platform-specific checks, hardware performance and visual/audio acceptance remain separate. Do not repeat unrelated tests merely to inflate a validation claim.

Maintain source attribution and licences. Keep state changes atomic. A failed save cannot consume a purchase or corrupt the current world. Preserve unrelated work and inspect changes before committing; the repository’s Git conventions still apply.

Direction (4 November 2026): temporary 3D models and animations. The game's current procedural 3D vehicle, gun and infantry models, and their animations, are temporary. FormSeed 3D model production works through Daisenjutsu's requests first. Omega War's FormSeed requests stay queued:

  • 22 request files covering 15 subjects in FormSeed Game Assets, awaiting reconciliation in issue #73;
  • the skinned-infantry need in FormSeed #60;
  • this repository's integration pilots, #6 and #8.

Until those resume, keep the temporary models functionally correct: gameplay geometry, mounts, crew clearance and muzzle parity. Do not invest in further visual polish unless the owner asks. The agreed request defaults for the replacement models (shared Daisenjutsu grounded-miniature style, parts-format conditions, qualified-package delivery) are in docs/formseed-model-treatment.md. 2D recognition and interface art continue independently. Showcase footage shows these temporary models.

Source of truth and exports

Edit docs/game-bible/ for game vision, lore, campaigns, rules, feature intent, presentation and roadmap decisions. Its books and structured registers form one framework. The private website is a generated view of these files.

The reading-view exporter is build-bible.py in the existing omega-campaign-storyboards-20261029 Site project. It reads this Bible directly, generates book/register pages and preserves the frozen archive. check-bible.cjs verifies navigation, search, archive access and responsive layout. Exported bible-export.json records source hashes.

Runtime data remains the executable configuration. When implementing a Bible decision, update the relevant source and tests, then amend the implementation observation/status. When source and intended design disagree, retain the discrepancy here until resolved rather than silently redefining the design from code.

Operational manuals for building, publishing, testing, recording and platform validation remain live technical companions. They do not decide game canon. Historical review packets, test results, citations and deployment receipts remain archival evidence.

National record ownership

Use Book IX and data/nations.json for national history, current people and relationships. Generated national dossiers select the existing force records; formation stock stays in forces.json, never copied into a second national inventory. Update the person once, reconcile linked person_ref compatibility fields in command/cast records, and run python3 tools/campaigns/export-national-dossiers.py --sync-compatibility. This is document/data validation only. Script/voice/runtime migration remains separate and is not triggered by research edits.

Maintenance workflow

  1. Read the affected book and register before making a change.
  2. Amend the existing rule or passage in place. Identify owner-approved direction, proposal, historical fact or implementation observation precisely.
  3. Update dependent books, roster identities, scripts and open items together; remove superseded active wording.
  4. Record a concise entry in the single change history, linking the affected sections and evidence.
  5. Export the private reading view and production inputs from the Bible; validate links and affected behaviour.
  6. Keep receipts and research evidence in the archive/evidence layer. Do not create another accumulating “decisions revision” outside the Bible.

A user request authorises its ordinary reversible updates. Proposals remain proposals until adopted. The archive cannot override a later owner decision or a corrected current passage.

Current delivery

The Bible is the private reading entry point. Archived pages and packets retain stable compatibility links. The reading view has its own export and delivery status; game and cinematic releases require their respective verification.

Expanded OOB storyboard delivery

The earlier 30 October retained-force storyboard delivery changed the Bible, current script register and generated review plates. That delivery did not change runtime inventory, voice recordings or finished films. Seven theatre identities are adopted; exact retained strength, commanders and new battalion commitments remain explicit production work. No gameplay/social showcase applied to that documentation-only delivery. The subsequent film implementation has its own showcase package.

Playback and historical records

The game consumes src/data/campaignIntroPlayback.json as executable playback data. It contains no review notes, copied transfer histories, production-status claims or source hashes. It does not define game canon. Current commands, rosters and intended script design remain in the Bible registers.

Historical production snapshots, old roster provenance fields and render receipts are committed in the separate local repository the historical production archive. Its manifest preserves checksums and source revision. The archive has no remote and is historical evidence only. Compilation/voice/film regeneration requires a separate authorized production pass.

Owner review reopened — formation continuity

After delivery, the owner reported that panning and subset changes made formations disappear and reappear and that the sequence was unclear. Earlier geometry, inventory and responsive checks did not establish satisfactory temporal continuity. Visual acceptance is reopened. Claude Opus 5.5 is the designated visual author. The next review establishes a static theater and army/corps organization for each occupied sector before rebuilding motion; existing films remain earlier review cuts. No new film or complete historical OOB is implied by the sector study.

French release menu implementation boundary

The Bavarian dossier lists 32 complete formation offers from the canonical contract. Parent divisions and groups allocate separate battalion/company/battery formations. A tested planning evaluator demonstrates objective confirmation, national material release, one-time orders and blocked transit in the private review, independently of Helmstedt saves. Playable campaign and French tactical integration, initial-OOB production lock and a new southern introduction remain unfinished. French formations are conditional later arrivals.

Terminology and pricing review — 6 November 2026

Reviewed the active Bible, campaign dossier, live campaign requisition/refit labels, intro map explanation, generated force-register headings and private formation menu. Campaign organizations use formation; tactical entities remain units, and definitions are unit types. Save/schema identifiers, historical source titles and archived evidence remain compatible. The current roster contains formation IDs, while its equipment manifests count tactical units and embedded weapons separately. The menu displays provisional RP prices, parent organization, echelon, unit-type roster, readiness, authorization and arrival. Budget and turn checks are executable preview behavior; gameplay balance and live Bavarian integration remain unverified.