Specification
Storage operations
Append, read, acknowledge, retain, compact — the operational contract.
This page will define the operational contract every Lakestream storage layer must implement: how data is appended, read, acknowledged, retained, and compacted. It matters because these are the verbs of the standard — the contract that lets a stream client and a table reader treat the same underlying storage as both a durable log and a compaction target.
Planned coverage
- Atomic append
- Mark-delete and acknowledgment (acks)
- Retention
- Compaction handoff
- Garbage collection (GC)
Source material
Documented in the ursa-storage repo, at project-docs/storage-operations-spec.md.