Design enhancement proposals
A design enhancement proposal (DEP) is a page that argues for one change to the design of datarecord before the code makes it. A key of the schema, the format on disk, the RecordLike protocol, the fold and the API each change through a DEP. Its reader is a contributor who was not in the discussion.
The contributing guide sets the process: how to number and write a DEP, its statuses, and what moves where when it lands. To start one, copy the template.
Once a DEP has landed, it stays as the record of the argument. Where the pages it landed in and the DEP differ, follow those pages. A number is never reused, even when its PR closes, so the table has gaps.
| DEP |
Title |
Status |
Superseded by |
| 1 |
dims, mappings, groups and traits |
Implemented (2026-08-16) |
DEP 16 (in part), DEP 20 (in part) |
| 2 |
groups, one construct for classification and sparsity |
Superseded (2026-10-26, implemented 2026-09-01) |
DEP 23 |
| 3 |
trait switches, a trait a component opts into |
Superseded (2026-10-20) |
DEP 16 |
| 4 |
staging as a layer, one fold, two sources |
Implemented (2026-09-01) |
DEP 20 (in part) |
| 5 |
one Record, over a NodeCache |
Superseded (2026-10-21, implemented 2026-09-01) |
DEP 19 |
| 6 |
a member file contains values, and nothing else |
Superseded (2026-10-13, implemented 2026-09-04) |
DEP 12 |
| 7 |
staging without _seq |
Implemented (2026-09-02) |
|
| 8 |
one interface over two objects: a source returns its own rows, and a fold returns the resolved rows |
Superseded (2026-10-21, implemented 2026-09-04) |
DEP 19 |
| 9 |
a Workspace holds the connection, a Store holds a location |
Implemented (2026-10-10) |
|
| 10 |
a group is one struct column |
Superseded (2026-10-26, implemented 2026-10-12, amended 2026-10-13) |
DEP 20 (in part), DEP 23 |
| 11 |
deletion cascades through tombstones, not through filters |
Implemented (2026-10-13) |
DEP 20 (in part) |
| 12 |
properties, metadata declared apart from data |
Implemented (2026-10-13, steps 1 and 2) |
|
| 13 |
buses and carriers are dims |
Implemented (2026-10-15) |
|
| 14 |
combining a record with an extension |
Rejected (2026-10-20) |
|
| 15 |
a dim is flat |
Implemented (2026-10-20) |
|
| 16 |
remove traits |
Implemented (2026-10-20) |
|
| 17 |
results are attributes |
Implemented (2026-10-20) |
DEP 20 (in part) |
| 18 |
drop narwhals |
Implemented (2026-10-20) |
|
| 19 |
one Record and a package layout |
Implemented (2026-10-21) |
DEP 20 (in part) |
| 20 |
a layer restates an axis whole |
Implemented (2026-10-22) |
|
| 21 |
the owner map contains keys as written |
Implemented (2026-10-25) |
|
| 22 |
a layer restates membership whole |
On hold (2026-10-22) |
|
| 23 |
multi-dims replace groups |
Implemented (2026-10-26) |
|
| 24 |
categories are enum dimensions |
Implemented (2026-10-26) |
|
| 25 |
each layer has its own manifest |
Implemented (2026-11-03) |
|
| 26 |
the fold reads each layer under its own schema |
Implemented (2026-11-03) |
|
| 31 |
select returns a view of a record's labels |
Implemented (2026-11-04) |
|
| 33 |
the fold is a fixed plan |
Implemented (2026-11-03) |
|
| 34 |
register creates one view per relation |
Implemented (2026-11-03) |
|
| 35 |
the workspace keeps the tables a record reads |
Draft (2026-11-04) |
|