Why this is a backend
The input is the evaluated drawing: move, line, cubic, transformed subpaths, paint opacity and clip stacks. No screenshot, edge detector or GPU readback supplies the beam. Muting a draw call changes this renderer while the official drawing remains intact.
The small piece of mathematics
A moving Gaussian spot integrates along each segment. An error-function difference gives its axial intensity; a Gaussian gives its width. History decays as exp(−Δt / τ). The Rive reticle uses the same arc-length scan position.
The exact boundary
This is a focused browser counterpart of RIVX’s native vector-beam pipeline. It implements path drawing semantics, not the complete native renderer or every .rivx document type. Raster images remain visible in the reference but have no vector contours. Clip centerlines use sampled geometric tests; narrow features can be missed, and glow may cross their boundary. Hidden paths can remain: this is a drawing-command view, not a visible-silhouette solver.