Crate keelrun_core 

keel-core: the real Keel kernel, Tier 1 scope (architecture spec §4).

One Engine per process runs every intercepted call through its target’s layer chain — cache → rate → breaker → timeout → retry — driven by the shared typed policy model (keel_core_api::policy). Waits are real tokio::time sleeps: production sleeps wall-clock time, and the conformance harness runs under start_paused where the same sleeps advance virtual time deterministically. The engine passes the identical scenario corpus as keel-core-stub — that equivalence is the whole point of the conformance suite.

Beyond the stub, the real engine:

• enforces timeout with tokio::time::timeout around each attempt (a policy-layer timeout terminates as KEEL-E011)
• applies schedule jitter (equal jitter: uniform in [w/2, w])
• is &self-concurrent: interior state behind a mutex, never held across an await

Every call and attempt is also emitted as a tracing span (keel.call / keel.attempt, architecture spec §4.5), with breaker transitions and cache hits as debug events. Spans cost effectively nothing when no subscriber is active. Enabling the optional otel feature adds [otel::init_otlp] to export those spans over OTLP. Independently of tracing, the events sink streams a live NDJSON feed of attempts/backoffs/breaker transitions to .keel/events/ (for keel tail), and mints the trace refs Tier 1 failure messages carry.

Tier 2 durable flows (FlowManager) build on the Tier 1 engine and the keel_journal persistence layer; the FFI facade wraps this async surface (later slices) for the PyO3/napi bridges.

Re-exports

pub use flow::FlowConfig;

pub use flow::FlowDescriptor;

pub use flow::FlowHandle;

pub use flow::FlowManager;

Modules

events

Tier 1 live event sink: an append-only NDJSON feed of what the engine is doing right now — attempt starts/failures, backoff waits, breaker open/half-open/close, rate-limit queueing, cache hits/misses — written per run to .keel/events/<run>.ndjson for keel tail / keel trace to follow (dx-spec §6, invariant 4). Non-contract: the line format is versioned ("v": 1 on every line) but lives outside contracts/; only Keel’s own tooling reads it, and no daemon is involved — readers tail the file (dx invariant 3).

flow

Tier 2: the durable flow manager (architecture spec §4.3–4.4).

Structs

Engine

The Keel kernel, Tier 1 scope. One per process; &self-concurrent.

Traits

DiscoveryRecorder

The discovery-recording surface the engine depends on: a single method, so the engine can hold a DiscoveryStore type-erased regardless of the Clock it was opened with. Implemented for every DiscoveryStore<C>.