ForgeFX · Kubota Source Consolidation

Three Surfaces → One Kubota Home

Adam’s intent: preserve the strongest farming visuals and mechanics, eliminate duplicate Kubota implementations, and give Devin one local checkout with one canonical source package and one public product URL.
Important finding: the ForgeLab Kubota copy and the loose demo were already moved into ForgeKubo on August 24. ForgeFarm remains separate.

Current State vs. Intended End State

Current

Three live domains, three app packages

Verified live
A · ForgeFarm ’19
farm.forgefx.dev

The polished standalone Babylon.js farming demo. This is the remaining major source to reconcile into the Kubota product.

github.com/adamkane/forgeapps/tree/dev/apps/forgefarm
/Users/forgebot/forgeapps/apps/forgefarm
Kubota copy removedB · ForgeLab
forgelab.forgefx.dev

ForgeFX’s broader prototype lab. It previously hosted compiled Kubota pages under public/kubo and public/kubota-autosteer-farm-demo; neither exists in the current repository.

github.com/adamkane/forgeapps/tree/dev/apps/forgelab
/Users/forgebot/forgeapps/apps/forgelab
Canonical Kubota packageC · ForgeKubo
kubo.forgefx.dev
/Product story and project library
/simulatorCurrent WorkSmart open-field simulator
/autosteerImported farm-demo code formerly duplicated in ForgeLab and a loose app
github.com/adamkane/forgeapps/tree/dev/apps/forgekubo
/Users/forgebot/forgeapps/apps/forgekubo
→
Target

One Kubota product and source home

Desired
C · ForgeKubo survives
kubo.forgefx.dev

One package for the Kubota story, references, media, models, training experience, and the best ForgeFarm environment/mechanics.

Merge into C
Selected ForgeFarm scene, game systems, camera work, terrain, vegetation, equipment behavior, tests, and production assets—reconciled rather than copied wholesale.
/Single Kubota landing and project hub
/simulatorOne canonical simulator experience
sourceAll Kubota code under apps/forgekubo
Archive after parityA · ForgeFarm retired as a separate product

After the valuable implementation is proven in ForgeKubo: archive the standalone app/project and retire or redirect farm.forgefx.dev.

Already cleanB · ForgeLab stays non-Kubota

Do not reintroduce a Kubota copy. Archive only the historical Kubota routes/content—not the entire ForgeLab product—unless Adam explicitly intends to retire ForgeLab itself.

Source Chunks That Matter

A · Bring forward from ForgeFarm

  • src/components/FarmGame.tsx — core polished farm experience
  • src/game/* — terrain, atmosphere, crops, equipment, rural dressing, vegetation
  • public/assets/* — environment, models, textures
  • Tests covering terrain and app behavior

B · Historical only

  • public/kubo/* — deleted compiled Kubo copy
  • public/kubota-autosteer-farm-demo/* — deleted compiled demo
  • The living source now exists in C; B should contribute no new source
  • The old ForgeLab URL currently falls back to the ForgeLab shell, not a Kubota experience

C · Destination and reconciliation point

  • src/openworld/* — current canonical WorkSmart simulator
  • src/autosteer/* — imported farm-demo source
  • public/assets/* and public/models/* — shared runtime media
  • src/App.tsx — route integration
Interpretation guardrail: “Archive everything except C” is safe if it means the standalone ForgeFarm deployment plus all Kubota duplicates. Archiving the entire ForgeLab app would remove unrelated prototypes, so that should be treated as a separate decision.