Crystal Dorm Facility Board / 水晶宿舍设施板机制

The Crystal Dorm Facility Board converts a successful construction promise into a persistent management surface. It tracks one exact facility, two exact staff capacities, five facility operations, two interruption/failure events, and the difference between the dorm’s public face and hidden use.

The mechanism is deliberately facility-local. It does not define every facility, every safehouse, every clinic, or every inspection. Its identity is the exact Crystal Dorm facility ID plus the artist-safehouse route interaction.

Entry handoff

facility_board_entry:
  required_predecessor_flag: storyteller_st_scale_01_crystal-dorm-plan_success
  required_facility_id: card-storyteller-st-scale-07-crystal-dorm-facility
  required_route_interaction: artist-safehouse
  rejects:
    - generic_build_success
    - another_st_scale_01_contract_success
    - another_st_scale_07_facility
    - unbound_placeholder_permit

ST-SCALE-01 decides whether the Crystal Dorm plan succeeds. ST-SCALE-07 begins after that success and makes the built promise operable. The handoff must not be replaced by a generic permit card that is absent from the bound three-card packet.

Exact object registry

crystal_dorm_registry:
  cards:
    facility: card-storyteller-st-scale-07-crystal-dorm-facility
    medic_slot: card-storyteller-st-scale-07-crystal-dorm-medic-slot
    witness_guard_slot: card-storyteller-st-scale-07-crystal-dorm-witness-guard-slot
  rites:
    build: storyteller-rite-st-scale-07-crystal-dorm-build
    staff: storyteller-rite-st-scale-07-crystal-dorm-staff
    repeatable_use: storyteller-rite-st-scale-07-crystal-dorm-repeatable-use
    inspection: storyteller-rite-st-scale-07-crystal-dorm-inspection
    repurpose: storyteller-rite-st-scale-07-crystal-dorm-repurpose
  events:
    inspection: storyteller-event-st-scale-07-crystal-dorm-inspection
    fold_accident: storyteller-event-st-scale-07-crystal-dorm-fold-accident
  compatible_staff_tags: [medic, witness-guard]
  public_face: transparent_idol_dorm_livestream_set
  hidden_use: witness_safehouse_and_throat_injury_care_compartment

All ten bound objects must keep scaleFamily: ST-SCALE-07, the exact Crystal Dorm facilityId, and routeInteraction: artist-safehouse where that metadata applies. The medic and witness-guard cards are exact allocated role-capacity tokens. Possession is not allocation: only placing one through the staff rite records facility_crystal-dorm_staffed. Neither token identifies, recruits, employs, protects, or authorizes a person.

Facility state

crystal_dorm_state:
  predecessor_success: boolean
  built: boolean
  staffed: boolean
  inspection_triggered: boolean
  inspection_recorded: boolean
  safehouse_unlocked: boolean
  repeatable_operation_summary:
    runs: counter.crystal_dorm_operation_runs
    ever_public: flag.facility_crystal-dorm_use_public_face
    ever_hidden: flag.facility_crystal-dorm_use_hidden_use
    last_public: flag.facility_crystal-dorm_last_operation_public_face
    last_hidden: flag.facility_crystal-dorm_last_operation_hidden_use
    last_flags_mutually_exclusive: true
  selected_posture_by_rite:
    build: public_face | hidden_use | unresolved
    staff: public_face | hidden_use | unresolved
    inspection: public_face | hidden_use | unresolved
    repurpose: public_face | hidden_use | unresolved
  counters:
    - facility_integrity
    - artist_trust
    - inspection_risk
    - spectacle_yield
    - hidden_use
    - audit_heat
    - public_accountability
    - sponsor_control
    - staff_fatigue
    - death_pressure

Each repeated use increments crystal_dorm_operation_runs, preserves an ever-public or ever-hidden flag, clears the opposite last-posture flag, and sets the newly selected last-posture flag. Those state fields expose run count, posture history membership, and the latest posture. The durable replay/turn log preserves the full selected-posture order; focused evidence compares snapshots after sequential runs instead of demanding that final aggregate counters reconstruct that order by themselves.

Transition table

Step	Exact prerequisite	Timing	Required base output	Additional posture output
Build	predecessor success + exact facility	8-day long operation	facility_integrity +2, built flag	public: spectacle/risk; hidden: trust/hidden/audit
Staff	built + exact facility + exact medic or witness-guard role-capacity token	quick	artist_trust +1, staff_fatigue +1, staffed-capacity flag	public: spectacle/risk; hidden: trust/hidden/audit
Repeatable use	staffed capacity + exact facility + exact role-capacity token	quick, repeatable	facility_integrity +1, inspection_risk +1, spectacle_yield +1, operation-runs +1	public/hidden ever flag + mutually exclusive last-posture flag, plus branch counters
Inspection rite	inspection-triggered + built + staffed capacity + inspection risk >= 1 + exact facility + exact role-capacity token	same day	inspection_risk -1, public_accountability +1, inspection-recorded flag	public: spectacle/risk; hidden: trust/hidden/audit
Repurpose	inspection recorded + built + exact facility + exact role-capacity token	same day	repurpose-recorded flag	public: retain showroom + spectacle/risk, no safehouse; hidden: trust/sponsor relief/hidden/audit + safehouse-unlocked

The runtime may express the predecessor success as a trigger or condition, but the entry must be observable and must block build before the exact ST-SCALE-01 success. All later prerequisites are conjunctive and facility-local.

The sequenceIndex metadata is a registry order, not a claim that repeatable use must occur before inspection. The state graph has a spine plus an interrupt:

build -> staff -> repeatable use (zero or more times)
  |        |                 |
  +--------+-----------------+-> inspection interrupt when risk >= 1
                                  -> selected event stance
                                  -> staffed-capacity inspection response
                                  -> repurpose decision

A public-face build raises inspection risk immediately, so the event may open before staffing or repeatable use. The event waits on built plus risk. The response rite cannot run until an event stance has written facility_crystal-dorm_inspection_triggered; it also needs staffed capacity and an exact role-capacity token.

Public/hidden posture contract

Every one of the five rites exposes both stable option IDs.

public_face

The dorm is presented as a transparent idol-living set. The option adds spectacle and inspection risk. Public visibility does not erase the safehouse claim, prove that residents agreed to surveillance, or grant sponsor access to every room.

hidden_use

The witness-safehouse and throat-care compartment are actively used. The option adds artist trust and hidden-use state while increasing audit heat. Acknowledging the hidden route does not establish medical consent, witness ownership, or authority to capture testimony.

The two options must have distinct effects and must remain readable per selected rite. The mechanic fails if both options collapse into a generic facility_used result.

Repeatable operation pressure

storyteller-rite-st-scale-07-crystal-dorm-repeatable-use is the ongoing management loop. It is available only after capacity has been allocated through the staff rite and requires an exact medic or witness-guard role-capacity token on every run.

per_operation_minimum:
  facility_integrity_delta: +1
  inspection_risk_delta: +1
  spectacle_yield_delta: +1
  crystal_dorm_operation_runs_delta: +1
  posture: public_face | hidden_use
  ever_posture_flag_set: true
  selected_last_posture_flag_set: true
  opposite_last_posture_flag_cleared: true
  posture_cost_visible: true

Public-facing operation compounds inspection risk. Hidden operation compounds audit heat. Neither is a zero-cost optimal posture. Repeating the rite must never suppress the inspection event, clear earlier pressure, or count as a recorded inspection. Runtime state summarizes count, ever-posture membership, and last posture; the durable replay/turn log preserves full order. The focused test compares the first and second post-run snapshots to prove the last flags flip without erasing the ever flags.

Inspection interruption

The surprise-inspection event requires the built flag and inspection risk at least one. It does not require staffed state or repeatable-use history. A public-face build can therefore expose it immediately. Every selected event response writes facility_crystal-dorm_inspection_triggered; the exact branch consequences are:

• show_public_face: spectacle yield +1, inspection risk +1;
• route_inspector_to_hidden_use: public accountability +1, artist trust +1, audit heat +1, with inspection risk unchanged;
• seal_room_for_sponsor: sponsor control +2, artist trust -1, inspection risk +1, facility integrity -3.

