# Zero-fill filler policy

Option 1 emits an Original Xbox/XGD1 Redump-style 2048-byte-sector reconstruction.
Until a drive/workflow capable of reading the filler/padding regions is available,
the dumper intentionally writes synthetic zero-filled sectors for those ranges.

The generated `.media.json` records this explicitly under `reconstruction`:

- `filler_policy`: `zero_fill_until_drive_can_read_filler`
- `filler_verified_from_disc`: `false`
- `pending_hardware_capture`: `true`
- `filler_ranges[*].source`: `synthetic_zero_fill`

This keeps the image layout useful for emulator and reconstruction work while
avoiding a false claim that the filler ranges were physically captured.
