Fu Han Safe-Version Hash Attestation / 傅寒安全版本哈希公证线

Rite 22 offers three mutually incompatible safe stories, but its old runtime exposed only the selected generic 安全连续性版本. This storyline preserves the missing provenance question:

Before audience signatures start citing a safe archive, can a named person prove that all three source files existed, which hashes were observed, and how one posture was selected—without turning that proof into truth or authority?

Ordered chain

1. storyteller-rite-22-three-safe-versions remains the sole producer and now requires an explicit option. Choice 0 records a company-selected version; choice 1 preserves parallel versions. Both gain actual Fu Han and the same five-card packet.
2. storyteller.rite.fu_han_safe_version_hash_attestation_review.v1 requires eight exact cards in hand and one explicit source-choice history.
3. Review choices 0–3 are terminal: bounded recruit, independent public deposit, company capture, or hostile suppression.
4. If storyteller-rite-23-fan-signature-accession completes while the window remains open, storyteller.event.fu_han_unattested_version_set_default.v1 creates a recovery-only miss.

Eight exact review slots

Slot	Exact card
fu_han	card-storyteller-fu-han
continuity_docket	card-storyteller-continuity-docket
safe_archive_version	card-storyteller-safe-archive-version
version_manifest	storyteller.card.fu_han_three_version_manifest.v1
hash_register	storyteller.card.fu_han_observed_hash_register.v1
source_choice_receipt	storyteller.card.fu_han_safe_version_selection_receipt.v1
future_reader	storyteller.card.fu_han_named_version_set_reader.v1
authority_boundary	storyteller.card.fu_han_attestation_only_authority_boundary.v1

A generic notary, a single safe-version card, mutable flags without ordered Rite 22 history, off-hand cards, or mixed source history must fail before state mutation.

The future_reader row is explicitly storyteller.reader.seventh_dome_fan_signature_accession_desk.v1 — the Seventh Dome Fan-Signature Accession Desk, or a recorded successor. Its scope is limited to three-version existence, observed hashes, and generation/selection order.

Four dispositions

Choice	Required Rite 22 history	Result	Recruitment
0	parallel versions preserved	protected bounded version-set notary	sole recruit + route asset
1	parallel versions preserved	public hash deposit; Fu Han independent	no
2	company safe version selected	white-glove capture of selected hash	no
3	either real source choice	suppressed rows and hostile countertestimony	no

All branches preserve a named future effect and visible counter cost. Only choice 0 sets fu_han.recruited and route_asset.fu_han_safe_version_hash_notary.

Natural miss

The Rite 23 deadline requires the still-open window, actual Fu Han, the named reader, the armed default, and absent disposition/recruitment. Its sole event option removes Fu Han, blocks the route, preserves the named reader, gains storyteller.card.fu_han_late_hash_mismatch_counterclaim.v1, and records unattested_version_set_recovery_only.

The counterclaim proves only that the version set or hash chain is disputed. It cannot reconstruct a missing file or select an official history.

Adjacent-lane boundary

• Safe Continuity Version Fork observes whether a safe version can stabilize breach at visible cost. Fu Han does not decide stabilization.
• continuity-version-dispute governs later legal identity of competing versions. Fu Han does not confer legal identity.
• Ming Ke proves pre-Rite-22 docket dispatch/arrival order. Fu Han proves the version files and hashes created inside Rite 22.
• Baiya can preserve or edit a later cut. Fu Han cannot edit, authenticate, or own it.

Replay contracts

• lens/replays/fu-han-safe-version-hash-attestation.recruit.replay.json: real Rite 22 choice 1, exact eight-slot review choice 0, actual Fu Han retained, sole route asset present.
• lens/replays/fu-han-safe-version-hash-attestation.default.replay.json: real Rite 22, real Rite 23, default option 0, actual Fu Han removed, late counterclaim present, route asset absent.

Both must come from integrity-backed CLI sessions with source: storyteller; neither may seed source, window, recruitment, route, deadline, miss, or terminal flags.