Enum HighPriCommand 

pub enum HighPriCommand {
    AssertEdge {
        edge: EdgeAssertion,
        responder: Sender<Result<()>>,
    },
    RetireEdge {
        source: String,
        target: String,
        edge_type: String,
        valid_from: String,
        valid_to: String,
        responder: Sender<Result<()>>,
    },
    UpsertConcept {
        concept: ConceptUpsert,
        responder: Sender<Result<()>>,
    },
    WriteBulkAtomic {
        edges: Vec<EdgeAssertion>,
        responder: Sender<Result<usize>>,
    },
    RebuildCurrent {
        responder: Sender<Result<RebuildReport>>,
    },
    RegisterModel {
        model: ModelName,
        dim: usize,
        responder: Sender<Result<()>>,
    },
    Checkpoint {
        responder: Sender<Result<CheckpointReport>>,
    },
    Shutdown {
        responder: Sender<Result<()>>,
    },
}

Commands sent to the Write Actor on the high-priority channel (UI-driven work).

Variants

AssertEdge

Fields

edge: EdgeAssertion

responder: Sender<Result<()>>

RetireEdge

Fields

source: String

target: String

edge_type: String

valid_from: String

valid_to: String

responder: Sender<Result<()>>

UpsertConcept

Fields

concept: ConceptUpsert

responder: Sender<Result<()>>

WriteBulkAtomic

Fields

edges: Vec<EdgeAssertion>

responder: Sender<Result<usize>>

RebuildCurrent

Fields

responder: Sender<Result<RebuildReport>>

RegisterModel

Create a model’s embedding table and its DiskANN index (D-037, D-048).

High priority despite being setup work: it is one small transaction, and every embedding write for the model blocks on it, so queueing it behind a bulk job would stall the thing it gates.

Fields

model: ModelName

dim: usize

responder: Sender<Result<()>>

Checkpoint

Move WAL frames back into the main database file (§4.5, F-30, D-156).

High priority, and for once the reason is not latency: a caller asking for a checkpoint is asking for it now, usually at the end of a bulk load or before taking a copy of the file, and queueing it behind the background work it was meant to follow inverts the intent. It is also the only command here that is not a transaction.

Fields

responder: Sender<Result<CheckpointReport>>

Shutdown

Fields

responder: Sender<Result<()>>