These event response IDs are not substitutes for the rite’s public_face and hidden_use posture IDs. The event opens the interruption and records the selected stance. The rite requires that triggered flag, staffed capacity, the exact facility, and an exact role-capacity token, then records the same-day response and creates facility_crystal-dorm_inspection_recorded. It cannot be resolved before an event stance is selected.

The sponsor-seal integrity loss is a deliberate endogenous fold route. ST-SCALE-01 success contributes one integrity, Crystal Dorm build adds two, and seal_room_for_sponsor subtracts three. The result is zero integrity with the inspection triggered and unrecorded, satisfying the concrete fold entry without an invented timer.

The inspection rite may reduce current inspection risk, but its own selected posture can add risk or audit heat again. That is intended: inspection creates an answerable record rather than a universal clean bill.

Safehouse repurpose

The repurpose rite is reachable only after an inspection record exists. Its base effect records facility_crystal-dorm_repurpose_recorded; safehouse authority is not a base effect.

• public_face writes the public repurpose result, retains the showroom, and adds spectacle and inspection risk. It does not write facility_crystal-dorm_artist-safehouse_unlocked.
• hidden_use writes the hidden repurpose result, raises artist trust, reduces sponsor control, adds hidden-use and audit pressure, and alone writes facility_crystal-dorm_artist-safehouse_unlocked.

Safehouse unlock is a route capability. It does not automatically:

• recruit or protect every artist;
• resolve Mu Ning’s route;
• qualify an untagged person as a medic or witness guard;
• grant diagnosis, treatment, body, voice, archive, or memorial authority;
• make another ST-SCALE-07 facility a safehouse.

Fold accident

fold_accident_entry:
  semantic_missed_rite: storyteller-rite-st-scale-07-crystal-dorm-inspection
  inspection_triggered: true
  inspection_recorded: false
  facility_integrity_lte: 0
  relative_day_timer_required: false
fold_accident_output:
  common_flag: facility_crystal-dorm_fold_accident_triggered
  branches:
    fold_to_black_screen:
      death_pressure: +1
      downstream_card: card-storyteller-st-scale-02-glass-dorm-scandal
      public_accountability: 0
    convert_to_public_accountability:
      public_accountability: +2
      folded_card_granted: false
    bury_as_sponsor_maintenance:
      sponsor_burial_or_capture_pressure: true
      public_conversion: false

All three concrete state facts are required: the inspection triggered, its response was not recorded, and integrity is nonpositive. They are the executable meaning of the semantic missed-rite marker; no unsupported relative-day timeout is inferred. Low integrity before an inspection trigger, an unrecorded inspection while integrity remains positive, or a recorded response is not the exact fold-accident state. The three options must have mutually exclusive effects: the existing Glass Dorm Scandal card and death pressure belong only to the black-screen branch, public accountability belongs only to its conversion branch, and sponsor burial/capture pressure belongs only to the sponsor branch. The downstream ST-SCALE-02 card proves one consequence; it is not a fourth card in this mechanism’s bound input registry.

Isolation from adjacent facilities

The Blackbox Editing Room, Fan Interaction Hall, and Whitebox Evidence Vault share the broad ST-SCALE-07 facility-board grammar, but each has different facility IDs, staff tags, counters, route interactions, and events. No sibling facility may provide the Crystal Dorm built, staffed, inspection, repurpose, or fold state.

Likewise, pre-build broadcast-license acceptance and expiry are upstream authorization concerns, while named-character recruitability is a character-route concern. This mechanism owns only post-success Crystal Dorm facility operation.

Authority invariants

allowed_outputs:
  - exact_facility_state
  - exact_role_capacity_allocation
  - operation_posture
  - local_counter_deltas
  - inspection_record
  - safehouse_route_capability
  - fold_accident_record
forbidden_outputs:
  - resident_or_witness_ownership
  - blanket_surveillance_consent
  - treatment_or_diagnosis_consent
  - body_or_voice_capture_consent
  - personhood_or_death_finding
  - archive_or_memorial_custody
  - naming_likeness_or_merchandising_rights
  - universal_facility_access
  - blanket_broadcast_authority

The allowed role-capacity result is facility-local operational state. It is never evidence that a person has been identified, recruited, employed, medically credentialed, assigned, protected, or authorized.