How to Operate the System

Start Here

• ZerothCore is operated from the public web layer, the operator dashboard, Commander, mission routes, and proof APIs.
• Default entry point: /world.
• Primary command surface: /commander.
• Primary service offer: /services.
• Public route directory: /routes.

Daily Health Checks

• Check /api/health locally and publicly before making changes.
• Use PM2 to confirm zerothcore-web is online.
• After restart, wait for Next.js to bind to 127.0.0.1:3000 before testing public routes.

curl -sS http://127.0.0.1:3000/api/health | jq
curl -sS https://zerothcore.ai/api/health | jq
curl -sS https://zerothcore.com/api/health | jq
pm2 status

Services + PayPal Operations

• The live service page is /services.
• The current offer is Founding Operator Access.
• The current PayPal offer id is founding-operator-access.
• The current price is $500.00 USD.
• Order creation must return ok=true, PAYER_ACTION_REQUIRED, an approveUrl, and the expected offer id.

for URL in \
  http://127.0.0.1:3000/api/paypal/order \
  https://zerothcore.ai/api/paypal/order \
  https://zerothcore.com/api/paypal/order
do
  echo "--- $URL ---"
  curl -sS -X POST "$URL" -H "Content-Type: application/json" | jq
done

Menu / Public Routes

• Public menu routes are registered in lib/zerothcore/public-route-registry.ts.
• Add public pages there after the route exists and builds.
• Use /routes to confirm the public route index exposes the page.

Build + Deploy Procedure

• Back up files before mutation.
• Change the minimum necessary files.
• Run npm run build.
• Restart zerothcore-web with PM2.
• Save the PM2 process list.
• Verify local and public routes.

npm run build
pm2 restart zerothcore-web --update-env
pm2 save

Evidence + Proof Cycle

• Every surgical change should create a timestamped folder under data/proof-cycle.
• Store backups, command output, and verification notes there.
• Do not claim deployment success without health, route, or API evidence.

Charmy / EEPOTH / Exnilium Glossary

• Charmy: conversational/operator intelligence layer.
• EEPOTH: command doctrine and proof-cycle control layer.
• Exnilium: generation, storage, organism, and artifact systems.
• Proof cycle: inspect, back up, change, build, restart, verify, preserve evidence.

Emergency Stop / Rollback

• If a change breaks the build, restore the backup from the matching data/proof-cycle folder.
• If the app is down, check PM2 logs and port binding first.
• Never delete working subsystems during recovery.

pm2 logs zerothcore-web --lines 120 --nostream
ss -ltnp | grep -E '127.0.0.1:3000|node|next'
pm2 restart zerothcore-web --update-env