# Cut 1 migration table: R-heat fit and term counts
Date: 2026-09-18. Cut 1 of `docs/stats-and-power-cut.md`. Generated by a scratch migration console (two
phases, neither kept) against `GameData/Aetheria.cc` at pre-migration sha1 `d65c2aede2ee637fdb77fb83e6d7acd4d6c37cb3`
(12,682,424 bytes). The committed file's sha1 is `13a13a675064f971dfff3a3d83998220da42dd49` (12,682,737 bytes,
+313 for 51 authored `OptimalTemperature`/`PlateauWidth` float pairs).
**The pre-migration catalog does not open under the post-Cut-1 code.** Opening the unmigrated bytes with the
new `AetheriaStores.Open` throws immediately: `ClearPath: OptimalTemperature 0 lies outside its bounds
[223.15, 473.15]` -- `StatValidation` refusing the unauthored-default 0 for the very first design it checks.
This is why the schema change and the catalog rewrite are one commit, not two: there is no working
intermediate state. Keys 2-5 (the retired `HeatExponentMultiplier`/`DurabilityExponentMultiplier`/
`QualityExponent`/`FromRole`) are simply absent from the new `PerformanceStat` type, so CultCache's normal
slot-compatibility path (an unrecognized stored key is skipped, not an error) is what makes the *stat* fields
safe to drop silently -- it is `OptimalTemperature`/`PlateauWidth` on `EquippableItemData`, freshly required by
the new validation, that make a bare code swap without the catalog rewrite unusable.
**AetherDb invariants (`census`, `factions`, `dangling`, `station-fit`, `hardpoint-fit`, `loadout 1`) are
byte-identical before and after** -- captured with the pre-Cut-1 binary against the unmigrated copy and the
post-Cut-1 binary against the migrated copy, since neither binary can open the other's catalog shape. None of
these commands reads a stat value, so identical output is the expected proof that nothing but the stat/heat
shape moved.
- EquippableItemData records before: 51, after: 51 (must match -- the migration adds no records)
- Stats migrated into declared terms: 348 of 348 dumped
- Items fitted from an authored curve: 37; items with no curve (full-range plateau): 14
- Stat values at quality .5 / full durability / the item's own optimum: 281 of 348 unchanged, 67 diverge -- every divergence moves toward Max (the plateau's full-performance value), which is a move away from Min for an inverted stat (Max < Min) and reads as a negative delta below; max |delta| 72.8125
## Stats whose at-optimum value changed (the intended R-heat balance change)
| Item key | Path | Min-Max | Old value | New value | Delta |
## Re-authoring: Tractor Beam, 13 curve-less designs, and Earp/The Bat (operator ruling: "reauthor those items")
Written through the catalog's own types, in a scratch console over `Aetheria.Shared` (not committed; the
committed `GameData/Aetheria.cc` diff is the artifact). Every already-fitted design in the catalog shares the
exact same normalized curve shape -- optimum at 25.5% of the range above `MinimumTemperature`, plateau 12% of
the range wide -- regardless of hardpoint or behaviour, matching five distinct bound ranges to 5+ significant
figures. That is not rounding coincidence; it is one Bezier template authored once and reused catalog-wide, and
the 14 unauthored designs are simply the ones nobody assigned it to. Each row below applies that same fraction
to the design's own (unchanged, except Tractor Beam's) bounds, or points at the specific sibling design that
carries the identical bounds and therefore the identical fitted curve. All 16 records were validated
(`StatValidation.ValidateHeatResponse`) before any write reached disk; a failing record would have written
nothing.
| Item | What it is | Old bounds | Proposed (landed) | Why |
|---|---|---|---|---|
| Assembly Line | Tool-hardpoint facility gear, no active Behavior (a station production module) | 273.15-373.15, degenerate full-range plateau | Opt 298.65, PW 12 (bounds unchanged) | House-style fraction (25.5%/12%) over its own band; shares its exact bounds and prior placeholder shape with 4 sibling facility items below |
| Deep Ore Extractor | Same Tool/no-Behavior facility family | 273.15-373.15, degenerate | Opt 298.65, PW 12 | Same as Assembly Line -- identical bounds, identical fraction |
| Refinery | Same Tool/no-Behavior facility family | 273.15-373.15, degenerate | Opt 298.65, PW 12 | Same as Assembly Line |
| Shipyard | Same Tool/no-Behavior facility family | 273.15-373.15, degenerate | Opt 298.65, PW 12 | Same as Assembly Line |
| Surface Ore Extractor | Same Tool/no-Behavior facility family | 273.15-373.15, degenerate | Opt 298.65, PW 12 | Same as Assembly Line |
| Autocannon | Ballistic weapon, `AutoWeaponData` | 173.15-473.15, degenerate | Opt 249.65, PW 36 | Matches 6k Shooter, the only other design sharing this exact 173.15-473.15 band |
| Core Power | Reactor gear, `ReactorData`+`WearData` | 200-450, degenerate (old curve authored with 0 keys, old getter threw) | Opt 263.75, PW 30 | Matches Manhattan, the only other design sharing this exact 200-450 band |
| Industrial Thermostatic Heater | Tool-hardpoint heater, `ThermotoggleData`+`EnergyDrawData`+`HeatData` (it generates heat) | 150-400, degenerate | Opt 213.75, PW 30 | House-style fraction skewed toward the cold end, matching a device meant to run best where it is needed (cold) and degrade once its own output overheats it |
| LRMM72 | Launcher weapon, `LauncherData` | 223.15-473.15, degenerate | Opt 286.9, PW 30 | Matches GT 3K (`LauncherData`) and scorched void policy (`GuidedWeaponData`), both sharing this exact band with identical fitted curves |
| Large Drive | Thruster gear, `ThrusterData`+`WearData` | 200-400, degenerate | Opt 251, PW 24 | Matches deep space burnout, the only other design sharing this exact 200-400 Thruster band |
| plight | Energy weapon, `ChargedWeaponData` | 263.15-398.15, degenerate | Opt 297.575, PW 16.2 | Matches ColdFire and Spectra, both sharing this exact band with identical fitted curves (`AutoWeaponData`, but bounds -- not behaviour -- is what the shared template keys on) |
| Tractor Beam | Sensors-hardpoint gear, no active Behavior | -0 to -0, min==max==optimum, width 0 (S1: dead at every temperature) | Bounds 200-400 (newly authored), Opt 251, PW 24 | Never had real bounds authored at all; 200-400 matches the other small Sensors/gear family already using that exact range (not if i see you first, The Bat, Large Drive, deep space burnout), and the fraction gives it not-if-i-see-you-first's exact curve |
| Earp | Ballistic weapon, `InstantWeaponData` | 175-475, real 2-key curve peaking exactly at Minimum (dead at every temperature -- same bug class as S1, found while enforcing S5/S6's plateau-clamp rule) | Opt 251.5, PW 36 | House-style fraction over its own unique 175-475 band (no exact-bounds sibling exists); moves its peak off the lethal boundary the same way the 14 do |
| The Bat | Sensors-hardpoint gear, `SensorData` | 200-400, real fitted optimum 209, PlateauWidth 33 (pokes 7.5 past Minimum -- found while enforcing S5/S6) | PlateauWidth 18 only; optimum 209 unchanged | Minimal fix: shrink only the plateau to the largest width that clamps to the bounds with the authored optimum held fixed, preserving the one genuinely distinct fitted curve in this list |
## Zero consumables in the catalog
Cut 0 flagged that `ItemManager.CreateInstance` has no `ConsumableItemData` branch, so a `ConsumableItem` is
apparently never minted by the normal path, and asked whether Cut 1 should look before touching consumables.
**(probe)** The catalog holds **zero**`ConsumableItemData` records (`cache.GetAll<ConsumableItemData>().Count()
== 0` against `GameData/Aetheria.cc`). There is nothing to touch: no consumable design exists to migrate, to