From ddd0d5b4b77a0eaa208301affc0627139d219c75 Mon Sep 17 00:00:00 2001 From: Sylpheed RE agent Date: Wed, 26 Aug 2026 01:53:59 +0000 Subject: [PATCH] re: the weapon DATA SHEET's "defaulted on disc" premise is false Every field weapon-datasheet-runtime.md calls defaulted is on the disc. The record table reads them directly; the old string-pool reader could not see a value whose string is shared or reordered and reported it absent. Verified against the disc myself rather than adopted: wep_05_ASMissile TriggerShotCount (defaulted) -> 4 wep_60_ASMissile TriggerShotCount (defaulted) -> 4 wep_02_Missile Power (defaulted) -> 100.0 [Shell] wep_60_ASMissile Power (defaulted) -> 1000.0 [Shell] wep_25_HBeam MaximumRange (defaulted) -> 4000.0 [Shell] wep_11/28/36/70 LoadingCount (defaulted) -> 6/5/5/0 Two consequences recorded: * The hypothesis "the title-code default for TriggerShotCount is 4" answers a question that does not exist -- both weapons state 4 explicitly. * The bracket "wep_60_ASMissile's defaulted Power sits in the C band (150-500)" is refuted: it is 1000.0, outside the band. That also puts a question over the bucket model or over that row's identification. What is NOT withdrawn: the runtime capture itself. Every number it read matches the disc. What goes is the reason for taking it -- the Gallery panel was not recovering values the disc lacks, it was reading values our parser was missing. Still useful as an oracle, redundant as a source. Correction banner at the top; the original document is left intact beneath it. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01PMRJjbxLqZtsb5Vb7KunPE --- docs/re/weapon-datasheet-runtime.md | 30 +++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/docs/re/weapon-datasheet-runtime.md b/docs/re/weapon-datasheet-runtime.md index c68ff91..93a81c4 100644 --- a/docs/re/weapon-datasheet-runtime.md +++ b/docs/re/weapon-datasheet-runtime.md @@ -1,5 +1,35 @@ # Weapon DATA SHEET — runtime capture (Route B) +> ## ❌ CORRECTION (2026-08-26) — the premise is false +> +> **The fields this document calls "defaulted on disc" are on the disc.** The +> [record table](structures/idxd-container.md) reads them directly; the old +> string-pool reader could not see a value whose string is shared or reordered, +> and reported it absent. Verified against the disc: +> +> | weapon | field | this doc | **on disc** | +> |---|---|---|---| +> | `wep_05_ASMissile` | `TriggerShotCount` | *(defaulted)* | **4** | +> | `wep_60_ASMissile` | `TriggerShotCount` | *(defaulted)* | **4** | +> | `wep_02_Missile` | `Power` | *(defaulted)* | **100.0** (`Shell`) | +> | `wep_60_ASMissile` | `Power` | *(defaulted)* | **1000.0** (`Shell`) | +> | `wep_25_HBeam` | `MaximumRange` | *(defaulted)* | **4000.0** (`Shell`) | +> | `wep_11` / `28` / `36` / `70` | `LoadingCount` | *(defaulted)* | **6 / 5 / 5 / 0** | +> +> Two consequences: +> +> * ❌ The ❔ hypothesis *"the title-code default for `TriggerShotCount` is 4"* +> answers a question that does not exist — both weapons state 4 explicitly. +> * ❌ The 🟡 bracket *"`wep_60_ASMissile`'s defaulted `Power` sits in the C band +> (≈ 150…500)"* is **refuted**: it is **1000.0**, outside the band. That also +> puts a question over the bucket model, or over that row's identification. +> +> The **runtime capture itself stands** — every number it read matches the disc. +> What is withdrawn is the reason for taking it: the Gallery panel was not +> recovering values the disc lacks, it was reading values our parser was missing. +> As an oracle it is still useful; as a *source* it is now redundant. + + **Status:** 🟡 first dynamic capture, 2026-07-28. The Arsenal's *Gallery Mode* panel is a direct runtime readout of the IDXD weapon record, which makes it an oracle for the fields the disc leaves **defaulted**. Two field mappings are ✅ `CONFIRMED`; two defaulted values