CLARA independent node — Node.js 22+; no dependencies. Extract to a private folder, not a web root.
Run from the extracted directory:
  node node/node.mjs init
  node node/node.mjs credentials
  node node/node.mjs serve
Open http://127.0.0.1:8788/ and select Node, paste the token and explicitly approve the displayed authority pin. No public listener; the hosted web studio cannot contact this local HTTP node by default. Browser actor key is separate from node authority. The operator token permits submissions and reading the whole ledger. A separate readToken permits snapshot reads only; give mirrors only readToken, and protect both. Ledger text and contract data are not encrypted. Use non-sensitive data. Keep state.json private and backed up; losing the authority or actor key can prevent future changes. One process per data directory. CLARA_NODE_DATA overrides the directory; CLARA_NODE_PORT changes port. Do not remove writer.lock unless you have confirmed the previous process is stopped. Do not expose this reference server to the internet or critical workloads. No consensus, money, mining or autonomous peer discovery.
Independent mirror workflow (stop any running node in the target directory):
  node node/node.mjs export chain.json
Copy chain.json and the authenticated network and authority key to the mirror operator. In a DIFFERENT working directory or set CLARA_NODE_DATA:
  node node/node.mjs mirror-init chain.json NETWORK AUTHORITY_KEY
  node node/node.mjs credentials
  node node/node.mjs serve
To update, stop mirror, export a fresh snapshot from authority and transfer it, then run:
  node node/node.mjs mirror-sync new-chain.json
Mirror verifies each signature, deterministic state replay, authority pin and append-only history; it refuses forks or truncation. Export reflects committed state at read time. Snapshots are not confidential; transfer privately as appropriate. No automatic network transport or TLS service is included. For deployment across organizations a separately reviewed authenticated TLS gateway, access-control policy, redundancy and independent audit are necessary.

Optional authenticated pull (mirror stopped): set CLARA_PEER_TOKEN to the source node readToken privately, then node node/node.mjs mirror-pull http://127.0.0.1:8788/. The source can be another local process or an explicitly configured trusted HTTPS service; no redirects or plain remote HTTP. A pull never changes the mirror's pinned authority and rejects history rollback. Unset the environment variable afterward.

Credential lifecycle: stop the node, run node node/node.mjs rotate-tokens, then node node/node.mjs credentials. Both previous tokens are invalidated; ledger identity and history are unchanged. Distribute only the new readToken to mirrors. The console identifies read-only connections before allowing write controls.
