fabi/Syplheed-Reborn
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

re: the Enumeration self-index is not a naming route, and the residual is two _Test variants

Browse Source 
The tempting move - 360 objects state their own contents, so use that to name
them - does not work, and it is now measured rather than assumed:

  objects carrying an Enumeration record                       360
     key already named by archive-naming routes 1 + 2          348
     still unnamed                                              12
     newly named by name_hash(prefix + own record name + ext)    0

Sixteen prefixes x seven extensions x every record name of every unnamed
object: zero gained. A self-index names an object's RECORDS; a TOC key is
name_hash(path + file name). The two vocabularies never meet.

The residual is exactly two objects x six packs, each byte-identical across the
packs and each an unnamed VARIANT of a named _Test table, not a duplicate:

  2390212806 (1493 B)  Placement_00..02 + RouteTest_00..01 - a trimmed
                       Stage\Null_Test.tbl (3121167452, 27545 B, same five
                       records plus four Frame_Test_Asteroid_*)
  2719765792 (14124 B) Formation_100, Formation_Fleet_01, Formation_Fleet_02 -
                       the same three record names as Formation_Test.tbl
                       (3463590559, 14025 B) but a different payload

That answers the previous iteration's question about the six-record
Placement/RouteTest sibling: it is Null_Test.tbl minus the asteroid frames.

Independent confirmation for stage-mission-tables: name_hash(prefix +
"Formation_Test.tbl") -> key 3463590559, whose records are exactly those three,
so the two frame-ratio exceptions do live in the file it names.

Dangling link recorded, not fixed: idxd-container.md references
idxd-unnamed-keys.md twice and that file does not exist on this branch - it
belongs to auto/idxd-unnamed-keys.

One control missed unexplained: EnumSquadron_Test.tbl matches no pak key under
any of the sixteen prefixes. n=1, not chased.

All fifteen artefacts byte-identical.
This commit is contained in:
Sylpheed RE agent
2026-08-28 02:57:20 +00:00
parent 027e6bb7a7
commit e222016dfc
2 changed files with 89 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

39
docs/re/structures/idxd-container.md
View File

@@ -197,3 +197,42 @@ declaration table — and the spelling is the only thing that distinguishes them
[[mission-wave-arrivals]] counted 28 `Enumeration_*` records while filtering
non-route records out of a speed measurement; what it does not say is what they
are.
### ❌ The self-index is not a naming route — measured, 0 gained
Tempting next step: 360 objects state their own contents, so can that name the
objects themselves? **No.**
```
objects carrying an `Enumeration` record 360
key already named by archive-naming routes 1 + 2 348
still unnamed 12
newly named by name_hash(prefix + own record name + ext) 0
```
Sixteen path prefixes × seven extensions × every record name of every unnamed
object: **zero**. A self-index names an object's **records**; a TOC key is
`name_hash(path + file name)`. The two vocabularies never meet, and no amount of
record names reaches a file name. A measured negative.
✅ **The residual is exactly two objects, each repeated once per language pack,
and each is an unnamed variant of a named `_Test` table** — byte-identical across
all six packs, and *not* a duplicate of its named counterpart:
| key | size | records | its named counterpart |
|---|---:|---|---|
| `2390212806` | 1 493 B | `Placement_00…02`, `RouteTest_00…01` | `Stage\Null_Test.tbl` = `3121167452`, 27 545 B — **the same five records plus four `Frame_Test_Asteroid_*`** |
| `2719765792` | 14 124 B | `Formation_100`, `Formation_Fleet_01`, `Formation_Fleet_02` | `Formation_Test.tbl` = `3463590559`, **14 025 B — the same three record names, a different payload** |
So one is a trimmed `Null_Test`, the other a second `Formation_Test`-shaped file.
Neither name resolves under any of the sixteen prefixes with the eight candidate
spellings tried.
This also confirms [[stage-mission-tables]]'s attribution independently:
`name_hash(prefix + "Formation_Test.tbl")` → key `3463590559`, whose records are
exactly `Formation_100`, `Formation_Fleet_01`, `Formation_Fleet_02` — the two
frame-ratio exceptions really do live in the file it names.
❔ One control threw an unexplained miss: **`EnumSquadron_Test.tbl`**, named by the
`_Test` stage record, matches **no pak key** under any of the sixteen prefixes.
n = 1, not chased.