Left over from the rename: the handoff still described opponent 2 as "rung N"
and pointed at matchRung, and three comments in gameplay.js still called the
opponent curve a ladder. One word per thing, everywhere now — OPPONENTS, WOUND
STAGES, a sprite FAMILY — with a note in the handoff saying which word replaced
what, so the next reader is not left translating.
(The barrel weapons keep their own "rungs of the same ladder" line: that one is
about the WEAPON payout order and was never part of the confusion.)
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A day went into sprite consistency and most of it was spent solving the problem
in the wrong place. Written down so the next session starts from the answer
instead of rediscovering it.
The boundary everything else follows:
the generator, GIVEN REFERENCE IMAGES -> identity, pose, composition
the pipeline, DETERMINISTICALLY -> exact colour
the gates -> layout accidents only
With the proof, because it is the part that is hard to believe until measured:
the brute's serve sheet came back with his build, his garments and his DARK
TONES pixel-identical to the reference and his big pale shirt two shades
brighter. The model was looking straight at the character. Every call
re-renders and re-rendering re-lights. No prompt fixes that.
And the rule underneath all of it — A REFERENCE BEATS A DESCRIPTION, at every
level. The racket zombie's sheet was made from the character as an IMAGE plus
the poses as IMAGES and landed first time; the brute's three sheets each
re-derived the character from the same paragraph and produced three different
brutes. Corollary worth having: every corrective sentence in a prompt is
compensating for a reference you did not supply. When a prompt grows a third
"do NOT" clause, add an image instead.
Also written down: correct-then-check, calibrate-before-you-gate (with the
numbers every threshold was calibrated on), the five gates and what each one
actually measures, six traps that each shipped something silently before they
were caught, and three things still open — including that `changed` passed a
headless brute that still had its head, because it knows something moved and
not what.
The brute is PARKED: out of ZFAMS, 31 frames on disk, nine batches in the JSON,
one line away from live. Its healthy eleven are good; its wound stages are not.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Slices 1, 2 and 5 struck through with what they actually became; 3, 4, 6 and 7
left standing, with a note on 3 that the wound-stage art now exists for it and
on 4 that the racket_* batches are its template. The parts of slice 2 that are
still open (shots[] and the PARRY — the cheapest depth in the mode) are called
out rather than buried under a DONE.
Added: the record shape table (which of g/s/dead each mode uses and why), the
classic-tennis mode, the second ending, and four new traps — the stats banked
flag that no-kill modes never clear, the magenta key that ate racket strings,
the read-only PIL image that made the fix look like a no-op, and the detail
bar that ratchets against what it is replacing.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Temporary file, written because a session ran out of context mid-slice — fold
into PROJECT.md and delete when the work lands. Not in the Dockerfile COPY;
docs are not served.
Records the decision (A: blood-only, measure becomes opponents felled) and
the finding behind it: Oliver believed losing a match killed him, when he was
bleeding out during deuce wars. That misreading is itself the bug — model A
only works if the player can see they are bleeding, not losing.
Also carries the build order (summary+measure, named ladder with
personalities, wound-driven play, the fall animation, menu, flick teaching,
opponent serve games), the flight-recorder recipe that ended four rounds of
guesswork, the traps this mode already sprung, and the do-nots.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
wuwiandClaude Opus 5