AI-Assisted AeroNyx Node Deployment Standard

AeroNyx privacy protocol nodes can be installed and maintained with AI coding agents such as Codex, OpenClaw, Claude Code, Hermes, and similar terminal-capable assistants.

The standard is simple: the human operator provides the server and approves the action; Nodeboard provides the registration code and generated command; the AI assistant uses one AeroNyx entrypoint and verifies the result.

Source of the command

The command comes from Nodeboard:

https://app.aeronyx.network

Open Registration Codes, create or select a private registration code, and copy the generated quickstart command.

The assistant should not guess where deploy/node/aeronyx-node.sh comes from. It comes from the open-source Rust repository:

https://github.com/AeroNyxNetwork/AeroNyx

The generated command clones or pulls that repository first, then runs the wrapper.

Required command flow

The generated command implements this flow:

clone/pull main -> preview plan -> install/register -> status -> healthcheck

The primary entrypoint is:

./deploy/node/aeronyx-node.sh

The normal action is:

./deploy/node/aeronyx-node.sh quickstart --registration-code "<code>" --api-base "https://api.aeronyx.network/api" --repo-dir "$PWD"

AI safety rules

AI assistants must:

• use the generated Nodeboard command
• use deploy/node/aeronyx-node.sh as the primary entrypoint
• read the preview plan aloud or summarize it
• require human approval before entering INSTALL
• run status and healthcheck after install or upgrade
• report Nodeboard Capacity Decision results
• report Event Closure open/watch/recovered results
• avoid exposing registration codes in logs or public chat
• avoid collecting packet payloads, destinations, DNS contents, domains, URLs, browsing history, private keys, or wallet-level traffic

AI assistants must not:

• invent script names
• bypass the preview plan
• run destructive system commands without approval
• change Nodeboard policy without explaining impact
• restart a node with active sessions unless the operator explicitly approves the impact

Completion checklist

An AI-assisted deployment is complete only when:

• the Rust repository is on main
• quickstart has completed
• status reports the node process and operator metadata
• health --json reports AeroNyx privacy protocol status
• Nodeboard shows fresh heartbeat
• Capacity Decision is visible
• Event Closure has no unreviewed critical Open item
• the operator knows the node detail URL in Nodeboard