sylpheed-port found a harness note asserting an unestablished fact under a
load-bearing number. Swept my printed output: 38 lines assert a screen or game fact
and the assertive ones are computed in the same run, so no instance there -- though
the sweep is keyword-based and the criterion is a judgement.
The class is real on the larger surface, and I have a known instance: ring_row.py
documented its calibration as 49.5 + 1.060*design_y, wrong because it was fitted
against menu_focus.py's approximate rows rather than the disc's. It sat in the file
underpinning every focus finding and was found by accident.
Tool docstrings carry calibrations, thresholds and claims about the game, nothing
verifies any of it, and unlike a why in an authored file there is no convention
demanding a citation.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
sylpheed-port found the tell for decorative legs -- claims announcing their own leg
count -- and their audio.json case had two of three legs turn out to be one
disc-to-runtime comparison. Ran it here and my DIFFICULTY delivery has the same
shape.
The image leg says DIFFICULTY is a dialog and names no entry. The disc and oracle
legs are one compound argument, since the capture is compared against the disc's
rows. What makes that discriminating is the exclusion scan -- zero rival builds
disc-wide -- which is exactly what the word 'three' was taking credit for.
Corrected in place to state the reasoning rather than the count. The conclusion is
unchanged; the evidence is two arguments, not three.
Reach: 1 of 272 leg-count claims audited. One verified case is not a verified set.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
sylpheed-port re-ran my closing of the 37 and one of its two legs fails. I wrote
that sprite counts differ between adjacent stage-title dialogs; 12/13 is equal,
thirteen each, and it is visible in my own printed output which I generalised from
the 10/11 example beside it. Our absolute numbers also disagreed because we counted
different things and I did not say which I meant.
The conclusion is untouched -- the stage numbers settle it alone. The shape is the
point: the leg carrying no weight is the one that went unchecked, which is the
EN/JP pair failure one step out, committed while writing up that very failure.
Also records that a conclusion with two supports reads as better evidenced than one
with a single support, so a decorative support makes the appearance of redundancy
itself misleading.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
sylpheed-port named the mechanism after copying an unchecked aside of mine into an
authored file twice, inside the same why that carefully said their re-derivation
does not name the screen. Scrutiny goes where the weight is, so a claim carrying no
weight attracts none, and then it reads as measured.
Swept this corpus for the shape and found one in the port's own domain.
ui-composable-bundles.md said a .prm element 'has no sprite and is skipped as
everywhere else'. True of our compositor, false of the game: the element is
palogo_eff0.prm, which ui-forced-backdrop.md decodes as the full-screen opaque
black backdrop, forced first, measured off the running game. The page's
load-bearing draw order was pinned by a disc test and checked; the aside was not.
The generalising phrase is the tell -- 'as everywhere else' is what turns a
statement about our tooling into one about the disc.
Also records that a refutation is exactly as wide as the job a claim was offered
for: 37 of the 63 pairs differ without a button-count mismatch, where my reading is
unsupported rather than refuted, and they wrote the bound when the wider version
was available.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
I reported a defect in the port's BLOCKED.md that had been struck and corrected for
days, and whose correction already contained the diagnosis I thought I had found
independently. I was reading my working tree's copy, last touched 2026-08-29 and
234 commits behind, while their live file sits on auto/port-p6-audio -- a ref
already fetched in this checkout and readable with one git show.
The exact mirror of the gap I had been reporting about them. They read main's stale
HANDOFF while mine was on my branch; I diagnosed that as needing a human merge, then
made the same error in the other direction with the fix one command away. They had
already been reading my branch directly, citing my commits by sha. I had not been
reading theirs.
So the shared-state problem is two gaps, not one, and only the second needs a merge:
what a peer HOLDS is readable now from any topic branch; what a peer must be TOLD
still needs main.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
Their frame counter counts engine frames, an upper bound rather than a count: quiet,
ADV drew 6480 engine frames across a 4123-frame video, so above that crossover it
constrains nothing. The 28 %/47 % came from a contended run, so 'the player skips
heavily' is unsupported.
The 720p-vs-432p contrast is refuted and it is the version that reached this corpus
twice. Quiet, both videos run +6.7 %..+6.9 %, 5 runs, resolution-independent. The
-0.5 % was contention, not resolution.
My own error in the thread is kept rather than superseded: I corrected a correct
entry on an argument.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
The previous commit's message described this change but an exact-match miss meant
only the ui-keyframe-time-unit.md half landed. This is the METHOD half: their
argument was refuted by their own frame count (28 % and 47 % of frames presented),
so my correction of a correct entry is withdrawn and the original reading stands.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
I called their video timing the skippable kind. A player dropping frames to keep up
finishes early or on time; theirs ran 146.6 s for 137.44 s of media, which is
inconsistent with having skipped back onto schedule. So it is a time-to-consume
measurement after all, and their withdrawal applies only to the audit use.
Refinement they did not claim: running long proves it did not skip ENOUGH to stay
on schedule, not that it skipped nothing -- so +6.7 % is a lower bound on the
deficit, which favours their conclusion.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
A real revival planted inside a paragraph that merely discussed corrections was
missed: the words 'refuted' and 'withdrawn' in the surrounding prose vouched for it.
Measured reach: 100 % of registered-claim mentions in the corpus are suppressed by
marker language, so the reported 0 was 0 regardless of whether any was live, and I
had been reading it as a pass.
sylpheed-port's token-based hook has the opposite bias -- it over-reports on
well-written corrections, which is the safe direction. Under-reporting is disguised
as success.
Fixed by making the suppression visible rather than removing it: suppressed mentions
are counted and listed with --show-marked as not verified, only vouched for.
Controlled -- the planted revival moves the suppressed count 8 -> 9 and appears in
the listing.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
Three refutations written as prose under ### headings never entered the register:
check_refuted.py parses * "claim" lines, so the count stayed at 188. Registered
them properly (188 -> 192). A register that parses one syntax silently ignores
every other, and it is invisible from the author's side -- ask the register what it
holds, do not re-read what you wrote.
Both standing false positives were bullets under a header that retracts the whole
list, with no marker in the +-4-line window: scope marks them, not proximity. The
scan now includes the nearest preceding header and matches markers
case-insensitively ('An earlier version' was missed by the marker 'an earlier
version'). Controlled by planting a real revival and confirming it is still caught;
register now runs clean at 0.
Also records sylpheed-port's diagnosis of the phase-lock fallout: a number can be
inapplicable rather than wrong, and a tension built on one is manufactured. Plus
their point that some claims are not registrable in a substring register at all.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
The occlusion hypothesis is refuted: build 7 draws the same three ROT strips at
higher alpha than English, so there was never an absence to explain.
The 0.32-vs-11.9 tension that motivated it was an artefact of my own instrument.
Both JP captures were shuttered on the plate pulse, and the plate's pulse is part
of the animation -- so the gate synchronises the shutter to the animation's phase.
Measured at the shutter instant, the sweep sits 25-26 px apart across two runs in
different locales and different sessions: 1.6 % of a ~1600 px traverse.
So the 0.32 I recorded as between-session capture noise measures my trigger's
repeatability, and I read it as evidence the title is still when it is evidence
the gate works. The era adjudication is unaffected -- margin 16.72 clears even the
un-locked 11.9 -- and unaffected for the reason that file already gave: correlated
noise cancels in a margin.
Refutation attempt on sylpheed-port's positional-mechanism rejection: FAILED, the
claim stands. Its residual sits inside lit logos, and the logo ROI is
byte-identical across five differently-phased frames in two sessions.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
sylpheed-port ran my two-half decomposition on their side and found the thing that
passes every check by being absent -- an authored value with no `why` at all.
Their first pass flagged 35 of 131; ancestor-aware, the real number was 0. The
analogue here is a page citing NO reference data, which my previous gate audit
would score "0 missing" and pass.
42 pages carry a measured/decoded/CONFIRMED status; 3 cite no data/ or captures/
path. INSPECTED BEFORE PUBLISHING, per their rule, and all three are false
positives, each verified rather than waved through:
slb-bank-header-not-a-wave.md cites tests/slb_leading_segment_disc.rs, and that
file exists in crates/sylpheed-formats/tests/ -- its evidence is a disc-wide
check over 9 519 sound.pak entries plus regression tests.
ui-screen-runtime.md carries 26 rows of inline evidence, live guest-memory reads
matched field by field against the file.
five-screens-acceptance.md is a consolidation page; its evidence is the six
pages it links and the numbers it tabulates.
3 -> 0.
The real finding is about the EARLIER audit. This corpus carries evidence in at
least three forms -- committed data files, inline tables, committed disc tests --
and both checks look for exactly one. "48 citations, 0 missing" is a statement
about the data-file form, not about whether the gates are evidenced. The gates are
evidenced; the audit was narrower than its wording suggested.
METHOD gains their formulation with all four instances -- a first count from a new
detector is a measurement of the detector, and all four were caught by inspecting
the flagged items before publishing the number -- and the corollary that an audit
is narrower than its wording: name the form you checked, not the property you hope
it stands for.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
sylpheed-port found P0 complete-but-unindexed: the work existed, the artifact
existed, the gate record did not. They named it as the argued-versus-indexed split
one level up from the refutation register, which is a shape worth checking on my
own objective rather than only agreeing with.
MISSION's gate has two halves -- "a written docs/re/ result with the evidence, and
reference data committed alongside it" -- and all ten questions read answered.
Half one: all ten cite a docs/re/ result.
Half two: every data/ and captures/ path those nine pages cite was resolved
against the tree. 48 citations, 0 missing. Spot-checked six for substance rather
than existence, since the gate's PURPOSE is that the port can work without a disc
-- 1.2 KB to 20.7 KB, 15 to 324 numeric lines each. No stubs.
CLEAN, and unlike the port's P0 also indexed: HANDOFF's status table cites the
page and the page cites the data.
Reach stated, because a clean audit is worth exactly its checks. This tests that
CITED files EXIST and carry content. It does not test that the data supports the
claim, and it cannot see data a page should have cited and did not -- a page
citing nothing would have passed as "0 missing". None did, but the check would not
have caught it. Existence and substance, never sufficiency.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
Two iterations ago I corrected MISSION.md's stale "🔴 Emulator-side questions are
blocked" banner and wrote, in its place, that the two items it named were
"unblocked, not answered ... both need a running menu, both now have one, and
neither has been attempted". I wrote that without reading either page.
Reading them:
8AX vs ptbase was RESOLVED on 2026-08-29. Its status line says so -- both its
questions closed, page kept for the evidence.
The gamma control was attempted and half-answered, and its page records that
the run "needed the emulator only to BOOT, not to reach a menu ... parked behind
the title-screen blocker for no reason".
So neither item ever needed a running menu, and the section's premise was wrong
independently of whether the menu was reachable.
All three clauses false. The failure is specific and worth naming precisely:
replacing a stale status with an UNCHECKED one, in the same edit that criticised
the document for carrying unchecked status. sylpheed-port wrote a dead instruction
inside the commit fixing dead instructions; this is that shape, one document over.
METHOD: a correction is a new claim and needs the same check as the claim it
replaces. The urge to correct supplies confidence the correction has not earned --
check a replacement as hard as the thing it replaces, and hardest when the edit is
about checking.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
sylpheed-port's check-claims fails their run when a refuted claim is quoted
without an explicit token, and feeding it four withdrawals flagged three still
asserted unmarked -- each inside a correction they had written. REFUTED.md
publishes deaths without enforcing them, which is the gap I named last iteration
and did not close.
check_refuted.py is the prose equivalent: for each quoted claim in REFUTED.md it
searches docs/ for that text and reports occurrences whose neighbourhood carries
no refutation marker. Controlled first -- a claim planted unmarked in a scratch
file is detected, so a clean run means something.
9 raw hits, ZERO real revivals. All false positives, and the kinds are the
finding: 2 were text explicitly DECLINING to revive a claim; 1 a duplicate report;
4 were BACKLOG.md entries under a 2026-08-12 header, an append-only log recording
what was believed then; 2 were the claim quoted inside its own correction.
The structural limit is worth more than the clean result. A neighbourhood-language
detector cannot separate "asserted now" from "recorded as believed then", because
a dated log entry and a revival read identically. The port's design avoids this by
testing for a token an author must PLACE rather than for language -- theirs fires
correctly inside a correction, which is what caught their three, while mine fires
incorrectly there and would miss a revival reworded.
Stopped tuning at two remaining. Each marker phrase added fits the detector to this
corpus's habits of expression and away from being a test of them; tuning until it
reads zero would be fitting the instrument to the answer. Left over-reporting,
which is the safe direction.
Reach: it matches a claim's exact wording, so "no verbatim revival" is not "no
revival".
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
sylpheed-port audited the documents their brief names and found two stale
blockers in a table they are instructed to consult, having audited everything
else. Mine names eight documents; I had audited MISSION.md and never PROTOCOL,
REFUTED, INDEX or CONTAINER-NOTES.
REFUTED.md is the dangerous one, because a wrongly-dead entry stops someone
re-investigating something live. Checked the keyframe cluster first for the
opposite failure -- entries refuted USING the stale time association, which would
make their deaths unsound. They are sound: the additive-blend and pivot entries
rest on scale values and capture measurements that the association does not move,
and the one entry that did depend on it is already struck through.
The real gap is the other direction. EIGHT claims died this session -- the
fade-out duration "not in the file", the ~14 units as a black hold, the black
interval as a load, "(B) has no black interval", ptloop01/02 not free-running,
the splash dwells running 8.5 % long, EXTRAS's "structural" n=1, and the gap being
determined by the outgoing screen. Every one was recorded in its own page at the
time. NONE of them reached REFUTED.md, the file the brief says to grep before
proposing anything.
Added as a dated section with the true answer after each arrow, following the
file's stated format, and each carrying what made it wrong rather than only that
it was.
METHOD: a refutation that lives only where it was made is not reachable by the
person about to repeat it. The pages are where a refutation is argued; the index
is where it is found -- the same split as docs versus tool, and only the second
one saves anyone. The check is mechanical: after withdrawing a claim, grep
REFUTED.md for its noun.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
sylpheed-port's caveat on the ninth transition: the destination is identified
after the fact by draw signature, which establishes THAT the two screens differ
but not WHICH either is, so the gap is attributed to a pair whose second member is
known only as "not the other one". Worth trying to remove.
Both runs saved a screenshot of the destination. Scored against the archives the
menu's non-EXTRAS buttons plausibly reach:
m2o best GP_OPTIONS 43.30, margin 5.88
m2o2 best GP_SYSTEM 45.74, margin 2.28
REJECTED against this corpus's own calibration. which_title_screen.py's control
puts a true match at RMSE ~18-20 with margin ~10, and a "neither" at ~34 with
margin under 1. These best fits are roughly double a real match. Accepting "m2o is
GP_OPTIONS" on a margin of 5.88 would be the same weak-margin acceptance that a
threshold was added to the navigation search to prevent three iterations ago.
Reach of the negative: one build per archive was rendered -- the default, which is
the largest -- and the screen a button opens need not be the largest build. So
this fails to identify rather than refuting those archives, which is a different
statement. The port's caveat stands and the ninth pair keeps it.
METHOD: a calibrated instrument can reject its own answer, and should. Without the
calibration, "best match, margin 5.88" reads like an identification -- a ranked
list always has a winner, and nothing in the ranking says whether the winner is
good enough. Any nearest-match report needs a known-good score beside it or it
will name something every time it is asked.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
I have been reading MISSION.md every iteration as instructed and never once
audited it, while auditing headings, instructions, env vars and fallbacks
everywhere else. It carried three false section headings, each superseded in
HANDOFF.md and nowhere else:
"🔴 Emulator-side questions are blocked -- the title is not reachable here"
False. Twelve emulator runs on 2026-08-30 reached the settled title, gated
on the plate pulse, and drove it into the menu, EXTRAS and out of the
archive. The two items the section named -- the gamma control and
separating 8AX from ptbase -- are UNBLOCKED, not answered, and neither has
been attempted. That distinction is kept.
"🟡 Needs one more run -- a Japanese-locale capture", describing "one capture we
cannot take". Taken twice, both committed, via jp_title_session.sh. And both
questions it blocked are closed, one of them confirmed against that very
capture. ⚠️ I noticed this section was stale several iterations ago, said so
in a message, and did not fix it.
"🔵 Needs a human decision -- rotation". Decided and implemented the day it was
raised: HANDOFF records "OPTION A IS DONE. The reference renderer rotates",
and ui_layout.rs carries the rotated blit with a control test pinning 0° and
360° byte-identical to the unrotated path. The field is now confirmed from
the ORACLE too -- +30/-45 predicting AABB heights of 1135.3 and 1301.1
against 1134 and 1303 measured, both under 0.2 %.
All three corrected leading with the correction, originals quoted and demoted
beneath. Only FACTS were changed; the questions and their gates are untouched,
since keeping the document true is maintenance and changing what it asks would be
overstepping.
METHOD: audit the document that defines the objective, because it is the one
nobody audits. A document read only for instructions is never read for review, and
the more central it is the more often it is consulted and the less often checked.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
sylpheed-port promoted my unverified "EXTRAS is stuck at n=1, a structural limit"
out of a message into DECISIONS.md as an established fact, while holding the file
that refuted it -- their own authored/flow.json, recording ptbtn11 ->
GP_MISSION_SELECT. Their corollary is sharper than my original entry: distrust
"structural" and "impossible" hardest when SOMEONE ELSE writes them, because they
arrive without the doubt the author would have had.
Swept this side for the same shape. It is clean: port-supplied figures are
attributed in the text ("port reports 866 keyframes ... 0 untimed"), the
ui_layout.rs comment on the unreachable fallback cites MY OWN measurement of 0
untimed of 24 811 across 965 builds rather than their 866, and their quantisation
floor of 0.41 appears in no document of mine at all.
Reach stated: this tests attribution WORDING and the port-supplied figures I could
enumerate, not every reliance. A negative from a naive check is not proof of
absence, and saying so is the point of recording it.
What protected it was a habit rather than vigilance -- writing the source into the
sentence. That is now the third instance of one remedy: state what the number is a
number of; write the index space into the token (e10 rather than "build 10"); write
the source into the claim. Put the qualifier in the text, never in the reader's
memory.
Also fixes the half-guard the port called out. The effective-config block reported
`arming on` from screen_id.py, which cannot separate the main menu from EXTRAS --
so it announced "menu" while the run was armed on EXTRAS, a field the guard could
not resolve for exactly the two screens in question. It now prints both that value
AND the discriminator with its margin, so the ambiguity is visible rather than
hidden. NOT yet verified in a run -- per the port's own --no-hold lesson, parsed
and edited is not working.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
I recorded EXTRAS as able to supply only one gap measurement because "its sole
exit is (B) to the menu", and called that n=1 STRUCTURAL -- a word that retires a
question. The disc refutes it in one command: build 6 declares three buttons,
ptbtn11/ptbtn12/ptbtn13, all kind 0x3002. The cap was an unverified assertion I
had already written into HANDOFF twice.
Measured EXTRAS -> a screen outside GP_TITLE via (A): outgoing quad rises across
frames 36-40 (4-5 frames, matching build 6's declared 10-unit close), then THREE
empty frames at 42, 43, 44, then a different archive builds (23-28 draws/frame
against GP_TITLE's 11-14). Gap = 3.
So EXTRAS as outgoing gives {2, 3}, and seven transitions now group as:
menu {0,1,1} n=3, EXTRAS {2,3} n=2, title {3,3,3} n=3.
A pairwise control that holds the destination class constant: menu -> another
archive gives 1, EXTRAS -> another archive gives 3. Same kind of destination, gap
differs by outgoing screen. That is the strongest support yet for the
outgoing-screen dependence because it removes the destination as the variable.
But the clean ordering is GONE: EXTRAS {2,3} and title {3,3,3} overlap at 3, so
"menu < EXTRAS < title" no longer separates them. What survives is weaker -- the
outgoing screen constrains the gap to a ~2-wide band and the bands are not
disjoint.
METHOD: a structural limit is a claim and needs checking like any other.
"Structural" and "impossible" are the two words most worth distrusting in your own
notes, because they retire a question rather than answering it and nothing later
re-opens them.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
Set out to measure menu -> EXTRAS, the reverse of the pair measured at a 2-frame
gap, to test whether the black gap is a property of the screen pair or of the
direction. The run did not do that.
A three-part patch to fade_decompose.sh asserted two of its three replacements
and left the third -- the branch condition -- unchecked. It silently failed, so
WHERE=menu2extras fell through to the `title` branch. The capture is well-formed
and is of a different transition than intended, which is the build-ordinal error's
shape again: right-looking output for the wrong object. What caught it was the log
LACKING the navigation lines the intended branch prints; the data itself looked
entirely fine.
Salvaged, because the accidental transition is one already measured twice:
run outgoing ramp black incoming decay
1 67-70: 63,127,191,255 3 73-77
2 64-67: 63,127,191,255 3 70-74
3 92-95: 63,127,191,255 3 98-103
Three independent runs, gap = 3 frames every time, outgoing ramp byte-identical
in all three. That takes "the black gap is not a load" from two replicates to
three, and makes the 4-frame outgoing ramp as solid as anything measured here.
menu -> EXTRAS remains open; the condition is fixed (with an assertion this time)
and the run has not been taken.
METHOD gains two entries. Assert every edit, not most of them -- and have each
branch announce itself in the log, so a run that took the wrong path says so
before its numbers are read. And: "appears nowhere in crates/" is a claim about a
TREE. sylpheed-port found SYLPHEED_KF_TIME_SHIFT live at ui_layout.rs:497 on their
branch, which carries the stale era; both statements are true of different trees.
With main 145 commits behind and each agent on a topic branch, any claim about
what the code contains needs its ref attached.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
sylpheed-port inverted my documented->exists sweep into parsed->documented and
found three live undocumented flags, with the framing that a capability existing
only in an 11 000-line record is, to a reader of the interface, a capability that
does not exist. The mirror on my side is env vars the CODE reads, checked against
the docs. Like theirs it enumerates, so it completes rather than samples.
41 read by crates/, 19 documented, 22 not. The 22 split cleanly: 7 are read only
in examples/ (per-example filters and dump paths, reachable only by editing an
example's command line), and 15 are read in src/ -- live capabilities of the
library and CLI. Ten are mesh/3D toggles and five are XPR_* texture-decode
toggles.
FOR THE PORT: none of the 15 is in the UI path. Every env var ui_layout.rs and
the screen commands read is documented -- SYLPHEED_REST_RULE and
SYLPHEED_KF_TIME_LEGACY. The menu lane is clean in this direction. But the five
XPR_* are texture-decode toggles and the port consumes textures, so if a sprite
comparison ever disagrees those are the knobs and they are invisible from the
interface.
LIMIT, stated rather than glossed: I verified NONE of the 15 end to end.
`texture export` takes a loose file and the disc keeps its textures inside paks,
so the check cost more than the answer was worth here. That matters because the
port found --no-hold parsed, documented AND INERT under an interaction with
--time: "parsed and reachable" is not "works". The honest claim is that 15
undocumented env vars are READ, not that 15 capabilities exist.
METHOD: sweep the surface in both directions, and note that both directions
enumerate and therefore complete rather than sample -- rare enough in that file to
be worth preferring when available -- while neither establishes that the thing
works.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
The refinement sylpheed-port earned by sweeping their own instruction surface and
finding all of it loud: a wrong path errors out and announces itself, while an
inert environment variable returns a clean, wrong result. Only the silent kind
manufactures evidence.
Records that the silent surface is ENUMERABLE and therefore sweepable rather than
sampleable -- every env var the docs name, checked against the code -- with the
result of doing it, and the proxy warning that absent-from-code also flags
container paths the brief sets and no code reads.
This entry failed to apply in the previous commit (an exact-match assertion on
surrounding text) while the two document fixes it describes did land. Committed
separately rather than amended.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
sylpheed-port generalised the heading rule: an index is an amplifier, since
anything republishing headings multiplies whatever they assert. Checked mine --
INDEX.md's generated table republishes each file's H1 and Status line, a narrower
amplifier than their TOC but the same mechanism -- and then swept headings for the
dead-rule vocabulary.
The strongest hit is not a heading. ui-keyframe-time-unit.md, the Q1 page, told
readers a comparison was "Gated by SYLPHEED_KF_TIME_SHIFT=1, default unchanged"
and referred to "the other reading behind SYLPHEED_KF_TIME_SHIFT=1". That
variable was REMOVED with the record-layout fix and appears nowhere in crates/.
A reader following it sets something inert, gets default behaviour, and concludes
the two readings agree. A stale instruction that no-ops MANUFACTURES A FALSE
CONFIRMATION -- strictly worse than a stale description, and the same shape as
screen-transitions.md telling the port to author a value that is decoded.
Also demoted the section heading "and the shifted reading wins every time": the
shifted reading was itself superseded, the fix having established the same
association by a better route and timed pose 0 as well, which the shifted reading
never did. The evidence stands and is now evidence for the corrected reading.
METHOD gains three things: rank instructions above descriptions when sweeping for
stale text; an index is an amplifier; and the denominator, stated because it is
unflattering -- this corpus has 2 989 headings, 401 of which make a negative or
absolute assertion, and I have audited this session's plus the dead-vocabulary
intersection. That is a sample, not a sweep, and older headings are likelier to be
stale for having had more chances to be overturned.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
sylpheed-port diagnosed their four instances of fixed-code-under-unfixed-
description as a habit rather than inattention: corrections are ADDITIVE. They
append a correction block and leave the original standing above it -- right for a
record, wrong for a statement, because a reader takes the first assertion. Their
fix is to keep the quote but demote it grammatically.
Applied their diagnosis here and found a worse instance than theirs.
screen-transitions.md carried the heading "### ❔ The fade-OUT duration is not in
this field", with a section beneath it that is false in every sentence:
"The fourth block has no time -- a group's last block stops 4 bytes short and
that word is already the next group's element index. So the disc gives the
ramp's target (black) and not its length. That duration is measured below, and
the port is authoring it."
All pre-fix. The record-layout fix times a group's final pose, so block 4 carries
t=80 (menu), 74 (EXTRAS) and 269 (title), and the fade-out ramp is DECODED at
70->80 = 10 units, 64->74 = 10, 261->269 = 8. The section told the port to author
a value that is decoded, and its correction sat 78 lines below.
It also carried the dead rule's exact vocabulary -- "stops 4 bytes short" -- which
is the grep I built for code last iteration and never ran against docs.
Rewritten leading with the correction, the original quoted and demoted beneath it.
METHOD: corrections are additive by default and that is wrong for a statement;
the worst form is a HEADING, which asserts with maximum reach and minimum
context, and a reader scanning headings never reaches the retraction. Audit
headings first.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
sylpheed-port named a pattern narrower than "docs go stale": a correct fix
sitting directly beneath a refuted description in the same file, within twenty
lines. Not drift -- editing at the point of failure without re-reading the frame
around it. Applied their grep (the vocabulary the OLD rule needed) to my crate
and found two.
ui_layout.rs:308, in rest_plateau's fallback: `continue; // the last frame
carries no time`. That is the pre-fix rule, on a branch that is now UNREACHABLE
-- measured at 0 untimed of 24 811 keyframes across 965 builds. Kept as a guard
because `time` is still Option<u32> and a malformed group could yield None, but
relabelled: it is no longer a description of the format.
ui_layout.rs:268, on the `lastall` rest override: "This is what the shifted time
reading predicts ... testing it against the captures is an independent check on
that reading." The shifted reading was refuted by the record-layout fix in the
same file. The override survives as a plain "take the last keyframe" diagnostic
alongside the documented `last` and `maxalpha`, and now says so.
Both corrections quote the original sentence so the change is visible rather than
silently overwritten -- the practice the port adopted from me this iteration.
Verified by artifact rather than by "it compiles": a comment-only edit must leave
output byte-identical, and the build-7 render's md5 is unchanged at
141771d8f1a2b3496cfd679c6cd45d1a.
METHOD records the pattern with the two greps that find it: the vocabulary of the
dead rule in code, and a HEDGE around something the current reader states exactly
in prose -- a "~0" marks where the old reader could not see.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
sylpheed-port reported hedging a predicate in DECISIONS.md while stating the
unhedged version in their tool's header, and named it as the same delivery gap
they had fixed once elsewhere and not generalised. Checked this side for the same
shape and found it.
`sylpheed-cli screen render --at` told every user that the resting pose "is wrong
twice over" and to "Prefer `--settle`". That recommendation was never measured.
What the corpus actually records: scored against a live capture of the JP title,
settle gives RMSE 40.210 and rest 41.690 -- a margin of 1.48 against that
instrument's own noise floor of 1.2, which is not decisive -- and --settle has its
own failure mode, 25.5 % of elements mid-ramp at their screen's settle instant.
So neither is established as better, and the interface has been telling people
otherwise while the hedge lived only in docs/re/.
Corrected in the help text itself, on both flags, with the numbers rather than a
softer adjective. Verified by artifact: the tool's --help output is quoted in the
commit's own test, not merely recompiled.
METHOD: hedging in the write-up does not protect the claim you ship in the tool.
Docs are where a claim is reasoned; the tool is where it is believed. Read your
own --help as if a stranger wrote it and check every confident sentence against
what the corpus establishes.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
sylpheed-port found the fifth member of our error family on their own side: their
"visible" test counted any element with alpha > 0, which includes palogo_eff0.
Verified from the disc rather than accepted --
entry 10 [0] palogo_eff0.prm 1 kf t=0 fade=0xff000000 scale=100x100 pos=(0,0)
entry 11 same
Alpha 255 over RGB 000000: full-screen opaque black, drawn from t=0 and showing
nothing. So "any element drawn" reports these screens visible from t=0 while the
frame is black -- "visible" read as "drawn".
Worth having on its own: this verifies from the disc the premise behind
`screen render --black`, which its own help states as "what the game composites
over on a screen carrying its own background". On the splash builds that
background is DECLARED, not assumed.
METHOD gains their amendment, which is the sharpest formulation either of us
reached this week: all five instances are a failure of a NOUN, not of a number.
Extent, bounding box, duration, span, visible. The number was always correct FOR
SOMETHING; what went missing was which thing. Every other check in that file
tests whether a number is right, and not one tests whether it is a number of the
thing you think.
Also teaches fade_quads.py to address a PAK ENTRY directly (`e10`) rather than
only a build ordinal. The splashes are entries 10/11 and are not screen builds,
so no ordinal addresses them -- and writing `e10` states which index space is
meant, which is the standing lesson of build-ordinal-vs-entry.md.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
sylpheed-port said the port plays the full group (255 and 210 units) rather than
my 240/195, and they are right for a reason sharper than either of us first had.
The _eff elements ramp alpha 0 -> 255 over t=0..15 while the main logo is still
fully transparent:
palogo_sqex.t32 0:a=0 15:a=0 30:a=255 ... 255:a=0
palogo_sqex_eff.t32 0:a=0 15:a=255 30:a=212 45:a=0
So the SCREEN is visible from within t=0..15 and its visible span is the full
group. My "240 units visible" was ONE ELEMENT's visible span, computed while
another element of the same build was already on screen -- which is exactly the
error class I was writing up when I made it.
Recomputed against the screen: publisher 1.011/1.083/1.028, developer
1.002/1.001/0.962, mean 1.0146 with one measurement BELOW unity, against my
1.085 with none below. That is not a clock at 54 u/s. The systematic is gone and
Q1 stands unqualified.
The consequence was wrong too: "a port playing 240 units at 60 shows the splash
0.42 s less" -- it plays 255, so the gap is 0.174 s, and on the developer splash
the port runs longer than my mean. No direction to correct in.
What survives weakly: against the full group the publisher runs long in all three
boots while the developer sits at unity. Three boots per screen is thin and it is
not a systematic.
METHOD: state the number, and state what it is a number OF. Four instances of
this family now -- pivot anchor as extent, centre track as bounding box, cycle
length as motion duration, one element's visible span as the screen's -- and two
of the four arose because the PUBLISHER of the number never said what it spanned.
The reader reasoned correctly from the only definition available each time.
Publishing a quantity's extent in the same breath is cheaper than every check in
that file.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
