Three-Key Custody Docket / 三钥羁押案卷
Three-Key Custody Docket is the card for a route asset, proof object, edit copy, voice object, memorial package, or correction version that cannot safely move until sponsor, inspection, and cutroom custody are all visible.
It exists for the late management-RPG state where individual pressure systems are already armed: Orion Breath can fund or freeze the public version, Inspector Rhee Archive can admit, quarantine, or seize it, and Han Cutroom can produce, withhold, checksum, or split the source. The docket makes those keys collide on the same asset instead of letting one system silently settle custody.
Entry state
Create or update this card from state, not from a fixed turn number, when all are true:
- one named asset or target version is needed by at least two live systems;
- sponsor, inspection, and cutroom authority can each affect the asset, or one authority is explicitly absent/refused;
- releasing the asset with only one authority would create fraud, capture, public distrust, seizure, edit debt, or recovery-only route state;
- at least one player choice can seat, split, escrow, counter, quarantine, or refuse a key;
- the result can change future route access or route cost.
Required row shape
Each docket row must name the asset, the three keys, and the consequence of releasing without all of them.
three_key_custody_row:
row_id: <stable id>
asset_id: <route asset, proof object, edit copy, voice object, memorial package, correction row, or lawful/public record>
asset_kind: route_asset | proof_object | source_copy | voice_object | memorial_package | correction_version | public_record | lawful_record
shared_target_version: <version id>
sponsor_key_holder: sponsor | manager | funder | naming_rights_desk | explicit_absence
sponsor_key_state: key_unasked | key_offered | key_refused | key_seated | key_split | key_escrowed | key_counterfeit | key_hostile | key_missing
inspection_key_holder: inspector | archive | white_glove | legal_seal | explicit_absence
inspection_key_state: key_unasked | key_offered | key_refused | key_seated | key_split | key_escrowed | key_counterfeit | key_hostile | key_seized | key_missing
cutroom_key_holder: editor | source_custodian | black_box | checksum_holder | explicit_absence
cutroom_key_state: key_unasked | key_offered | key_refused | key_seated | key_split | key_escrowed | key_counterfeit | key_hostile | key_missing
missing_or_refused_key: sponsor | inspection | cutroom | none
proposed_release_pattern: sponsor_inspection | sponsor_cutroom | inspection_cutroom | split_three_key | escrow_and_delay | quarantine | blackout_fold | default_lockout
excluded_holder: <holder harmed by the proposed pattern>
collateral_at_risk: schedule_slot | route_asset | public_receipt | legal_seal | edit_checksum | source_tape | oxygen_credit | memorial_license | artist_consent | fan_refund_queue | explicit_absence
default_if_ignored: sponsor_capture | inspection_seizure | editor_withhold | counterfeit_key | route_asset_lockout | blackout_fold | recovery_only
future_route_effect: protected | costlier | captured | lawful_only | public_only | split_canon | contradiction_pending | recovery_only | hostile | blockedThe card fails its purpose if it stores only approved, blocked, or custody=true without naming all three keys, the missing/refused key, the excluded holder, and the future route effect.
Key meanings
Sponsor key
The sponsor key is not merely money. It is the power to fund, freeze, brand, insure, cancel, or default the public version. It can come from 播出破产账本线, Orion Breath Storyline, stop-loss pressure, oxygen relief, naming rights, or route-asset collateral.
Inspection key
The inspection key is admissibility and seizure pressure. It can admit the copy, demand token proof, quarantine the asset, seize a false owner, or convert the asset into lawful-only state.
Cutroom key
The cutroom key is source control. It can make a checksum copy, withhold the only edit, split public/formal copies, preserve a contradiction, or reveal that a clean release is counterfeit.
Observable use
The player must be able to inspect the row before a release happens. A valid surface shows:
- which asset is at stake;
- which three holders have keys or explicit absence;
- what release pattern is proposed;
- who is excluded;
- which proof or collateral is being risked;
- what default will occur if ignored;
- how future route access changes.