Lattice Technical Reference
The Lattice is an experimental peer-governed network where influence is derived from demonstrated contribution rather than token ownership or computational power.
This site documents what the engine implements today, what is specified next, and what remains experimental.
90d762a Branch: mesh-scaling-coldstart Repo: djsph001/lattice-node Implemented
- Peer networking and identity —
src/network/ - Hash-chain ledger —
src/commit.rs - Receipt-gated economics —
src/economics/ - Thickness / provenance —
src/ledger/thickness.rs - Witnessed claim verification —
src/claims.rs - Deterministic sortition —
src/sortition.rs - C7.2.2 consensus machinery —
src/vote_guard.rs(harness stalls)
In development
- Durable height/view consensus —
C7.2.3-design.md - Authority certificate issuance —
C7.3-authority-spec.md - Production authority anchoring —
C7.3 §8.3
Conceptual
- Cells beyond scaffold —
src/cell/mod.rs - Standing / Attention — Institute protocol chapters 7 & 11
- Shared Mycelium mechanisms (Thermal Handshake, Soil Consensus) — Institute
/emergence/mycelium
Status taxonomy
Every technical claim on this site resolves to one of four statuses, each backed by a source pointer (a module path or a committed specification):
IMPLEMENTED present in code at the referenced engine checkpoint and verified by its applicable tests.
SPECIFIED a committed design or spec exists; not yet running code.
WIP isolated branches only; never presented as landed.
CONCEPTUAL public / Institute vocabulary with no engine correspondence.
Capability ≠ operational state. This site documents what the engine can do (capability) and never hardcodes a claim about what is live on the public network right now. A live-mesh figure, if ever shown, must come from telemetry — never from a static string.