2.1 KiB
2.1 KiB
Runtime Effect Kind-8 Tier2 Setup Core Note
This note records the current setup-payload-core comparison across the six bundled add-building carrier maps:
Alternate USA.gmpChicago to New York.gmpLouisiana.gmpPacific Coastal.gmpRhodes Unfinished.gmpTexas Tea.gmp
The comparison uses the checked compare-setup-payload-core surface.
Immediate result
The upstream setup payload already differs across the carrier set.
Observed differing fields:
payload_word_0x14payload_byte_0x20payload_word_0x3b2candidate_header_word_0_hexcandidate_header_word_1_hex
Carrier-set shape
Current payload_word_0x3b2 values:
Alternate USA.gmp = 1Chicago to New York.gmp = 2Louisiana.gmp = 2Pacific Coastal.gmp = 1Rhodes Unfinished.gmp = 1Texas Tea.gmp = 3
That means Louisiana.gmp is not unique on payload_word_0x3b2.
Current candidate-header word pairs:
Alternate USA.gmp = 0x10000000 / 0x00009000Chicago to New York.gmp = 0x00000000 / 0x00000000Louisiana.gmp = 0xcdcdcdcd / 0xcdcdcdcdPacific Coastal.gmp = 0x00000000 / 0x00000000Rhodes Unfinished.gmp = 0x00000000 / 0x00000000Texas Tea.gmp = 0x00000000 / 0x00000000
So Louisiana.gmp is currently unique among the shipped carrier set on the candidate-header
sentinel pair, while Alternate USA.gmp stays separately unique on the recognized
rt3-105-map-container-v1 header pair.
Current implication
The upstream side of the Tier 2 strip is now bounded more tightly:
- the current
Louisiana.gmprecipe/runtime outlier status is not explained bypayload_word_0x3b2alone, becauseChicago to New York.gmpalso carries2 - but
Louisiana.gmpdoes stand out on the candidate-header sentinel pair
So the next Tier 2 upstream question is narrower:
- whether the unique
0xcdcdcdcd / 0xcdcdcdcdcandidate-header state inLouisiana.gmpis relevant to the coupled0x00435630 / 0x00412d70 / 0x00412fb0 / 0x00412c10rebuild strip, or whether it is only another container-side artifact unrelated to the shippedAdd Building Warehouse05row.