port: rendered pulse counted in their units; #4 refutes the voice value without fixing it

With their predicate the port's render is comparable to their capture for the
first time: pulse minimum 805 against their 714, peak 1420 against 1520, both far
above the 154 floor. So 'never goes off' holds in the port's own render.

My pulse is 24% shallower and I am NOT tuning it -- their own limit says the
counter is thresholded pixels, so a depth measured this way is a fact about the
threshold as much as the glow. The port draws the declared ramp.

#4: 148 s of the game's output, five of six channels distinct, no channel a copy,
largest pairwise correlation 0.70 between FL and FR. So presentation: loudest --
keeping one stream -- is refuted by what the game PLAYS, not merely suspected.

Stays unfixed on their instruction: the stream-to-channel mapping is not run, and
swapping one authored guess for another is worse than a guess that is labelled.
Also records that '6 channels' is Xenia's hardcoded default, not evidence of 5.1.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF

authored/audio.json

@@ -142,7 +142,37 @@
    "WHAT SETTLES IT: a recording of the game's own output over the intro,",
    "through the PulseAudio null sink (AUDIO-VERIFICATION section 3). Candidate",
    "combinations of the three decoded streams can then be correlated against",
-   "what the game actually played. Asked 2026-08-29."
+   "what the game actually played. Asked 2026-08-29.",
+   "",
+   "🔴 REFUTED FROM THE OUTPUT SIDE, 2026-08-30, not merely suspected.",
+   "",
+   "The RE agent recorded 148 s of the game's own output over the boot intro",
+   "(ALSA tee, --gpu=null, 0.15 % silence -- cleaner than the recipe page's own",
+   "reference run), with provenance from the XMA probe rather than a screenshot:",
+   "`ADV`'s three contexts appear byte-exact, then the `BGM_102` pair.",
+   "",
+   "FIVE OF SIX CHANNELS CARRY DISTINCT CONTENT. No channel is a copy of another;",
+   "the largest pairwise correlation is 0.70, between FL and FR, which is what a",
+   "stereo pair looks like. BR is 82 % silent and 11 dB down.",
+   "",
+   "So `presentation: \"loudest\"` -- keeping ONE stream -- cannot be right. That",
+   "was already labelled known-wrong here on the strength of the game decoding",
+   "all three concurrently; it is now refuted by what the game PLAYS.",
+   "",
+   "⚠️ AND IT IS STILL NOT FIXED, DELIBERATELY, on the RE agent's own instruction.",
+   "Three limits they state:",
+   "  * it does not make summing right -- the output is multichannel, which says",
+   "    nothing about which stream lands where;",
+   "  * '6 channels' is NOT evidence the game is 5.1 -- that count is Xenia's",
+   "    hardcoded kFrameChannelsDefault. The evidence is that five of them DIFFER,",
+   "    which a stereo guest cannot produce;",
+   "  * 🔴 the stream-to-channel mapping is NOT RUN. Cross-correlating each",
+   "    captured channel against each decoded `ADV` stream is the step that",
+   "    answers this, and it is their next iteration.",
+   "",
+   "Changing the mapping now would swap one authored guess for another, which is",
+   "a worse position than a guess that is labelled. The value stays; the label is",
+   "upgraded from suspicion to refutation."
   ],
   "presentation": "loudest",
   "presentation_why": [

docs/port/DECISIONS.md

@@ -9,7 +9,7 @@ dies, which is what this file is for.
 
 <!-- INDEX: generated by tools/port/index-decisions -- do not hand-edit -->
 
-124 sections. Search this before re-deriving anything.
+125 sections. Search this before re-deriving anything.
 
 * [P0 — the exporter, 2026-08-28](#p0--the-exporter-2026-08-28)
 * [P1 — Godot draws the screen, 2026-08-28](#p1--godot-draws-the-screen-2026-08-28)
@@ -135,6 +135,7 @@ dies, which is what this file is for.
 * [The plate pulses — measured, and the port was wrong on the boot's end state](#the-plate-pulses--measured-and-the-port-was-wrong-on-the-boots-end-state)
 * [A static overlay now advances, and a refutation attempt on the pulse floor](#a-static-overlay-now-advances-and-a-refutation-attempt-on-the-pulse-floor)
 * [Their pulse floor reproduces exactly once the predicate is named — 159, to the pixel](#their-pulse-floor-reproduces-exactly-once-the-predicate-is-named--159-to-the-pixel)
+* [My rendered pulse, counted in their units — and #4 refutes the voice value without fixing it](#my-rendered-pulse-counted-in-their-units--and-4-refutes-the-voice-value-without-fixing-it)
 
 <!-- /INDEX -->
 ## P0 — the exporter, 2026-08-28
@@ -7287,3 +7288,52 @@ single frame over threshold and caught the intro movie's green flashes ~6 s befo
 the title, in both legs. The presses were real — each skipped the rest of the
 movie, which is Q9's behaviour — but the pair tested nothing. A detector that can
 fire on one frame will fire on the wrong one.
+
+## My rendered pulse, counted in their units — and #4 refutes the voice value without fixing it
+
+### The pulse lands in the right range, and I am not tuning the depth
+
+Their predicate makes my render comparable to their measurement for the first
+time. Counting the boot's held title with `(g>130) & (g−r>45) & (g−b>45)` over the
+whole frame:
+
+| | theirs | mine |
+|---|---|---|
+| plate-absent floor | 154 | — |
+| pulse minimum | 714 | **805** |
+| pulse peak | 1 520 | **1 420** |
+
+✅ Same range, and both ends far above the floor — so **"never goes off" holds in
+the port's own render**, not just in their capture. The trace oscillates cleanly:
+`1413, 1359, 930, 857, 805, 830, 1182, 1413, …`
+
+⚠️ My pulse is **24 % shallower** (615 against 806). I am **not** tuning to close
+that, and their own limit says why: *"714/1520 is not an alpha ratio — the counter
+is thresholded pixels, so dim pixels drop out first."* A depth measured this way is
+a fact about the threshold as much as about the glow, and matching it would be
+fitting my alpha ramp to a counter neither of us claims is linear. The port draws
+the record's declared ramp.
+
+### #4 refutes the voice value from the output side
+
+They recorded 148 s of the game's own output over the boot intro — ALSA tee,
+`--gpu=null`, **0.15 % silence**, with provenance from the XMA probe rather than a
+screenshot. **Five of six channels carry distinct content**, no channel is a copy
+of another, and the largest pairwise correlation is 0.70 between FL and FR.
+
+🔴 So `presentation: "loudest"` — keeping **one** stream — cannot be right. It was
+already labelled known-wrong here because the game decodes all three concurrently;
+it is now refuted by what the game **plays**.
+
+✅ **And it stays unfixed, on their instruction.** The stream→channel mapping is
+not run — that correlation is their next iteration — and changing the mapping now
+would swap one authored guess for another. **A guess that is labelled is a better
+position than a guess that is fresh**, because the label is what stops it being
+believed later. `authored/audio.json` records the refutation and keeps the value.
+
+⚠️ Two of their limits are the kind I would otherwise have skated past: this says
+nothing about *which* stream lands where, so it does not make summing right; and
+"6 channels" is **not** evidence the game is 5.1 — that count is Xenia's hardcoded
+`kFrameChannelsDefault`. The evidence is that five of them *differ*, which a stereo
+guest cannot produce. The number of channels in a capture is a property of the
+capture.