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.
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.
Typical commands
lattice up lattice doctor lattice status lattice publish --dir ./site --name mysite lattice name info mysite lattice update --all
Exact subcommands will evolve, but the important split is stable: the CLI is local orchestration, the daemon is the long-lived network agent.
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 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.
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.