From f095fe647f2b45f2260d824669eb4c3d3580d28f Mon Sep 17 00:00:00 2001 From: Sylpheed RE agent Date: Wed, 26 Aug 2026 02:10:14 +0000 Subject: [PATCH] re: the stage-02 "defaulted field" capture is wrong for 99 of 101 fields The last file still resting on the "defaulted on disc" premise. Re-checked through the 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, out of 101 listed. FiringRange was already recorded correctly elsewhere (runtime 0 is the accessor's miss value); SELength joins it. One pattern worth keeping rather than dismissing: 15 of the fields sit in exactly 5 objects each -- AB_* (afterburner), PowerCut*, AA_/AV_AxisMode_*. That is the Delta Saber family, so those fields are player-craft-only rather than defaulted, which is a different fact than either the file or my correction to it would suggest on its own. The runtime values themselves stay -- they are real measurements. What is withdrawn is the claim that the disc does not carry the fields. That completes the sweep: weapon-datasheet-runtime.md, unit-struct-runtime.md, live-unit-definitions.md, INDEX.md and now this capture all carried the same wrong premise from the same blind reader. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01PMRJjbxLqZtsb5Vb7KunPE --- ...stage02-defaulted-field-runtime-values.txt | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) 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