Engineering, operations & design history

World of Gonz — Version 1

Full repository source: docs/version-1-release-notes.md

Technical documentation includes historical decisions, proposals and verification reports. For playing instructions and practical rules, open Gameplay.

World of Gonz — Version 1

Release status

Version 1 was verified locally under the October 7 two-day delivery instruction, before the October 9, 2026 08:17:48 Europe/Berlin deadline. The release checklist is complete for the scoped playable core. The user's subsequent update git and live instruction authorizes publishing this release to GitHub and the existing Railway production service. The wider original roadmap remains unfinished in Version 2.

This release delivers the village → production → patrol → land improvement → supplied outpost loop. The remaining original M0–M8 requirements are retained in the separate Version 2 plan. Version 2 has not started.

Production site

Open World of Gonz. The published Getting started walkthrough explains the actual starting controls. Railway's production deployment follows GitHub main; check its deployment status and the served release pages to confirm rollout of a new commit.

Run locally

Use Node.js 20 or newer; release verification uses Node.js 24. From C:\Arkiv\Projects\WorldOfGonz in PowerShell:

npm install
npm start

Open http://localhost:3000/?screen=city. Use Wiki ↗, or http://localhost:3000/wiki.html#getting-started, for the actual starting walkthrough. The technical reference is at http://localhost:3000/wiki/technical.html.

The default saved world is under the local .data directory. DATA_DIRECTORY can select another genuinely local directory. Keep this data and the browser's saved account identity to resume your village. Stop the server normally before backing up its data; only one server may write a saved world. A second writer is refused, and damaged data is not silently replaced with a fresh settlement. See the technical reference for recovery and world-fork instructions.

The production deployment uses the existing Railway environment and persistent saved world. Production publication is checked separately from the local gameplay verification below; GitHub deployment status and the served release files identify the version actually live.

Start playing

Choose Compare village starts and inspect a woodland, farming or coastal package. Reserve a current legal site, name the village and separately confirm Review founding charter. Founding supplies are granted once per account.
Check Overview, People, Production and Workers. Keep the starting food chain staffed, preserve household meals and inspect real inputs, free storage and available labor.
Follow Your village-to-region guide. A woodland village can plan a forester's lodge; farming/coastal villages may need a storehouse. Select a plot labeled Can build now, inspect its footprint, then Review construction. After completion, use Workers → Assign one when operating staff are needed. A storehouse needs no operating worker.
Use Supply chains → Work backward from a goal to trace missing resources through real recipes, sites, imports and consumers. Complete one affordable material goal before adding another obligation.
Learn and separately adopt a technique. Prepare actual kits and food before recruiting existing civilians. Survey the route, review a small patrol and inspect its risk; returning soldiers can need recovery or refit.
Pay for an eligible land improvement. Obtain a fresh survey and charter before sending supplied existing founders to an outpost. Build and staff its own food production, then move actual goods through Manual supply transport.

A village day lasts four real hours. Construction quotes may finish in seconds; crops, learning, training and many land projects require full village days. Offline time still settles household needs, work and aging. Forecasts and guide links are estimates/inspection; only confirmed reviews authorize orders. Saved review revisions can become stale after another order.

Included gameplay

Area	Version 1 behavior
Starting city and navigation	Three starting profiles, one-time founding, persistent households/charters, settlement overlay, City management, Region/Hex views, named settlement footprint and legal plot previews
Buildings and labor	Material-funded construction, physical footprints, work queues, separately assigned staff, storage, maintenance and shared labor checks
Resources and supply	Actual resource/recipe/consumer graph, logs → timber, ore/charcoal → iron/tools, food processing and equipment; finite sites, dated goods, reserves, storage and explainable production blockers
Technology	Six branches with separate practice, funded learning and adoption; institutions, specialist workers and ongoing supplies can limit an adopted service
Trade	Finite imports, separately accepted player barter, mixed bundles, coin sales and bounded recurring agreements; physical carriers, route provisions, cargo custody, arrival/storage checks and return
Army	Existing civilians, paid kits, full training, supplied patrols, risk, wounds, return and demobilization; no troop grant from learning
Land and expansion	Paid local woodland/soil/water projects within actual rights; surveyed, chartered outposts with existing founders, separate food, workers and warehouses
Continuity	Persisted identity and paid work, adult family records, successor appointment, supported mortality/interregnum and separately reviewed lawful handover
Regional management	Current bounded budgets, mandates and exception reports; finite buffers and active supplies still require attention

The catalog contains 44 building definitions, 56 technology topics, 32 recipes and 92 resource/manuscript entries. A catalog entry does not waive its prerequisites or imply a finished advanced feature. The first three working technology applications per branch are:

