14 SEPTEMBER 2026 · capExpertAPI · CAP-2031 / CAP-680

What converts, and in what order

The backfill is a list of descriptors — one per column, or per key inside a document column, that holds a file path. Each names where its files are now, who they belong to, and where they go. This is that list, in the order the seeder walks it — every row says which column the value is read from and which account it is filed under.

Descriptors

122was 123 before QR came out

Wave 1 — own their files

6334 columns + 29 document keys

Wave 2 — borrow a destination

59all folder-derived

Owner fallbacks

36+2 that apply to all

Why there are two wavesseedAll()

The split is not about column shape. It is about who owns the file.

A borrowing key holds a path that some other column already owns — a vendor’s quote copied into a facility’s inventory record, say. It must not derive its own destination, because the account it would resolve is the account of the record holding the copy, not the account of the record that owns the file. So it looks the owning row up in the ledger and takes that row’s destination whole. That only works if the owning row is already there.

Inside a wave, descriptors are grouped by physical column and the groups run concurrently. Two descriptors naming one column run one after the other — without that, both pass the duplicate guard before either inserts, which was measured at 1,569 doubled reference keys and 3,196 extra rows.

The keys you named9 + 6

The nine you listed, then the mirrors that must follow them. The tag says which wave each falls in.

Where the owner falls back36 + 2

Every destination needs an account to file under. 36 of the 122 descriptors name more than one candidate and take the first that is set; two further fallbacks live in the seeder itself and apply to any descriptor.

Wave 1 — descriptors that own their files63

OWN_DESTINATION_DESCRIPTORS. The seeder runs all 63 as one wave. 34 read the path straight off a column (DIRECT_COLUMN_DESCRIPTORS); 29 read it from a key inside a document column where the file is that record’s own (OWNED_KEY_DESCRIPTORS). Value read from is blank wherever the descriptor name already says which column the value comes out of.

Wave 2 — keys that borrow a destination59

BORROWED_KEY_DESCRIPTORS. Every one is folder-derived: the module comes from the folder the file sits in, and the destination is taken from whichever wave 1 row owns it. A reference no row owns falls back to deriving its own. Value read from is blank wherever the descriptor name already says which column the value comes out of.