Contract Artist/Developer: Fully Procedural three.js Environment (No External Assets)

The Project: We're looking for a contractor to build one flagship 3D environment as a proof of concept — a scene generated entirely by code, running live in the browser in three.js, with no external meshes, textures, HDRIs, or audio files referenced anywhere. Every tree, rock, building, texture, and light needs to originate from procedural logic at runtime. This is a paid trial project. If it goes well, there's follow-on work building a small library of similar scenes across other environment types (urban, rural village, fantasy, desert, mountains, historical, ruins, oriental architecture — you're welcome to propose which one you tackle first). The quality bar: Before applying, look at this reference project: https://github.com/Braffolk/fable5-world-demo — a fully procedural 4x4km open world in three.js (WebGPU/TSL), built with zero external assets. It's a strong illustration of the ceiling we're aiming near: believable terrain with real hydraulic erosion, hundreds of thousands of uniquely-varied plant instances, four-cascade shadows with no crushed blacks, volumetric atmosphere, reflective water, and a laundry list of explicitly banned outcomes (cloned-looking trees, tiled textures, fog used to hide LOD pop-in, flat/lifeless lighting). Your scene will be smaller in scale and doesn't need an identical feature list — but it should read as deliberately art-directed and technically considered, not like a generic Three.js demo scene. We want it to hold up next to what current AI-driven "world generation" pipelines are starting to produce, and beat them on craft. What you'll deliver: -A single self-contained, real-time interactive scene built in three.js (WebGL or WebGPU — your call, tell us why), running in a normal modern browser, with no dependency on any external asset files. All geometry, materials/textures, and lighting generated by code. The scope of the scene should be approximately 100mx100m, though the specific content type might change this. -A design document covering: --Your technical approach and design principles for the environment --A file-by-file description of the codebase and how it's structured --Caveats, pitfalls, and dead ends you hit (and how you got around them) — this is as valuable to us as the scene itself -Source code, organized and documented well enough that another developer could pick it up. Who we're looking for: three.js expertise is a plus but not the only path in — procedural-generation thinking matters more than framework familiarity. Strong candidates might come from: -three.js / WebGL / WebGPU creative development -Houdini (procedural modeling, VEX, PDG) -Grasshopper / Rhino (parametric/generative design) -Generative art / creative coding backgrounds (Shadertoy, p5.js, openFrameworks, TouchDesigner) with a track record of shipping to the browser Please include examples of prior procedural work — even outside three.js — alongside anything browser-based you've built. Scope & terms -Format: Fixed price per scene, paid trial engagement -Scene topic: Open — propose the environment type you're most excited to tackle from the list above -Timeline & price: Propose your own estimate for a scene + design doc at this quality bar; tell us your reasoning -Rights: Work product (code + doc) is delivered as a work-for-hire; no third-party or stock assets of any kind may be used How to apply: Send: -Links to your strongest procedural/generative work (three.js if you have it, otherwise Houdini/Grasshopper/creative-coding work is great too) -A short note on which environment type you'd pick for the flagship scene, and why -Your proposed price and timeline for scene + design document