3.2 KiB
Runtime Effect Kind-8 Tier2 Named Availability Note
This note records the current named-candidate availability comparison between the strongest title-overlap pair:
Louisiana.gmpDutchlantis.gmp
The comparison uses the checked rt3_105_save_name_table_probe surface from inspect-smp.
Immediate Result
Warehouse05 is not the differentiator.
Observed values:
Warehouse05Louisiana.gmp = 1Dutchlantis.gmp = 1
Port01Louisiana.gmp = 1Dutchlantis.gmp = 1
Furniture FactoryLouisiana.gmp = 1Dutchlantis.gmp = 1
FarmGrainLouisiana.gmp = 1Dutchlantis.gmp = 1
Logging CampLouisiana.gmp = 1Dutchlantis.gmp = 1
So the strongest current Louisiana -> Dutchlantis title overlap does not also come with a unique
Warehouse05 availability toggle that would directly explain the one-row
Add Building Warehouse05 dispatch cluster in Louisiana.gmp.
Full Named-Availability Differences
The current comparison shows 18 differing names:
AluminumMill:Louisiana = 0,Dutchlantis = 1AutoPlant:Louisiana = 0,Dutchlantis = 1Bauxite Mine:Louisiana = 0,Dutchlantis = 1Chemical Plant:Louisiana = 0,Dutchlantis = 1Farm Corn:Louisiana = 1,Dutchlantis = 0FarmCotton:Louisiana = 1,Dutchlantis = 0FarmRice:Louisiana = 1,Dutchlantis = 0FarmSheep:Louisiana = 0,Dutchlantis = 1FarmSugar:Louisiana = 1,Dutchlantis = 0Fertilizer Factory:Louisiana = 0,Dutchlantis = 1Iron Mine:Louisiana = 0,Dutchlantis = 1Nuclear Power Plant:Louisiana = 0,Dutchlantis = 1Oil Refinery:Louisiana = 1,Dutchlantis = 0Plastics Factory:Louisiana = 0,Dutchlantis = 1Recycling Plant:Louisiana = 0,Dutchlantis = 1Steel Mill:Louisiana = 0,Dutchlantis = 1Tool And Die:Louisiana = 0,Dutchlantis = 1Uranium Mine:Louisiana = 0,Dutchlantis = 1
Current Implication
The Tier 2 candidate/world-state rebuild strip remains plausible in general because it owns named
candidate availability seeding and refresh, but the current evidence no longer supports the narrow
claim that Louisiana.gmp gets its Add Building Warehouse05 row from a unique
Warehouse05 availability difference relative to Dutchlantis.gmp.
Two deeper grounded notes tighten that further:
structure_candidate_collection_rebuild_runtime_records_from_scenario_state0x00412d70does not consult the scenario-side recipe-book name at[state+0x0fe8]; it formats the rebuilt candidate display stem from one of two fixed built-in roots0x005c93d8or0x005c93e8plus the current ordinal.scenario_state_upsert_named_candidate_availability_record_and_refresh_runtime_filters0x00434f20now reads safely as a real boolean availability override writer rather than a wider mode enum.
So the next Tier 2 recovery question is now tighter still:
- whether the relevant difference is in broader candidate-state rebuild sequencing, latch refresh,
or cargo-membership/runtime-record reconstruction under
0x00437737 / 0x00412c10 / 0x00412bd0 / 0x00412d70 / 0x00412fb0, rather than in the direct named availability bit forWarehouse05itself.