Proof Wall Rotation Receipt
Proof Wall Rotation Receipt opens after a proof wall pin has been moved, replaced, unpinned, retired, or marked stale, and a later reader tries to cite the old pin as if it still proves the current wall.
Proof Wall Pinning Custody already decides which proof becomes visible and which proof is occluded for a named reader. Its state machine includes rotated: an older proof can move behind a newer pin while remaining recallable and scarred. The remaining gap is the receipt for that rotation. Without it, a sponsor, public recap, lawful annex, archive row, route asset, or management report can cite the old visible pin and erase the fact that the wall changed.
This storyline makes rotation itself a proof object. The old pin stays true as history, but future play must prove why it was rotated, who authorized the current pin, who is harmed by the change, and which reader may still consume the old pin.
Playable Question
When a prior proof-wall pin is rotated or unpinned, does production certify the current pin, attach a rotation receipt to the old pin, split old and new readers, rebuild the wall, publish an omitted-proof notice, quarantine the rotation, or let a false rotation default harden?
Every answer must name source wall row, prior pin, current pin or explicit absence, rotation reason, rotation authority, future reader, harmed or excluded reader, proof bridge, selected posture, wall state after, prior pin state after, and future route effect.
State-Triggered Entry
Open this storyline only from live state pressure:
entry_state:
trigger_kind: state_pressure
source_proof_wall_row_visible: true
prior_visible_pin_visible: true
current_pin_or_explicit_absence_visible: true
rotation_reason_visible: true
rotation_authority_or_explicit_absence_visible: true
future_reader_consumes_rotation_state: true
harmed_or_excluded_reader_visible_or_explicit_absence: true
player_can_certify_attach_split_rebuild_notice_quarantine_or_default: true
no_fixed_turn_trigger: true
no_fixed_day_or_week_trigger: true
no_raw_pin_count_trigger: true
no_dashboard_or_lens_health_trigger: trueInvalid entry includes a raw number of pinned proofs, a dashboard warning, a proof-wall cleanup phase, or a stale pin with no future reader trying to consume it.
Bound Content Pack
- Proof Wall Rotation Receipt defines rotation states, branch families, and false-rotation defaults.
- Proof Wall Rotation Docket records the source wall, prior pin, current pin, rotation reason, authority, proof bridge, readers, posture, after-state, and future effect.
- Proof Wall Rotation Review resolves certification, receipt attachment, reader split, rebuild, notice, quarantine, or default.
- False Proof Wall Rotation Default records when a rotated pin is consumed as current clean proof.
- Proof Wall Rotation Receipt Lens observes this packet.
Storyline Spine
Beat 1 - A wall pin changes
A public receipt may be replaced by lawful proof, a sponsor-safe proof may move in front of an artist-boundary proof, a proof-wall pin may be retired into archive, or an old recovery-only proof may be unpinned after a new bridge appears. The old pin is not deleted; it becomes historical and scoped.
Beat 2 - A later reader cites the old visibility
A later route, recap, archive release, sponsor package, management closure, lawful annex, route asset, or broadcast-reality check says the old visible pin proves the current wall. This is where the rotation docket opens.
Beat 3 - The docket separates old pin from current wall
Create Proof Wall Rotation Docket. It must preserve source proof-wall row, prior visible pin, current pin or explicit absence, rotation reason, rotation authority, proof bridge, future reader, harmed reader, selected posture, wall state after, prior pin state after, and future effect.
Beat 4 - Review prices the change
Run Proof Wall Rotation Review. A rotated pin can remain citeable, but only through a named receipt and reader scope. A lawful replacement cannot become public truth for free; a sponsor replacement cannot erase public counterproof; an archive unpin cannot make the old wall current.
Beat 5 - Future play reads rotation state
Future content consumes rotation_state_after, not old_pin_was_visible. A prior pin can become history-only, receipt-bound, split, rebuilt, notice-required, quarantined, or false-clean. That after-state must change reader acceptance, route cost, custody, or recovery play.
Branch Map
| Branch | Relief | Cost or scar | Future state |
|---|---|---|---|
certify_current_pin | named reader can accept the current wall | prior pin remains history-only with scope | accepted-with-current-pin |
attach_rotation_receipt | old pin remains citeable inside a receipt | proof bridge, addendum, or carrier burden remains | receipt-bound or bridge-required |
split_old_and_new_readers | incompatible readers stop overwriting each other | split upkeep and source ambiguity rise | public-only, lawful-only, sponsor-only, or split |
rebuild_wall_from_sources | stale rotation cannot file first | delay, archive debt, or proof burden rises | wall-rebuild-required |
publish_omitted_pin_notice | harmed reader sees what changed | public distrust, inspection heat, or sponsor pressure rises | notice-required or contradiction-pending |
quarantine_rotation_claim | false current-wall use is blocked | current route loses shortcut | quarantined, blocked, or recovery-only |
false_proof_wall_rotation_default | fastest desk cites old pin as current | hidden harmed-reader or authority scar hardens | false-current, hostile, costlier, or recovery-only |
Every non-default branch must mutate one relief surface, one cost surface, and one future reader or route effect.
Default
If later play consumes an old pin as current wall proof without source wall row, prior pin, current pin or absence, rotation reason, authority, proof bridge, harmed reader, or future effect, False Proof Wall Rotation Default fires or arms.
false_proof_wall_rotation_default:
false_clean_rotation_claim: true
source_wall_row_or_absence: <wall row id or explicit_absence>
prior_pin_hidden_or_overread: prior_pin_hidden | current_pin_hidden | rotation_reason_hidden | authority_absent | proof_bridge_absent | harmed_reader_hidden | old_pin_claimed_current | equivalent
capturing_reader: sponsor | public | lawful_reader | archive | route_asset | management | broadcast_reality | equivalent
harmed_or_excluded_reader: <reader route claimant or explicit_absence>
rotation_state_after: false_current_wall | stale_pin_reused | sponsor_only | public_only | lawful_only | split_required | quarantined | blocked | recovery_only
future_reader_effect: wall_rebuild_required | public_notice_due | lawful_annex_due | sponsor_unwind_due | route_costlier | blocked | hostile | recovery_only
counter_deltas_min: 3
durable_mutation: trueNon-Goals
- Not another initial pinning review.
- Not another proof-board snapshot page.
- Not an archive-index afteruse receipt.
- Not valid when rotation is only a UI reorder, dashboard state, raw pin count, or fixed cleanup phase.
- Not valid if an old wall pin can become current universal proof without a rotation receipt.