Where the payload lives is the constructor’s name, as in the C lifecycle verbs, so a residency an index lacks has no constructor to call.
Each takes only the placement its own hardware has, one shard per entry, and an empty list derives it.
inRam, err := usearch.DenseInitRam(options, []int32{0, 1}) // one graph per socketinVram, err := usearch.DenseInitVram(options, []int32{0, 1, 2, 3}) // sharded, never replicatedonGpu, err := usearch.DenseLoadVram("index.safegraphs", &usearch.DenseLoadVramConfig{Devices: []int32{0}})
An NVMe index is only ever viewed: external-memory graphs are never modified in place.
API
EnumResidencyResidency is where a handle keeps its payload, and where an executor computes and places the arenas it makes.1