Package Structure

lattice is organized as a family of focused packages for CRDTs and their shared infrastructure. You can depend on the lattice_crdt umbrella for the core toolkit, or pick individual packages for a smaller dependency graph.

Packages

lattice packages, versions, documentation, and contents

Package	Version	Docs	What it provides
lattice_crdt	on Hex	API docs	Umbrella for core, counters, registers, sets, maps, sequence, and text
lattice_core	on Hex	API docs	ReplicaId, VersionVector, DotContext — shared causal infrastructure
lattice_counters	on Hex	API docs	GCounter, PNCounter
lattice_registers	on Hex	API docs	LWWRegister, MVRegister
lattice_sets	on Hex	API docs	GSet, TwoPSet, ORSet
lattice_maps	on Hex	API docs	LWWMap, ORMap, Crdt dispatch
lattice_sequence	on Hex	API docs	Generic ordered-list CRDT with move support
lattice_fugue	Unreleased	Not published yet	Non-interleaving sequence CRDT implementing Fugue
lattice_text_core	on Hex	API docs	Shared grapheme and range helpers for text CRDTs
lattice_text	on Hex	API docs	Plain-text CRDT backed by lattice_sequence
lattice_text_fugue	Unreleased	Not published yet	Non-interleaving text CRDT backed by lattice_fugue
lattice_presence	on Hex	API docs	Distributed presence CRDT with topic/key/pid/meta tracking

• lattice_crdt

  Version

  View lattice_crdt on Hex

  Docs

  Read lattice_crdt API docs

  Provides

  Umbrella for core, counters, registers, sets, maps, sequence, and text

• lattice_core

  Version

  View lattice_core on Hex

  Docs

  Read lattice_core API docs

  Provides

  ReplicaId, VersionVector, DotContext — shared causal infrastructure

• lattice_counters

  Version

  View lattice_counters on Hex

  Docs

  Read lattice_counters API docs

  Provides

  GCounter, PNCounter

• lattice_registers

  Version

  View lattice_registers on Hex

  Docs

  Read lattice_registers API docs

  Provides

  LWWRegister, MVRegister

• lattice_sets

  Version

  View lattice_sets on Hex

  Docs

  Read lattice_sets API docs

  Provides

  GSet, TwoPSet, ORSet

• lattice_maps

  Version

  View lattice_maps on Hex

  Docs

  Read lattice_maps API docs

  Provides

  LWWMap, ORMap, Crdt dispatch

• lattice_sequence

  Version

  View lattice_sequence on Hex

  Docs

  Read lattice_sequence API docs

  Provides

  Generic ordered-list CRDT with move support

• lattice_fugue

  Version

  Unreleased

  Docs

  Available after the first release

  Provides

  Non-interleaving sequence CRDT implementing Fugue

• lattice_text_core

  Version

  View lattice_text_core on Hex

  Docs

  Read lattice_text_core API docs

  Provides

  Shared grapheme and range helpers for text CRDTs

• lattice_text

  Version

  View lattice_text on Hex

  Docs

  Read lattice_text API docs

  Provides

  Plain-text CRDT backed by lattice_sequence

• lattice_text_fugue

  Version

  Unreleased

  Docs

  Available after the first release

  Provides

  Non-interleaving text CRDT backed by lattice_fugue

• lattice_presence

  Version

  View lattice_presence on Hex

  Docs

  Read lattice_presence API docs

  Provides

  Distributed presence CRDT with topic/key/pid/meta tracking

Dependencies

graph LR
    lattice_counters --> lattice_core
    lattice_fugue --> lattice_core
    lattice_registers --> lattice_core
    lattice_sequence --> lattice_core
    lattice_sets --> lattice_core
    lattice_maps --> lattice_core
    lattice_maps --> lattice_counters
    lattice_maps --> lattice_registers
    lattice_maps --> lattice_sets
    lattice_text --> lattice_core
    lattice_text --> lattice_sequence
    lattice_text --> lattice_text_core
    lattice_crdt --> lattice_core
    lattice_crdt --> lattice_counters
    lattice_crdt --> lattice_registers
    lattice_crdt --> lattice_sequence
    lattice_crdt --> lattice_sets
    lattice_crdt --> lattice_maps
    lattice_crdt --> lattice_text
    lattice_text_fugue --> lattice_core
    lattice_text_fugue --> lattice_fugue
    lattice_text_fugue --> lattice_text_core
    lattice_presence

The only packages with no lattice package dependencies are lattice_core, lattice_text_core, and lattice_presence. lattice_text_core depends only on gleam_stdlib; lattice_core and lattice_presence also depend on gleam_json.

Import paths

In Gleam, imports come from the package name. Even when you install the umbrella lattice_crdt, you import from the sub-package names:

import lattice_core/replica_id
import lattice_counters/g_counter
import lattice_sets/or_set
import lattice_maps/or_map
import lattice_sequence/sequence
import lattice_fugue/sequence
import lattice_text/text
import lattice_text_core/grapheme
import lattice_text_fugue/text
import lattice_presence/presence_state

Which approach to choose

Start with lattice_crdt if you are getting started, prototyping, or using CRDTs from multiple categories. It includes the causal core, counters, registers, sets, maps, the YATA-style sequence, and its text wrapper.

Pick individual packages when binary size or dependency count matters, or when you only need one category of CRDT. For example, if you only need counters:

gleam add lattice_counters

Add lattice_presence separately when you need distributed presence. It has no lattice package dependencies and is not included in the lattice_crdt umbrella.

Evaluating the Fugue packages

lattice_fugue and lattice_text_fugue are not published to Hex yet. To evaluate either package, clone the lattice repository and declare the package as a local path dependency in your project's gleam.toml:

[dependencies]
lattice_fugue = { path = "../lattice/packages/lattice_fugue" }
lattice_text_fugue = { path = "../lattice/packages/lattice_text_fugue" }

Keep only the dependency or dependencies you need. Paths are relative to your project's gleam.toml, so adjust them for the location of your lattice clone. Do not use gleam add for these unreleased packages.

See Installation for full details.