SlateDB storage engine — implementation plan

Warning

This is not authoritative documentation. It describes a plan of work that is not yet implemented and will change as it lands. Once the work is complete these documents should be removed; the finished system is described by the SlateDB storage engine spec, the plugin’s user documentation, and the repos themselves.

Tactical companion to the SlateDB storage engine spec. The spec covers the design and the why; these are the task handoffs — each self-contained, each landing green, with commit boundaries and verification requirements stated per task.

Critical chain: 1 → 2 → 3 → 4 → 5, then 6; task 7 floats after 5. Tasks 1–4 deliver a working single-index engine under autocommit; task 5 delivers multi-statement transactions with honest semantics; task 6 adds secondary and unique indexes; task 7 is DROP reclamation and operational polish.

• Task 1: slatedb-capi shim, container image, and spike
• Task 2: the memcomparable key codec and row value codec
• Task 3: plugin skeleton, metadata, and DDL
• Task 4: cursor read and write paths, autocommit, primary key only
• Task 5: multi-statement transactions
• Task 6: secondary indexes, unique and non-unique
• Task 7: DROP reclamation, fencing behavior, and operational surface