Callboard Photo Waiver Afteruse Receipt Mechanic

The mechanic treats photo consent as scoped custody, not as a universal clean waiver. Entry is state_pressure: a future route must attempt to consume an existing callboard photo waiver state, and the source row, photographer or explicit absence, depicted performer/asset, likeness scope, harmed claimant, requested afteruse, and proof bridge must be visible.

Counters and state are intentionally named so replay can show pressure rather than prose claims:

• callboardPhotoProgress measures review movement.
• photoWaiverHeat measures public/sponsor dispute risk.
• likenessArchiveDriftRisk rises when scope is hidden or overbroad.
• photographerBridgeTrust rises when the proof bridge is attached.
• performerClaimPressure rises when the depicted performer claim is reopened.
• futureRouteCost rises when later routes need scoped proof.
• falseCleanPhotoWaiver marks the durable default.

A valid branch must mutate future_reader_effect. The default records false_clean_photo_waiver: true, hidden_or_overbroad_likeness_scope, capturing_reader_or_route, harmed_claimant_or_absence, photo_waiver_afteruse_state_after, counter_deltas_min: 3, and durable_mutation: true.