max / quasi

Mark what a request decides, so a residual is read rather than recovered The derivation used to find a guard's branch by rendering the screen twice with that guard changed and measuring the difference, and a loop body by rendering it with one row and then two. Everything that went wrong in the staged path went wrong there: the window a repeat converts through, spans placed against each other, a prefix scan running past its own body, arms that had to stay flat because the arm not taken was never drawn. None of that information was ever missing. The macro parsed the guard, so it knows exactly which members it controls. It now says so. A staged twin marks the run of members each guard, loop and dispatch covers (quasi_router::stage::Mark). The renderer records where it wrote them (Cover). The derivation reads the record. One render answers every guard and every loop; a dispatch renders once per arm, because an arm nobody drew has nothing to compile, and each arm is read off its own cover -- so an arm may now hold loops and guards of its own. Gone with the comparisons: grown, shrunk, between, swapped, dispatched, placeable, placed, straddled, balanced, cuts, and the twelve tests that existed to argue about which placement a deletion should take. IN FLIGHT. The twin marks every container; four do not yet carry marks, and rustc names each one at the shape that tried: Table's rows, Field's options, the Node variants that hold members, and a bare Vec (which is what stage::Staged is for). A guarded setting is still refused unless it is in symbolic's PLACED list; the answer there is two arms over the member it settles, which also dissolves the Select and latched blockers.