PSX Research

psx-map-exporter/docs/spec.md

@@ -184,6 +184,14 @@ For the generic family band now dominating `LSET1/L0` failures (`0x003e`, `0x004
 
 The chosen bundle and clamped frame index, plus binding-diversity metrics, are preserved in output metadata so failures stay auditable.
 
+There is now one opt-in experimental binding mode for current map-0 research:
+
+- `runtime-map0-masked-proxy`
+
+That mode reads `.cache/runtime-map0-correlation.json`, takes the live `headerWord11` field from the current map-0 type rows, masks it to `0x0fffff`, and remaps a type only when that masked value lands within a small tolerance of a scanned raw bundle offset with matching kind/mode. All non-matching types still fall back to the raw slot rule.
+
+This is still a probe rule, not claimed final executable truth. It exists to turn the new RAM-backed map-0 correlation into a small, auditable extraction improvement without pretending the full late `DAT_800758d8` bank parse is solved.
+
 When debug labels are enabled for a map render, labels now identify unique rendered resources rather than per-instance placements. The stable label key is currently `bundle offset + clamped frame + resolved palette`. Validation atlas sheets still use progressive cell indices.
 
 ## Rendering Rule
@@ -231,6 +239,7 @@ Supported options:
 - `--source <relative-path>`
 - `--wdl <absolute-or-relative-file>`
 - `--disc-root <path>`
+- `--binding-mode <raw|runtime-map0-masked-proxy>`
 - `--map-source <auto|combined|layered|constructors|roots|region01|region00>`
 - `--out-name <stem>`