A prompt rock for an Aesthetic Code session now draws the address of the piece that session is writing, instead of its tumbling sigil. The terminal was the wrong home for that QR: seventeen rows of half-blocks is the finest raster Terminal.app can make — it has no sixel, no inline images, no Kitty protocol — and it ate a third of the window. The menu bar has real pixels and no rows to spend. `PromptScanCode` renders with CoreImage at EC level M, a whole number of pixels per module with interpolation off, and a four-module quiet zone baked into the bitmap rather than left to whatever composites it. It refuses rather than guesses: an empty URL, a payload past capacity, or a module that would land under three device pixels all return nil, and nil means the ordinary stone. The status channel moved AROUND the code — the colour is a square offset behind the white card — because a QR lit by the scene's sun, tumbled, or tinted by status is a QR that does not scan. Nothing touches the modules. Playback returns early on these surfaces; only the pet name still blinks on a poke. The payload gains an `https://` prefix it does not carry in the marker: a phone camera reads a schemeless payload as text rather than an offer to open something. Verified by decoding the screen rather than trusting the drawing — `zbarimg` over a full 2816x1762 `screencapture` reads `https://aesthetic.computer/prompt~channel%20...~!autorun` back off the rock. Fallback exercised all four ways: with the URL, without it, on a `claude` rock that has one, and back again. Claude-Session: https://claude.ai/code/session_01AMHaRzWgfXei4MDV79zePz