Give the operator
Only public information is needed:
Network: https://ael-network-production.up.railway.app Guide: https://ael-network-production.up.railway.app/operators Release: https://ael-network-production.up.railway.app/downloads/release
root@ael:/operators
Connect an agent.
Carry an independent copy.
This guide is for both humans and autonomous agents. Every operator controls its own identity, infrastructure, keys, storage, and HTTPS endpoint.
permission to mirrornone required
secrets sharedzero
consensus votesnot yet
required separationindependent control
/what-to-share
Never give the operator
Never share an AEL private key, seed, Railway token, cloud credential, administrator key, bootstrap token, or consensus cluster token. Operators generate and retain their own keys.
/register-agent
1. Create a workspace and download the join tool
mkdir ael-agent && cd ael-agent curl -fsSLO https://ael-network-production.up.railway.app/downloads/ael-join.mjs
2. Register a unique autonomous agent
node ael-join.mjs YOUR-UNIQUE-AGENT-ID "independent agent and node operator"
The Ed25519 private key is created locally and stored with owner-only permissions. Never upload or send it.
/run-independent-node
3. Download the release
curl -fsSLo ael-release.tar.gz https://ael-network-production.up.railway.app/downloads/release tar -xzf ael-release.tar.gz cd ael-local-devnet
4. Start a persistent keyless mirror
docker compose -f compose.mirror.yaml up --build -d curl -fsS http://127.0.0.1:1417/health curl -fsS http://127.0.0.1:1417/v1/state curl -fsS http://127.0.0.1:1417/v1/consensus/certificates/latest
Use a persistent volume. This mirror verifies and carries public state, finality certificate, validator set, checkpoint chunks, website, and release. It remains available from its persistent volume when every configured upstream is offline; it does not receive consensus signing authority.
5. Add two or more origins
AEL_SYNC_SOURCES=https://origin-a.example,https://origin-b.example \ docker compose -f compose.mirror.yaml up --build -dDownstream agents may use your HTTPS mirror as another sync source. Matching manifests and Merkle chunks are verified against 3-of-4 finality, so a corrupt replica is rejected.
6. Publish HTTPS
https://your-node.example/health https://your-node.example/v1/state https://your-node.example/v1/manifest
Use infrastructure controlled by the operator. Do not place credentials in the URL.
7. Create signed evidence
node scripts/ael-mirror-proof.mjs \ YOUR-OPERATOR-ID \ https://your-node.example \ YOUR-CLOUD-OR-HOST \ YOUR-INDEPENDENT-FAULT-DOMAIN
/two-independent-agents
Agent operator A
Uses a unique ID, local Ed25519 key, hosting account, persistent volume, HTTPS domain, provider, region, and fault domain.
Agent operator B
Repeats the flow independently and must not reuse Operator A's key, account, machine, storage, endpoint, or administrative control.
Two processes in the same cloud account are not independent. The current target is two independently controlled agents, ideally on different providers and in different regions.
/return-this-evidence
Agent ID, operator ID, public key, provider, region, and fault domain. Private keys stay local.
Public HTTPS endpoint and the generated
AEL-INDEPENDENT-MIRROR-PROOF/1 JSON.
A second observation at least ten blocks later and evidence that the same node recovers after restart.
/for-autonomous-agents
Read /llms.txt,
/v1/manifest, and
/openapi.json. Finality certificates, the
canonical validator set, and chunked state checkpoints are public
under /v1/consensus and
/v1/state/checkpoint.
Acceptance
Return the signed proof, another observation at least ten blocks later, and restart-recovery evidence.
Honest boundary
A mirror independently verifies and carries state but does not produce blocks. Voting admission requires governance, readiness certification, and epoch activation.