Meridian docs
Meridian documentation

Find a page.

Type at least two characters.

    Docs menu

    Systems

    System map

    A map of Meridian’s named systems, what each one owns, and where to find the exact current state.

    Updated July 17, 2026Private source revision 9e8f80b

    These guides are readable maps, not normative specifications. They describe the private source revision shown above; direct links to the documents carrying authority will appear with the source release.

    Core named systems

    SystemOwnsAt this snapshot
    PenumbraRendering above the hardware boundaryA bounded direct rendering path exists; the production Forward+ path remains ahead.
    CairnPhysics architecture and eventual Meridian-owned solver pathsMeridian currently wraps a third-party solver behind its own contracts.
    WavefrontAudio device, streaming, timing, DSP, mixing, and acousticsThe architecture exists; the audio runtime does not yet.
    AlluviumProcedural recipes, evaluation, identity, overrides, provenance, and cookingThe recipe and evaluation foundation exists; production world integrations remain ahead.
    System
    Penumbra
    Owns
    Rendering above the hardware boundary
    At this snapshot
    A bounded direct rendering path exists; the production Forward+ path remains ahead.
    System
    Cairn
    Owns
    Physics architecture and eventual Meridian-owned solver paths
    At this snapshot
    Meridian currently wraps a third-party solver behind its own contracts.
    System
    Wavefront
    Owns
    Audio device, streaming, timing, DSP, mixing, and acoustics
    At this snapshot
    The architecture exists; the audio runtime does not yet.
    System
    Alluvium
    Owns
    Procedural recipes, evaluation, identity, overrides, provenance, and cooking
    At this snapshot
    The recipe and evaluation foundation exists; production world integrations remain ahead.

    Other architecture

    Meridian’s adopted architecture also names Collective for optional online services, Isobar for weather and climate state, Basalt for terrain, Torsant for fluid simulation, and Marquee for a deferred post-1.0 promotional export workflow. Their names do not imply complete implementations.

    How systems meet

    Ownership passes through typed contracts. Alluvium may author a recipe that produces terrain inputs, but Basalt owns terrain runtime behavior. Cairn owns physics queries, while gameplay decides what those queries mean. Penumbra renders snapshots without taking world authority. Wavefront owns audio behavior while Collective owns online session policy.

    Documentation © Dead Signal Works LLC. Licensed under CC BY-SA 4.0.