Audience member describes a JRuby workflow where a background thread computes (e.g. a Mandelbrot fractal) while the GUI thread displays progress, and reports the Ractor equivalent blocks and cannot be fire-and-forget. Asks whether any form of fire-and-forget Ractor exists. Louis admits he doesn't know — also notes this is a danger of vibe-coding through an unfamiliar domain — but shares the pattern he used: Ractors send progress messages to a main coordinating Ractor that tracks the highest current decryption percentage and shuts the others down when one wins.