splendorctl

splendorctl is the local command-line interface for Splendor runtime workflows. It is useful for quickstarts, examples, trace inspection, state inspection, and safe replay.

Version

splendorctl --version

Run a local config

splendorctl run --config ./examples/local-basic-loop/config.yaml --cycles 1

This starts the local loop, invokes policy, submits actions through the gateway, commits state, and writes trace events.

Export traces

splendorctl trace export --db ./examples/local-basic-loop/data/trace.db --run <run-id>

Trace export emits JSON Lines of append-only trace records.

Inspect state head

splendorctl state head --db ./examples/local-basic-loop/data/trace.db --run <run-id>

The state head is the latest committed state node for the run.

Replay

splendorctl replay --db ./examples/local-basic-loop/data/trace.db --state-db ./examples/local-basic-loop/data/state.db --run <run-id>

Replay reconstructs the run without calling adapters again.

Daemon request helper

splendorctl daemon request can send local development requests to the runtime daemon. Use it only with explicit loopback local development settings unless the daemon is configured with authenticated production-grade transport and caller credentials.

splendorctl daemon request \
  --method GET \
  --url http://127.0.0.1:8077/health \
  --token "$SPLENDOR_CALLER_TOKEN" \
  --caller-credential ./caller-credential.json

Daemon tokens authenticate callers; they are not action authority. Side effects still require signed work-order scope and gateway verification.