Procedural Fields

Author one deterministic field bundle, then adapt it to each shader stage and consumer. Coordinates, seed, causes, derivatives, and output meanings belong to the field; fragment footprints, vertex LOD, storage, and diagnostics are consumer adapters.

For multi-system work, $threejs-choose-skills is an optional coordinator. Materials own PBR response, geometry owns topology, water owns free-surface state, and the final-image skill owns tone mapping and output conversion. Publish each cross-system field output with units, coordinate/frame convention, producer and consumer owners, revision, spatial/temporal support and filter, validity domain, error bound, update cadence, and staleness rule. Keep GPU resource layout and render LOD private to the consuming adapter.

1. Freeze the field contract

Record before implementation: