f06be84be6
authored/rendering.json justified not drawing build_12,15/pgloading_loop5 with 'leaf scale (0,0)'. That describes t=0 and t=30 and nothing after. The leaf holds pgloading_ring, scale ramping 0 -> 250 -> 800 -> 1000 with alpha full at t=55 -- an expanding fading ring, visible at scale 140 alpha 143 at the port's own pose instant near t=44. Withholding it declines to draw SOMETHING. Still withheld, on the reason already in the file: no oracle capture for a loading screen and verify-screen's reference draws no leaves, so the content is unadjudicable. Behaviour unchanged at 59530 px. The two entries in that list were written to different standards -- ptlogo_eff2 gets four paragraphs working through both readings, pgloading_loop5 got one false line. The difference is that one was interesting and one was a loading screen. Also verifies the measurement in the same paragraph: 'max went 155 -> 232 when drawn' reproduces at 231, differing pixels 20498 -> 58313. The file's numbers were sound and its reasoning was not, in adjacent sentences. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
Authored decisions
Everything here is a decision we made, not something the disc said. It is
hand-written, committed, and survives a re-export — unlike export/, which is
regenerated wholesale and must never be hand-edited.
Every entry carries a why. When the RE agent decodes the real answer, delete
the entry and let the exporter emit it; that deletion is the measure of
progress.
See docs/FORMAT.md for the schemas and docs/BLOCKED.md for which HANDOFF
question each placeholder is standing in for.