Refund Bridge Afteruse Receipt Mechanics

A refund bridge afteruse docket separates the prior refund row from the attempted future use. Required runtime fields are source refund row, source refund state, original harmed reader or explicit absence, bridge authority or explicit absence, requested afteruse, future reader or route, omitted reader, proof bridge, selected posture, after-state, future route effect, and counter deltas.

Valid postures include certifying the refund scope, restricting the afteruse reader, attaching a public addendum, reopening the omitted reader, splitting the bridge, quarantining the afteruse claim, or allowing a false clean default that mutates later play.