Runtime Modes

Stub Runtime vs Real Runtime

elo-agent-onboarder currently generates stub-ready installation packages. These packages are designed to validate directory layout, boot flow, health checks, and EOW status reporting before you replace the stub with a real OpenClaw-compatible runtime.

Stub Runtime

  • Generated as bin/openclaw-runtime.example.js.
  • Auto-copied to bin/openclaw-runtime.js when no real runtime exists yet.
  • Exposes a minimal /health endpoint.
  • Lets you test local start scripts, systemd units, docker compose, and EOW status reporting.

Real Runtime

  • Replace bin/openclaw-runtime.js with your actual OpenClaw-compatible runtime entrypoint.
  • Keep config/openclaw-runtime.json as the stable config boundary.
  • Keep /health compatible so generated health checks keep working.
  • Keep status reporting through report-status.sh or your own equivalent runtime logic.

Expected File Layout

install-root/
  bin/
    openclaw-runtime.js
    openclaw-runtime.example.js
  config/
    openclaw-runtime.json
    openclaw-runtime.example.json
  data/
  logs/
  runtime-contract.json
  report-status.sh
  healthcheck.sh

Migration Path

  1. Generate a profile package from EOW.
  2. Run it as-is with the stub runtime to verify the boot chain.
  3. Replace bin/openclaw-runtime.js with your real runtime.
  4. Adjust config/openclaw-runtime.json for your runtime-specific needs.
  5. Keep the generated health and status contracts unless your runtime has a stronger compatible implementation.
Install Plan Contract Bootstrap Architecture Live Service Manifest