Struct EmbeddedKernel 

pub struct EmbeddedKernel { /* private fields */ }

One opened embedded kernel: the composed service plus the store handle for operational tooling (replay, stats, compaction).

Implementations

impl EmbeddedKernel

pub fn open(data_dir: &Path) -> Result<Self, PortError>

Opens the store at data_dir (fail-fast per ADR-012) and composes the kernel. An existing directory opens with the engine it was created with; a fresh one gets the caller’s resolved default. On redb a second session on the same data dir fails here with an explicit single-writer error (ADR-011; the engine holds the lock); on SQLite it does not.

pub fn open_with_engine( data_dir: &Path, engine: Option<StorageEngine>, ) -> Result<Self, PortError>

open with a say in the engine (ADR-018): a fresh directory is created for engine; an existing one must already be engine, and the mismatch is refused by name rather than quietly opened as whatever it is — that is how a user ends up on the wrong engine without knowing. None means no preference.

pub fn engine(&self) -> StorageEngine

The engine behind this kernel’s store, as its data directory records it. Surfaced at startup and by the doctor so a user can see which one they are on.

pub fn data_dir(&self) -> &Path

pub fn store(&self) -> &EmbeddedKernelStore

pub fn service(&self) -> Arc<EmbeddedMemoryService>

pub fn quality_observer(&self) -> Arc<dyn QualityMetricsObserver>

pub fn quality_telemetry_dropped_observations(&self) -> u64

pub fn quality_telemetry_write_failures(&self) -> u64

pub fn quality_telemetry_error(&self) -> Option<&str>

pub fn quality_telemetry_active(&self) -> bool

Trait Implementations

impl MemoryRecallApi for EmbeddedKernel

fn capabilities(&self) -> ApiCapabilities

What this implementation is and what it can do. Checked by consumers at startup, before anything is at stake.

async fn wake( &self, request: MemoryWakeRequest, ) -> Result<MemoryRecallView, ApiError>

Recall the bounded context of one about.

async fn ask( &self, request: MemoryAskRequest, ) -> Result<MemoryRecallView, ApiError>

Ask one question of the memory, under an explicit answer policy.

impl MemoryRecordApi for EmbeddedKernel

fn capabilities(&self) -> ApiCapabilities

What this implementation is and what it can do. The report is the same one the recall side gives — one implementation, one account of itself.

async fn record( &self, request: MemoryRecordRequest, ) -> Result<RecordedMemoryView, ApiError>

Put something into the memory of one about, idempotently.