Technical Custody Afteruse Review

Assignment slots: technical custody docket, source patch cable, operator/absence note, console proof bridge, harmed claimant, requested afteruse, and future reader.

Branch families:

• certify_patch_scope — certify only the named cable/timecode scope; relief: narrow technical proof; cost: future reader must cite the scope; future_effect_any: scoped cable proof required.
• restrict_to_console_corroboration — use the cable only with console log corroboration; relief: false authority is blocked; cost: second proof required; future_effect_any: corroboration gate.
• split_cable_from_operator_consent — split physical cable custody from operator permission; relief: custody remains usable; cost: consent claim reopens; future_effect_any: operator consent unresolved.
• attach_battery_ledger_bridge — attach battery and replacement ledger bridge; relief: version drift falls; cost: maintenance liability rises; future_effect_any: ledger bridge required.
• reopen_harmed_technician_claim — reopen the technician or audience claimant; relief: blame cannot be dumped silently; cost: sponsor heat rises; future_effect_any: claimant hearing required.
• quarantine_uncited_patch_copy — quarantine a copied, uncited, or version-drifted cable claim; relief: false chronology blocked; cost: route delay; future_effect_any: quarantine required.
• false_clean_technical_default — spend the cable as universal safety, consent, and settled chronology; relief: route moves immediately; cost: false-clean technical scar; future_effect_any: recovery-only future reader.