docs: promote +0x08 to confirmed, keep the frame-rate reading amber
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PMRJjbxLqZtsb5Vb7KunPE
This commit is contained in:
@@ -206,10 +206,13 @@ See [`structures/ui-composable-bundles.md`](structures/ui-composable-bundles.md)
|
||||
separation is *shape*, or which bundle references which, and the PAK cannot
|
||||
answer the latter directly because its entries are name-hashed.
|
||||
✅ **By-product:** the header is not dead space. `+0x18`/`+0x1c` are the
|
||||
**design resolution** (1280/720 on 98.7 %, asserted), and 🟡 `+0x04` takes only
|
||||
`0x3C0000`/`0x1E0000` — exactly **60.0/30.0 in 16.16** — with `+0x08` at
|
||||
30/1200/120/60, i.e. a frame rate and a duration in frames. That last reading
|
||||
is from the values alone and is unverified against an animation.
|
||||
**design resolution** (1280/720 on 98.7 %, asserted), and ✅ `+0x08` is the
|
||||
**animation length** — checked against the keyframe times, which it bounds in
|
||||
**2 313 of 2 313** bundles and is attained by **444**, with the ratio peaking
|
||||
at 1.0 rather than near zero (that histogram is what rules out a vacuous
|
||||
bound). 🟡 `+0x04` (`0x3C0000`/`0x1E0000` = 60.0/30.0 in 16.16) stays amber:
|
||||
the only supporting evidence is that the twelve 30.0 bundles cap at `+0x08`=30
|
||||
while the 2 843 60.0 ones reach 1 440. ❔ `+0x0c` and `+0x10` unexplained.
|
||||
See [`structures/ui-rat-layout.md`](structures/ui-rat-layout.md).
|
||||
* 🟡 **What `opt ` links — a record→record reference** (2026-08-24, measured
|
||||
disc-wide and asserted). All **1 467** links reachable from a declaration table
|
||||
|
||||
Reference in New Issue
Block a user