diff --git a/docs/re/captures/stage02-defaulted-field-runtime-values.txt b/docs/re/captures/stage02-defaulted-field-runtime-values.txt
index d852adc5..374758bf 100644
--- a/docs/re/captures/stage02-defaulted-field-runtime-values.txt
+++ b/docs/re/captures/stage02-defaulted-field-runtime-values.txt
@@ -1,3 +1,28 @@
+# ❌ CORRECTION (2026-08-26) — "the disc record DEFAULTS the field" is false
+# for 99 of the 101 fields listed below.
+#
+# Re-checked through the IDXD record table over every unit-like object on the
+# disc (114 with a Generic.Type of Craft or Vessel):
+#
+#     present in ALL 114 objects .......  50
+#     present in some ..................  49
+#     present in NONE ..................   2   <- FiringRange, SELength
+#
+# So only `FiringRange` and `SELength` are genuinely absent. `FiringRange` was
+# already recorded correctly elsewhere (runtime 0 is the accessor's miss value);
+# `SELength` joins it.
+#
+# The old string-pool reader could not name a record, so a per-record field read
+# as absent. See docs/re/structures/idxd-container.md and
+# docs/re/idxd-legacy-reader-audit.md.
+#
+# One pattern worth keeping: 15 of the fields sit in exactly 5 objects each --
+# AB_* (afterburner), PowerCut*, AA_/AV_AxisMode_*. That is the Delta Saber
+# family; those fields are player-craft-only, not "defaulted".
+#
+# The runtime values below are still real measurements. What is withdrawn is the
+# claim that the disc does not carry the fields.
+#
 
 map check: 406 fields agree with the disc, 0 disagree