Runbook / ops

Crucible's operational controls support the retail trading OS vision. These notes describe the runtime foundation, not a declaration of live readiness. Use the runbook and configuration shipped with the exact deployed release.

Modes and qualification

The runtime recognizes PAPER, LIVE, BACKTEST and REPLAY. A recognized mode name does not establish that a broker, instrument or strategy is supported and qualified in that mode. Paper fills are simulated and do not predict live execution quality.

The composed strategy path still needs composed qualification, followed by supervised local paper and IBKR-paper gates. Live operation requires its own acceptance and authorization. The IBKR adapter and retail operator workflow remain in development.

Pre-flight and risk controls

Validate configuration, identities, data coverage and connectivity. Reconcile runtime state with the execution adapter and treat incomplete or unknown outcomes explicitly. Refusing new risk must preserve obligations to manage existing exposure; cancellation and flatten behavior require their own evidence.

The exact risk limits and credentials belong to private deployment configuration. The public marketing site does not issue trading commands or manage secrets.

Recovery

1. Retain the journal, identity sidecar, trusted chain anchor and matching configuration.
2. Validate journal integrity and reconstruct state. Current startup verifies the journal and its checkpoints; it does not promise to read only a snapshot and tail.
3. Identify any torn/missing tail and apply the configured recovery policy.
4. Reconcile broker outcomes before resuming new risk.

Durability settings determine what can be lost on process or host failure. An append is not a promise of durable persistence. Do not treat unknown broker outcomes as known rejections or blindly retry commands after restart.

Operator console

anvil-tui is a read-only terminal console consuming health and metrics. It is not the planned retail web control surface.

anvil-tui \
  --health-url http://127.0.0.1:9091/health \
  --metrics-url http://127.0.0.1:9090/metrics

Observability and performance

Prometheus metrics, health endpoints and structured tracing expose runtime behavior. Qualify end-to-end timing with the journal and operator path enabled, at the actual strategy input scope. Record queue pressure, refusals and failure behavior alongside latency; a feed-only percentile is not the full decision cost.