jflow-core 0.1.0

Shared types, configuration, and application state for the JANUS trading engine (signals, config, unified metrics, inter-module channels).
Documentation

jflow-core

Shared types, configuration, and application state for the JANUS trading engine.

Published to crates.io as jflow-core (the janus-core name is owned by an unrelated project). The library is imported as jflow_core.

This is the foundational crate the rest of the JANUS workspace builds on. It deliberately depends on no other workspace crate, so it can be reused standalone.

What's here

  • Config — unified TOML + environment configuration with a Redis overlay.
  • JanusState — shared application state (signal/market-data buses, service lifecycle, runtime log-level control, regime/threat snapshots, and a pluggable affinity recorder).
  • Signals — Signal, SignalBus, SignalType.
  • Market data — MarketDataEvent and friends (TradeEvent, KlineEvent, OrderBookEvent, …) plus the MarketDataBus.
  • Position guidance — PositionEvent, PositionClose, compute_guidance, PositionTracker (stateful trailing/give-back + sticky-exit), and PositionOutcome for closed-trade feedback.
  • Optimized params — OptimizedParams / ParamManager for hot-reloadable, per-asset strategy parameters.
  • Supervisor, metrics, session metrics, and shared Error/Result.

Features

  • redis (default) — enables the Redis-backed config overlay and param-update subscription. Disable with --no-default-features for a build with no Redis dependency.

Usage

[dependencies]
jflow-core = "0.1"

use jflow_core::{Config, JanusState};

# async fn run() -> jflow_core::Result<()> {
let config = Config::load()?;
let state = JanusState::new(config).await?;
# Ok(())
# }

License

MIT