Residue Clinic Custody / 余物诊所羁押机制

Residue Clinic Custody keeps treatment, evidence, sponsor claims, character testimony, and later reuse on separate rows. It prevents a clinic result from collapsing into either “the company fixed it” or “the public saw it, therefore everyone may use it.”

Core non-equivalence

pain enters a clinic
  != a diagnosis is proven
  != treatment consent authorizes merchandising
  != thermal residue identifies a person
  != a public record grants ownership
  != discharge grants future-use permission

Entry and progress state

residue_clinic_state:
  trigger_kind: state_pressure
  entry_pressure_flag: storyteller_residue_clinic_intake_pressure
  entry_pressure_producers:
    - rite.unauthorized_memorial_drop
    - storyteller-event-25-unauthorized-memorial
  progress: 0..8
  clinic_open: boolean
  queue_pressure: integer
  four_rows:
    fever_ticket_roll: present
    residue_thermograph: present
    ash_consent_tape: present
    clean_bandage_contract: present
  care_disclosure_postures_for_rites_01_to_06_and_08: {}
  rite_07_custody_disposition: return_to_named_patient | quarantine_disputed_residue | unresolved
  pressure_events: {}
  xi_sheng_state: state | explicit_absence
  luo_ji_state: state | explicit_absence
  custody_state_after: state
  discharge_state_after: state
  reader_family_selection_available_after_resolution: true

Progress may advance only through the exact source chain:

01 open clinic
 -> 02 thermal triage
 -> 03 consent recording
 -> 04 bandage bargain
 -> 05 night queue
 -> 06 burn testimony
 -> 07 return or quarantine
 -> 08 discharge signoff

Completion flags are evidence of prior resolution, not authority to recreate cards or skip assignments.

Evidence-row rules

Fever-ticket roll

Records that people are queued and that a pain-ordering rule exists. It cannot diagnose, identify, consent, prescribe, or allocate oxygen universally.

Residue thermograph

Records a temperature chain among the observed body, bed, object, or residue. It cannot establish bodily identity, personhood, death, medical necessity, ownership, or intent.

Records scoped treatment consent or refusal in one encounter. The row retains treatment scope, reader scope, and any refusal, but does not independently prove subject identity. It never grants merchandising, reenactment, likeness, voice, archive, memorial, or blanket future-use permission.

Clean-bandage contract

Records the sponsor’s repair offer and ownership language. It is a claim against the clinic state, not proof that the patient accepted the claim or that the sponsor owns the wound, treatment, image, residue, or recovery story.

Rite transition contract

ProgressRiteRequired output
1storyteller-rite-residue-01-open-clinicclinic open, fever-ticket roll, queue pressure, selected posture
2storyteller-rite-residue-02-thermal-triagethermograph, thermal chain, fever-line event reachable
3storyteller-rite-residue-03-consent-recordingash consent tape, consent integrity, consent/refusal scope
4storyteller-rite-residue-04-bandage-bargainsponsor contract and wound claim visible
5storyteller-rite-residue-05-night-queueXi source encounter and sponsor-audit event reachable
6storyteller-rite-residue-06-burn-clinic-testimonyLuo source encounter and attribution row opened
7storyteller-rite-residue-07-return-or-quarantinereturn_to_fan_medical_custody or quarantine_under_named_audit selected; normalized custody disposition and queue event reachable
8storyteller-rite-residue-08-discharge-signoffdischarge state, queue/archive deltas, discharge review reachable

Rites 01–06 and 08 must each retain the selected public_record or protected_patient posture. A mixed run is valid only when all seven care/disclosure selections remain readable and rite 07 separately retains the exact option ID return_to_fan_medical_custody or quarantine_under_named_audit plus its normalized return_to_named_patient or quarantine_disputed_residue disposition.

Branch families

The public/protected family applies only to rites 01–06 and 08. Rite 07 uses the separate custody-disposition family below.

Public record

Public record makes the clinic row answerable to the selected reader family. It may raise influence, public legitimacy, witness exposure, audit heat, sponsor pressure, or archive contamination. It cannot broaden the row’s authority.

Protected patient

Protected patient narrows disclosure and prioritizes continued care. It may raise favor, protection cost, schedule delay, queue pressure, or future citation burden. It cannot make absence clean or convert privacy into sponsor/archive control.

Return or quarantine

return_to_fan_medical_custody records the normalized return_to_named_patient disposition without widening treatment or reuse consent. quarantine_under_named_audit records quarantine_disputed_residue without converting quarantine into company, sponsor, archive, or memorial ownership.

Fan-medical event response

The four pressure events may bind a named fan/medical signature to the row. This preserves accountability with exposure and debt; it does not grant collective consent or ownership.

Contained event response

White-glove or sponsor containment may reduce immediate public exposure while raising audit, capture, distrust, queue, or recovery pressure. Containment cannot overwrite the ash consent tape.

Character-state separation

xi_sheng:
  owns: queue_numbering_and_pain_priority
  route_asset: route_asset.xi_sheng_residue_queue_registrar
  independent_outcomes: [recruited, protected, public, captured, compelled, quarantined, hostile, missed, recovery_only]
luo_ji:
  owns: one_named_burn_attribution
  route_asset: route_asset.luo_ji_burn_attribution_physician
  independent_outcomes: [recruited, protected, copyright, medical, split_consent, captured, hostile, missed, recovery_only]
independence:
  recruiting_one_recruits_the_other: false
  one_testimony_substitutes_for_the_other: false
  one_miss_erases_the_other: false

Core rites 05 and 06 introduce the source cards. Their character reviews determine route recruitment, capture, hostility, or miss. Merely gaining a card at the source beat is not proof of permanent recruitment.

Event contract

The four events must remain bound to their exact source boundary:

  • Fever Line follows thermal triage.
  • Sponsor Bandage Audit follows the night queue while the bandage offer is visible.
  • Queue Riot or Mutual Aid follows the custody choice.
  • Discharge Review follows signed discharge.

Each event selects one response, writes a branch-specific durable flag, changes at least one counter/state, and may hand off to storyteller-rite-30-residue-audit. Event handoff does not grant archive or memorial authority.

Clean-bin separation

The company clean-bin packet is adjacent ST-SCALE-04 runtime only: a separate disposal packet, not a ninth clinic rite and not rite 07’s custody-disposition implementation. Its photo/no-photo result may be cited as a later custody fact, but it cannot:

  • advance clinic progress;
  • create any of the four source rows;
  • recruit Xi or Luo;
  • authorize treatment or discharge;
  • identify the disposed specimen;
  • satisfy the clinic lens by itself.

Authority invariants

authority_invariants:
  treatment_consent_equals_merchandising_consent: false
  public_record_equals_public_ownership: false
  thermal_chain_proves_identity: false
  queue_order_proves_diagnosis: false
  discharge_grants_future_use: false
  clinic_decides_identity_personhood_or_death: false
  clinic_grants_voice_rights: false
  clinic_grants_archive_or_memorial_rights: false
  clinic_grants_universal_medical_authority: false
  clinic_grants_universal_broadcast_authority: false

Non-goals

  • Not diagnosis, prescription, or universal treatment authorization.
  • Not identity, personhood, or death adjudication.
  • Not voice, archive, memorial, likeness, or merchandising ownership.
  • Not a generic cure-all for residue, blackout, or sponsor pressure.