Alluvium

Alluvium is Meridian’s procedural world-authoring and asset-generation system. It is meant to make generated work inspectable: the recipe, inputs, identity, overrides, provenance, derived cost information, and cooked result belong to one traceable pipeline.

Recipe to result

1. 01Recipe

   Human-readable source declares typed operations and stable intent.

2. 02Fields and inputs

   Validated scalar or spatial data enters under explicit types and limits.

3. 03Evaluation

   Deterministic substreams produce stable generated identity.

4. 04Overrides

   Authored exceptions attach to identity instead of silently replacing the source.

5. 05Cooked result

   Runtime systems receive rebuildable artifacts while retaining their own live authority.

Current foundation

At this public revision, Alluvium is an implemented foundation. Canonical text recipes, typed fields, strict scalar evaluation, stable identity, deterministic substreams, retained override outcomes, derived-cache recovery, validation, a structured CLI, provenance auditing, and a basic semantic inspector have bounded implementation and cross-platform qualification behind them.

The full procedural world system, production terrain and vegetation integrations, native visual authoring, runtime-safe recipe execution, and private Project Meridian recipes are not complete public features.

Runtime ownership stays elsewhere

Alluvium can author inputs and derived predictions. It does not become the live terrain, physics, weather, rendering, navigation, audio, streaming, or save system. Those systems retain authority over runtime state.

This also preserves baked-only games: if a project ships cooked outputs without the evaluator, disabled Alluvium runtime behavior should impose no hidden cost.