Stream-verify the demo scenes: warp field + Klingon = DRAM-resident assets

trek's live-written DMA stream contains ZERO non-standard SENDs (624 pairs, all
four standard payloads) -- the captured demo frames, like the bench, draw only
the SMPTE test card. The warp starfield and Klingon vessel geometry are the
demos' scene ASSETS resident in render memory (compiled coefficient blocks
never referenced by the captured frames' chains). §07 relabeled accordingly:
"Recovered assets -- the Star Trek material". Every image in the readout is now
attributed by stream evidence, not memory scanning.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Cyd
2026-07-17 12:57:25 -05:00
co-authored by Claude Opus 4.8
parent 70a7d38329
commit 2a11838d74
+16 -16
View File
@@ -388,29 +388,29 @@
</section>
<section>
<h2><span class="idx">07</span> The warp field — a Star Trek scene, recovered</h2>
<p class="sub">The archive's <span class="mono">trek</span> capture — unreleased Star Trek
material — <b>replays and draws</b> after the dual-instruction-mode fix. Walking the
per-region DMA chains in the bin pages enumerated <b>898 compiled payload programs</b> for
the frame: four are the standard end-of-frame pipeline (fog, texture, RGB — byte-identical
in every capture), and <b>~860 are the scene itself</b>, per-primitive coefficient blocks
with their geometry sitting in plain screen-space floats. Plotted below:
<b>433 star positions and 389 streaks</b>, radiating from a convergence point — the
<b>warp-speed starfield</b>, reconstructed from micro-code compiled by the board's own
firmware running on the emulated i860.</p>
<h2><span class="idx">07</span> Recovered assets — the Star Trek material</h2>
<p class="sub">The archive's <span class="mono">trek</span> and <span class="mono">klngvid</span>
captures — unreleased Star Trek material — replay after the dual-instruction-mode fix, and
their render memory holds <b>~860 compiled per-primitive payload blocks</b> beyond the
standard program. Stream-verification shows the captured frames themselves draw only the
test card (§06) — these blocks are the demos' <b>scene assets, resident in DRAM</b>:
compiled geometry awaiting draws that this recording never reached. Recovered below:
<b>433 star positions and 389 streaks</b> radiating from a convergence point — a
<b>warp-speed starfield</b> — and a vessel scene, both read from coefficient blocks compiled
by the board's own firmware on the emulated i860.</p>
<div class="hero-render" style="margin-top:16px">
<span class="tag">recovered from the frame's compiled payload programs</span>
<canvas id="trekframe" width="832" height="512" aria-label="the warp starfield recovered from trek's compiled frame"></canvas>
<div class="cap"><b>trek at warp</b> — every point and streak is one primitive's
position read from its compiled coefficient block (fields +0x14/+0x18 and +0x24/+0x28,
plain IEEE floats in screen space).</div>
<div class="cap"><b>the warp starfield asset</b> — every point and streak read from one
compiled coefficient block (plain IEEE floats). Resident in trek's render memory;
not referenced by the captured frames' chains.</div>
</div>
<div class="hero-render" style="margin-top:14px">
<span class="tag">same recovery · the Klingon capture</span>
<canvas id="klngframe" width="832" height="512" aria-label="the Klingon scene recovered from klngvid's compiled frame"></canvas>
<div class="cap"><b>the Klingon scene</b> — 96 positions and 62 edge segments: a sparse
starfield with a dense tangle of intersecting edges right-of-center — <b>a vessel</b>,
recovered by the identical chain-walk from the <span class="mono">klngvid</span> capture.</div>
<div class="cap"><b>the Klingon scene asset</b> — 96 positions and 62 edge segments: a sparse
starfield with a dense edge tangle right-of-center — <b>a vessel</b>, recovered from the
<span class="mono">klngvid</span> capture's render memory (same resident-asset status).</div>
</div>
</section>