Current Public Contract
The repository’s current public guidance describes a canonical workspace with a dedicatedstate/ directory for runtime data:
~/.chainbot. Set CHAINBOT_CONFIG_DIR to point ChainBot at a different complete root.
What the state/ Directory Means
The stable contract in the public README is intentionally narrow:
state/is the runtime state area for a ChainBot root.- It sits alongside workflows, triggers, plugins, and secrets.
- It is part of the canonical layout created by
chainbot init.
docs/user/. Until that document exists, treat the README and design docs as the authoritative public source.
Operational Guidance Available Today
The commands below let you inspect or manage runtime behavior without inventing an additional storage abstraction:statusgives a non-executing workspace snapshot.observeinspects persisted trigger events, workflow logs, and runs.list-runsreturns workflow run history.servestarts the long-running daemon control plane.stoprequests graceful shutdown.
Configuration Boundary
The public root configuration examples show runtime defaults and path configuration inchainbot.toml: