Half-baked ideas in progress.

Documents here are not held to the separation the rest of the hub observes: they may mix normative rules, language-agnostic algorithms, and Rust-specific details freely, because working out which is which is usually the last step rather than the first.

Nothing here is adopted. When a draft settles, it is split along the usual seams and moves into Specification, Implementation and kladde-rs — or, if it is rejected, into Superseded with the reasoning intact. The proposal of the file as one sequence settled that way: its content is now the specification’s sequence and span table and the pages around them. So did the proposal of payload pages, which write a large transaction’s bytes once: it is now the journal’s external bytes, with their place in durability, the flush and the store’s policy.

Most drafts below were written against the design it replaced, of allocations and an address table, and describe that design where they say “today”; their ideas about consolidation’s policies carry over to pages of spans, and those about allocations, statements and places do not.

Current drafts

draftstatus
Open issuesan audit: where the other documents contradict each other, and what blocks a first prototype
The Move operationthe record is specified; how a flush states it is sketched, with the open questions listed but not answered
Segmentsa direction, not yet a design
Cleaning by ripenessa proposal: clean each page once waiting no longer pays, judged by how fast it still drains
Bayesian ripenessa proposal on top of it: keep a posterior over each page’s drain, for either variant of the draft, and decide from the posterior
Sorting survivors by temperatureanother idea for reducing file size, orthogonal to how ripeness is estimated: try to avoid creating pages that mix cold chunks with chunks that are still draining.
Variable-size valuesa proposal: separate how many bytes a value’s encoding takes from how much room its place reserves; packed places unpad enums, write integers and pointers as varints, and admit small strings and vectors that keep short content inline
Sparse leaves, and consolidation from the statements upa finding, resolved: leaves stayed far emptier than data pages because consolidation interleaves choosing victims, deriving statements, and laying them out; the newest size wins ended the pile-up of nearly empty leaves, and dropping the fill floor on retiring leaves ended their staying half empty; and a redesign from the address table’s logical level that keeps the three apart
Splices without restating the taila proposal for the address table: seven ways to state a splice without restating what lies behind it, measured on kladde-svg and on typing; recommends linked spans over backings, which the adopted design took further
A C++ implementationa proposal for the high-level design of kladde-cpp: a describing macro now and reflection later in place of #[derive(Durable)], enums from enum class, std::variant and class hierarchies, handles that outlive an edit, and four changes to the specification that a second language suggests

Open issues is the odd one out: it is not an idea in progress but a standing list, and it is kept here because it is maintained by audit and goes stale the moment the documents it indexes are edited.