Skip to main content

Module buffer

Module buffer 

Source
Expand description

OperationBuffer — filesystem-backed write-ahead buffer for graph operations.

Stores GraphOp payloads as JSONL (one JSON object per line). Operations are buffered when the store isn’t available (e.g., boot time) and drained into a live store when it becomes available.

The buffer stores raw operations, not entries. No hash, no clock, no parents. These are assigned at drain time through the normal store API. This means:

  • Ontology validation happens at drain time, not buffer time
  • HLC timestamps reflect drain time, not event time
  • Subscriptions fire at drain time
  • No sync participation (buffer is local, pre-store)

Callers should store real event timestamps in operation properties (e.g., {"timestamp_ms": 1711526400000}) for audit accuracy.

Structs§

OperationBuffer
Filesystem-backed buffer for graph operations.