Operations

Local command line.
Local daemon.

The CLI is thin by design. It mostly packages requests for the daemon, which owns the node key and the network state.

// Pattern

How the tools fit

The daemon runs continuously and exposes RPC. The lattice CLI is the operator surface for publishing, querying state, and triggering maintenance actions.

// Commands

Typical commands

lattice up
sudo lattice up --server
sudo lattice up --bootstrap
lattice doctor
lattice status
lattice publish --dir ./site --name mysite
lattice name info mysite
lattice update --all

lattice up is the normal desktop/laptop path. For an always-on Linux host, prefer sudo lattice up --server. For a bootstrap node, use sudo lattice up --bootstrap.

// Diagnostics

Use lattice doctor first

lattice doctor is the quickest support command in the stack. It checks the local daemon path, service state, RPC reachability, and prints the next sensible thing to do if something is missing.

lattice doctor
lattice doctor --json
lattice doctor --json --strict

The JSON form is useful for bug reports, CI smoke checks, and future installer/setup flows. --strict exits nonzero when the setup is unhealthy.

// RPC

RPC responsibilities

  • Manage name and site publication.
  • Query local node and storage state.
  • Expose maintenance operations like targeted resets or diagnostics when needed.
  • Provide local-only signing for app admin flows.
// Ports

Local surfaces

Fray and the browser extension both rely on local HTTP endpoints. Those surfaces should be treated as privileged local interfaces and hardened accordingly.