zeekayandHanzo Dev 14aa0fb805 docs: describe the three implementations, and how to build and check each ...

Lux is one protocol realised in Go, Rust and C++, and the docs described only
the Go one — so a reader had no way to tell which implementation a statement
was about, or that two of them are measured against the third rather than
against the spec.

Three new pages, one concern each:

  /implementations  what exists in each language across the six planes
  /build            native build recipes for all three
  /conformance      the corpus, the pinned oracle, the harness and its gaps

Refreshed where the existing pages were wrong or ambiguous:

  /zap          the version word is 2, not 1; the header rules a decoder must
                enforce, including the refusals, which are part of the protocol
  /zap/family   four layers answer to the name ZAP and two of them share no
                bytes; naming them apart is the fix, not a version field
  /gpu          one C++ implementation with bindings, not three; CUDA is not
                cleared for anything entering a state root
  /nodes        a node with no --http-port listens on 9630, not 9650

Every recipe and every port here was run or read out of the source, and the
one failing conformance check is recorded as failing rather than asserted to
be correct.

Co-authored-by: Hanzo Dev <[email protected]>

2026-08-29 01:36:13 -07:00

..

docs

docs: describe the three implementations, and how to build and check each

2026-08-29 01:36:13 -07:00