89 lines
3.1 KiB
Markdown
89 lines
3.1 KiB
Markdown
|
# Runtime Effect Kind-8 Tier2 Recipe-Book Note
|
||
|
|
|
||
|
|
This note records the current recipe-book comparison between the strongest title-overlap pair:
|
||
|
|
|
||
|
|
- `Louisiana.gmp`
|
||
|
|
- `Dutchlantis.gmp`
|
||
|
|
|
||
|
|
The comparison uses the checked `compare-recipe-book-lines` surface.
|
||
|
|
|
||
|
|
## Immediate Result
|
||
|
|
|
||
|
|
Unlike the named-availability table, the recipe-book surface differs heavily.
|
||
|
|
|
||
|
|
Observed high-level result:
|
||
|
|
|
||
|
|
- `matches = false`
|
||
|
|
- `content_matches = false`
|
||
|
|
- both files stay on `source_kind = recipe-book-summary`
|
||
|
|
- both files keep `book_count = 12`, `line_count = 5`, `book_stride = 0x4e1`, `line_stride = 0x30`
|
||
|
|
|
||
|
|
## Louisiana profile
|
||
|
|
|
||
|
|
`Louisiana.gmp` is sparse in this surface:
|
||
|
|
|
||
|
|
- only `book00` currently shows mixed line-area content
|
||
|
|
- the rest of the line areas are currently `zero`
|
||
|
|
- inside `book00`, only `line02` currently shows a nonzero mode word:
|
||
|
|
- `mode_word_hex = 0x00080000`
|
||
|
|
- `supplied_cargo_token_word_hex = 0x00004080`
|
||
|
|
- `demanded_cargo_token_word_hex = 0x00000000`
|
||
|
|
|
||
|
|
## Dutchlantis profile
|
||
|
|
|
||
|
|
`Dutchlantis.gmp` is much broader:
|
||
|
|
|
||
|
|
- many later books and lines remain `mixed` where `Louisiana.gmp` stays `zero`
|
||
|
|
- current explicit mode-word differences include:
|
||
|
|
- `book01.line02 = 0x001a0000`
|
||
|
|
- `book02.line02 = 0x00040000`
|
||
|
|
- `book03.line02 = 0x001a0000`
|
||
|
|
- `book06.line02 = 0x00010000`
|
||
|
|
- `book07.line02 = 0x00070000`
|
||
|
|
- multiple supplied-token lanes are also nonzero where `Louisiana.gmp` stays zero
|
||
|
|
|
||
|
|
## Current implication
|
||
|
|
|
||
|
|
This is the first strong Tier 2 discriminator between the strongest title-overlap pair:
|
||
|
|
|
||
|
|
- `Warehouse05` availability is **not** different (`1 / 1`)
|
||
|
|
- but the scenario-side recipe-book runtime inputs differ substantially
|
||
|
|
|
||
|
|
That strengthens the current bias toward the
|
||
|
|
`0x00435630 -> 0x00412d70`
|
||
|
|
side of the Tier 2 strip:
|
||
|
|
|
||
|
|
- `0x00435630` rebuilds the port/warehouse cargo recipe runtime tables from scenario-side recipe books
|
||
|
|
- `0x00412d70` then rebuilds candidate runtime records from scenario state
|
||
|
|
|
||
|
|
So the next Tier 2 recovery question should treat recipe-book/runtime-record sequencing as a more
|
||
|
|
likely differentiator for `Louisiana.gmp` than either title overlap or the direct named
|
||
|
|
`Warehouse05` availability bit.
|
||
|
|
|
||
|
|
## Same-condition-family contrast
|
||
|
|
|
||
|
|
The current recipe-side bias does not collapse to the shared condition family alone.
|
||
|
|
|
||
|
|
`Louisiana.gmp` and `Texas Tea.gmp` both currently sit on the same add-building condition family:
|
||
|
|
|
||
|
|
- `Louisiana.gmp`
|
||
|
|
- cluster:
|
||
|
|
`nondirect-ge1e-h0001-0007-0000-5200-0200-p0000-0000-0000-ffff :: [7:0]`
|
||
|
|
- label: `Add Building Warehouse05`
|
||
|
|
- row shape: `[0:8:0,0:8:0,0:8:0,1:2:-10,2:2:500000]`
|
||
|
|
- nonzero recipe modes: only `book00.line02 = 0x00080000`
|
||
|
|
- `Texas Tea.gmp`
|
||
|
|
- cluster:
|
||
|
|
`nondirect-ge1e-h0001-0007-0000-6d00-0200-p0000-0000-0000-ffff :: [7:0]`
|
||
|
|
- label: `Add Building Port01`
|
||
|
|
- row shape: `[0:2:25,0:8:0]`
|
||
|
|
- nonzero recipe modes:
|
||
|
|
`book00.line02 = 0x000a0000`,
|
||
|
|
`book01.line02 = 0x000a0000`,
|
||
|
|
`book02.line02 = 0x000a0000`,
|
||
|
|
`book04.line02 = 0x00050000`
|
||
|
|
|
||
|
|
So the current evidence says:
|
||
|
|
|
||
|
|
- shared `[7:0]` condition family is not enough to explain the shipped add-building row
|
||
|
|
- the recipe/runtime side is still map-specific even inside that same condition family
|