smooth-operator
The reference core for smooth-operator — the service layer on top of
[smooth_operator_core] (the agent engine). It defines three things:
- [
domain] — storage-agnostic domain structs (Conversation, Participant, Message, Session) that mirrorspec/domain/*.json. Checkpoints re-use the engine's [smooth_operator_core::Checkpoint]. - [
adapter] — the single [StorageAdapter] seam every backend implements (seedocs/STORAGE.md). Its checkpoint/knowledge accessors return smooth-operator-core's own traits so the engine plugs straight in. - [
runtime] — a minimal [AgentRuntime] that constructs a real smooth-operatorAgentandWorkflow, proving consumption.
It also owns two shared retrieval seams both backends/consumers depend on:
[embedding] (the text→vector [Embedder] + the network-free
[DeterministicEmbedder], the one home for both the Postgres adapter and the
ingestion pipeline) and [rerank] (the optional post-retrieval [Reranker]
stage — feature gap G8).