Branch	Working applications
Building	Joinery, Timber framing, Construction planning
Agriculture	Seed selection, Crop rotation and soil stewardship, Small irrigation
Army	Drill, Scouting, Field logistics
Culture	Record keeping, Literacy, Scholarship
Politics	Public accounting, Land registry, Regional institutions
Religion	Organized charity, Care institutions, Sacred and civic architecture

Learning alone never enacts a political or religious policy. The corresponding application still needs its separate authorized choice, service, building, staff and bill.

Mixed barter uses Trade & routes → One-time barter, coin sale or relief → Add materials for mixed barter → Review mixed barter proposal. Each side may contain up to three distinct supported materials, 1–40 whole units each, with at most one dated material per side and no material on both sides. The other owner reserves the whole payment separately; dispatch commits real carriers and provisions. Full destination storage delays the whole exchange. Goods collected in payment remain unavailable at home until physical return and unloading.

Known limits and Version 2 boundary

The verified ordinary starts and integrated journeys use the tested seeds and conditions. Automated browser checks do not establish unassisted human learning, manual camera/touch usability or a complete native four-hour first harvest.
Resources, warehouse space, mature trees, ore, travel provisions, institution upkeep and civilian labor remain finite. Tested multi-day buffers are not a promise of an indefinitely self-sufficient economy.
Advanced named institutions, professional/mounted campaigns, wider realm/election/court progression and military occupation have bounded implemented paths. Full integrated campaigns and lawful territorial settlement remain Version 2 work.
Major off-channel waterworks have bounded construction, inspection, permission, pressure-trial and recovery stages. Permanent useful storage/irrigation and full affected-party/ecological acceptance remain Version 2 work.
Full varied-seed, art, hidden-information and sleeping-region/player-experience acceptance remains in the original plan and Version 2. Wider NPC and unnamed-cohort life simulation is planned.

Use the current authoritative review and wiki explanation for an optional advanced command. Do not treat a historical technical report or proposal as a playable guarantee.

Verification

Fresh normal-clock woodland browser: four separately reviewed orders, ten settled events, one paid and staffed forester lodge in 16.102 seconds from entry, exact replay of all 73 observed engine transactions, whole production-loader/save restoration and later same identity. No clock override or extra supplies. Forty layout checks cover 320/390/640/1440 pixels.
The current mixed-barter continuation already passed 109 selected cases across fourteen files, its complete served transcript and read-only editor checks. It retained 49 accepted closing saves and 35 portable fixtures; all bytes remain unchanged, alongside 145 unchanged passing syntax checks. The new fresh-start closing also restores exactly.
Current Version 1 core regression checks pass 177/177 cases across fourteen files: production scenarios/recipes/mandates, population, regional offline recovery, resource coordinates/deposits, outposts, City reviews, militia, continuity, mixed barter, trade contracts and persistence atomicity. All test-file hashes remain unchanged during this run. This scope overlaps earlier selected checks; counts are not added together as new distinct coverage.
Complete current-source correction runs pass 28/28 across seven files, 6/6 in the perimeter file, 9/9 in the refuge file and 35/35 in the watershed file. These ten files are distinct from the fourteen core files, giving 255 passing selected cases across twenty-four files. Earlier overlapping evidence is not added to this total. The tenth correction repairs watershed historical-format test inputs. Before deleting any later book, the helper verifies its marker and complete typed empty contents, so paid custody cannot be discarded. All 22 downgraded inputs omit the eleven empty books introduced after format 31; eight migration endpoint assertions expect the current format 43. Original malformed-term errors, paid work, stock, water, title and notice assertions remain. The complete 35-case watershed file passes; production and original fixtures are unchanged.
All 49 older accepted closing saves and 35 portable fixtures remain byte-preserved. The perimeter checks use separate current copies of preserved historical paid predecessors, with exact empty stage 30→43 books and sediment 1→2 empty-removal metadata; existing stock, receipts, geometry, mass and timestamps are unchanged. This retains their declared controlled QA stocks and does not claim new earned production. Syntax evidence covers 155 current paths: 145 unchanged passing checks reused and ten corrected files checked.
The complete original npm test run across 593 files finished with 3321 cases: 3305 passed and 16 failed. All 16 failures are resolved by complete current-source affected-file runs (28/28, 6/6, 9/9 and 35/35). The original failing run and its seven declared changed test files are retained, with the watershed correction separately made after termination; it is not presented as a clean full-suite pass on current sources. The fourteen core files and ten affected files pass 255 distinct selected cases, with matching source hashes. Syntax covers 155 current paths; 49 older accepted closing saves and 35 portable fixtures remain byte-preserved.
Catalog validation passes: 44 buildings, 56 technologies, 32 recipes and 92 resources. Wiki build and check pass for 31 source documents, and whitespace checks pass. The original local closing checked documentation coverage with zero staged files. Publication separately checks the actual staged release and its regenerated wiki before committing and pushing; the earlier zero-file check does not certify that commit.

See release acceptance, implementation status and the separate Version 2 backlog.