re: the eight-value frame censused disc-wide, and my novelty claim withdrawn

Grepping FrameCount first would have saved the previous iteration an overclaim.

Withdrawn: the 8-value layout was not a discovery. stage-mission-tables already
documents Route_* records as (time, quat.x,y,z,w, pos.x,y,z) with
len(fields) == 8*FrameCount + 1 holding 1449 of 1449, and unit-group-table
already documents 1 + 8*FrameCount for formation slot lists. I re-derived the
shape from the asteroid tables and called slot 0 an "index" - it is the
corpus's time slot. Corrected in asteroid-fields.md. What the asteroid pass did
add is the norm test.

The census the corpus was missing: both prior statements were measured on one
table family each. Sweeping every IDXD record on the disc carrying a
FrameCount - 10986 records, 10974 with anon == 8 * FrameCount, and the entire
residual is 12 records: Formation_Fleet_01 (ratio 136) and Formation_Fleet_02
(ratio 4), six each, one per language pack. The two exceptions the doc already
names are the only two on the disc.

The quaternion is now measured, not asserted: over 78762 frames in five
families, |q| is within 1e-4 of 1.0 on 78762 / 78762.

Slot 0 is time only where something moves. It equals the running ordinal
0..N-1 in every formation (2196/2196), asteroid (384/384), placement (36/36)
and test-route (24/24) record, and in only 6228 of 8334 real routes - the one
family that stores true timestamps there.

Two record families new to the corpus: Placement_00..02 and RouteTest_00..01,
sharing a six-record template object whose sixth record is named Enumeration,
two such objects per language pack.

All fifteen artefacts byte-identical.
This commit is contained in:
Sylpheed RE agent
2026-08-28 02:20:15 +00:00
parent 01fbb42eb6
commit eaab3b1ead
3 changed files with 102 additions and 2 deletions

View File

@@ -5825,3 +5825,48 @@ list*, and why the group table needed both fields.
🟡 Not settled: whether the quaternion is object→world or world→object, and its
handedness — a norm test cannot separate those. And still: why `S28_p1` has an
asteroid volume with no definition.
---
## 🔴✅ 2026-08-28 — the eight-value frame, censused disc-wide (and my novelty claim withdrawn)
Item (a): apply the placement shape elsewhere. **Grepping `FrameCount` first
would have saved the previous iteration an overclaim.**
🔴 **Withdrawn: the 8-value layout was not a discovery.**
[[stage-mission-tables]] already documents `Route_*` records as
`(time, quat.x, quat.y, quat.z, quat.w, pos.x, pos.y, pos.z)` with
`len(fields) == 8·FrameCount + 1` holding **1449 of 1449**, and
[[unit-group-table]] already documents `1 + 8·FrameCount` for formation slot
lists. I re-derived the shape from the asteroid tables and called slot 0 an
**"index"** — it is the corpus's **`time`** slot. Corrected in
`asteroid-fields.md`. What the asteroid pass did add is the **norm test**.
**The census the corpus was missing.** Both prior statements were measured on
one table family each. Sweeping every IDXD record on the disc that carries a
`FrameCount`:
* **10 986** records carry one; **10 974** have `anon == 8 × FrameCount`.
* **The entire residual is 12 records**: `Formation_Fleet_01` (ratio 136) and
`Formation_Fleet_02` (ratio 4), six each — one per language pack. **The two
exceptions [[stage-mission-tables]] already names are the only two on the
disc.** "The common case, not universal" is now `10 974 / 10 986`.
**The quaternion is measured, not asserted.** Over **78 762 frames** in five
families, `|q|` is within 1e-4 of 1.0 on **78 762 / 78 762**. An arbitrary
4-tuple has no reason to land on the unit sphere.
🔑 **Slot 0 is `time` only where something moves.** It equals the running ordinal
`0…N1` in **every** formation (2 196/2 196), asteroid (384/384), placement
(36/36) and test-route (24/24) record — and in only **6 228 of 8 334** real
routes, which are exactly the family that stores true timestamps there
(`Route_ADN101_p1F`: t = 0, 20, 30). Read the slot as *time*; expect static
tables to degenerate it to an index.
**Two record families new to the corpus**: `Placement_00…02` and
`RouteTest_00…01`, sharing a **six-record template object** whose sixth record is
named `Enumeration`, two such objects per language pack. Nothing yet ties them to
a reader.
Written up in `docs/re/structures/stage-mission-tables.md`; `asteroid-fields.md`
carries the correction.