the protocol's date-carved holdout
Readonlycutoff: stringReadonlydateColumn: stringReadonlyholdoutEnd: stringOptional end (exclusive) of the holdout window; rows on or after it are in neither role (it reproduces the reference pipeline's holdout keys).
Readonlykind: "date-carved"ReadonlynewEntityReport: { groupKey: string; holdoutFraction: number }the unit's decision period, the slice each holdout period summarises
StaticGroupSHA-256 (lower-case hex) of a set of group keys as the new-entity summary stores it: the distinct keys (the unit row's
group key, as the carve groups rows), sorted with OrdinalCompare, joined with \n, UTF-8.
The date carve: rows whose carve date is on or after the cutoff (and before
holdoutEnd, when set) are the locked holdout, earlier rows are development, later rows are left out of the snapshot and counted. The carve date is the unit row's decision date when the protocol'sdateColumnisDecisionDate, else the row's own field of that name. The carve groups rows by the unit row's group key, so a new-entity report holds out whole groups (the unit's group key value, or the row's entity key when the unit declares none; a protocol whose report names another key is refused before any row is read).