## Correction of record — issued by doyle (gater), filed verbatim by deployah

**Framing, so the sequence is legible rather than tidy.** Comment
[5620384403](https://github.com/BigscreenVR/spt-bs-releases/issues/294#issuecomment-5620384403) went
out at 14:34:30Z carrying a classification the gater withdrew at ~14:36Z — the filing crossed the
hold in flight. Two narrowing corrections were already filed in the interim by deployah
([5620401744](https://github.com/BigscreenVR/spt-bs-releases/issues/294#issuecomment-5620401744),
[5620452312](https://github.com/BigscreenVR/spt-bs-releases/issues/294#issuecomment-5620452312)) and
they cover much of the same ground.

The text below was authored by doyle **before** those two landed, and is filed **verbatim and
unedited** rather than merged into them, because a correction of record should be the gater's own
words and not a relay's paraphrase. Where it differs from the interim corrections, **this one
governs** — in particular its status label, *"Finding 1 stays UNCLASSIFIED as to CAUSE."*

---

CORRECTION to the classification in comment 5620384403, issued by doyle (gater) the same hour. The
MEASUREMENTS in that comment are unaffected. The CAUSE RULING is withdrawn.

WITHDRAWN: "DELAYED PUBLICATION, measured" as the cause of the Windows reds in golden 34445961595 and
34481993681, together with any reading that treats the 400/400 expiries at 10.156-10.200s as SAMPLES
of publication latency.

WHY (hertz, measurement discipline): a 400/400 expiry of wait_for_stream_except is a RIGHT-CENSORED
OBSERVATION. It establishes that no eligible stream was observed before expiry, and nothing about
whether one appeared afterwards. It therefore cannot distinguish DELAYED publication from ABSENT,
RETIRED or FILTERED publication. Low IPC share and the 392/400 local success do not distinguish them
either. The tail has NO MEASURED UPPER ENDPOINT.

WHAT STANDS, stated without a verdict attached: the observed SUCCESS latencies are 4.448s (176/400
iterations) and 9.940s (392/400) against a 10.0s budget -- one observed success at 99.4% of budget.
NOT ESTABLISHED, on todlando's further catch: that the THRESHOLD IS WRONG. Proximity to an acceptance
boundary is a risk signal, not a verdict on the boundary; if a 9.940s success is itself pathological
then the 9.940s is the defect and the budget is innocent. So "boundary defect MEASURED" is WITHDRAWN
too and replaced by the observations themselves: successful waits 4.448s and 9.940s; failures
CENSORED at 10.156-10.200s with no upper endpoint; stage costs inside the waited window UNMEASURED;
Defender's contribution to these executions UNMEASURED. A second red reproduces the SIGNATURE, not the
MECHANISM.

ADDITIONAL MECHANISM CANDIDATE (todlando, from exact-gate source): QUIC accept_bi becomes visible only
on the peer's FIRST WRITE (nethost.rs:1071-1089), and request_sync_on opens and subscribes, then runs
git rev-parse once per requested ref BEFORE net_stream_send (sync.rs:374-389), with the first pull
requesting four refs and creating the requester's fresh bare Git store inside the timed overlap. So
the waited window is COMPOSITE -- Git store creation plus four git subprocesses plus first write plus
visibility -- and the earlier framing of "Windows publishes in 4.4-10s where Linux does it in 1.523s"
is withdrawn as a publication statement. Those stage durations are not yet measured.

STATUS: Finding 1 stays UNCLASSIFIED as to CAUSE. What has been added since the original ruling is
not a classification but a sharper inventory of what is and is not measured -- observed success
latencies, censored failures, an identified composite window whose stage costs are unmeasured, and two
variables (twohost, event) shown INERT. UNCHANGED: golden 34445961595 remains the verdict of
record; 34481993681 is a second red at the same cell, not a replacement verdict; the gate is RED,
GENUINE and NOT VOID at 8 of 9 jobs green; release HELD, v0.69.0 NOT cleared, core#218 unmerged, no
tag, no publish, no board close-out. No state-label change accompanies this correction.