Voice Custodian Counterclaim / 声权保管人反诉线

Voice Custodian Counterclaim is the system-facing storyline for the moment after a scoped Iris Vale voice row creates an affected custodian who can answer back.

The existing Iris and Mara character routes ask whether a named person can be protected, recruited, exposed, suppressed, made hostile, or recorded as absent. This top-level storyline asks the broader system question: did the counterclaim row itself stay visible enough for archive enforcement, protected witness payroll, route custody, sponsor gates, cutroom use, and broadcast reality to inherit it?

Playable Question

When a later actor tries to cite Iris’s voice near, beyond, or against its original boundary, does the producer preserve a real custodian answer, file counterclaim, bridge public testimony, sign scoped silence, shield the chain through edit, or record absence/default before a future reader treats the voice row as clean permission?

The answer must name:

• source voice row;
• accepted boundary and requested afteruse;
• affected custodian or explicit absence;
• custodian state before the answer;
• custody proof, channel, handler, and support or explicit absence;
• selected answer mode;
• relief, cost, and future-reader deltas;
• future route, enforcement, payroll, public, sponsor, cutroom, or broadcast-reality effect.

State-Triggered Entry

Open this storyline only from state pressure:

entry_state_required:
  trigger_kind: state_pressure
  source_voice_row_present: true
  source_row_is_scoped: true
  requested_afteruse_or_breach_present: true
  affected_custodian_or_explicit_absence_visible: true
  requested_custodian_answer_present: true
  custody_chain_known_or_testable: true
  future_reader_or_route_asset_present: true
  player_can_assign_answer_proof_handler_support_or_record_absence: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Do not open this storyline from a fixed chapter beat, generic legal pressure, raw counter threshold, dashboard state, lens health, or an Iris voice row that has no future reader.

Bound Content Pack

• 声权保管人反诉机制 defines the cross-custodian entry contract, branch contract, default state, and counter contract.
• Mara Fen 保管压力机制 handles Mara-specific person-state costs when Mara is the affected custodian.
• Iris Vale 保管人反诉线 binds the Iris-specific character route.
• Iris 声权保管人反诉案卷 records source row, custodian state, proof, answer request, support need, and future reader.
• Iris 声权保管人反诉听证 resolves affirmation, formal counterclaim, public testimony, sponsor sideletter, editorial shield, or default.
• Iris 保管人反诉默认 fires or arms when the custodian answer is hidden, unsupported, bought without release, edited without proof, or allowed to narrate first.
• Voice Custodian Counterclaim Lens observes this system wrapper independently from any one character lens.

Storyline Spine

Beat 1 - A scoped voice row reaches a new reader

The source can be a memorial probate row, afteruse citation, quarantine row, breach row, lawful annex, public acknowledgement, sponsor package, checksum path, or equivalent voice-custody surface.

The game records the source row and accepted boundary before allowing a later reader to consume it.

Beat 2 - A custodian answer becomes due

Create or refresh Iris Voice Custodian Counterclaim Docket when the requested afteruse needs Mara Fen, another custodian, or explicit absence to answer.

The docket must not reduce the custodian to present: true. It must expose custodian state, proof, support need, channel, handler, requested answer, and future reader.

Beat 3 - The hearing prices the answer

Run Iris Voice Custodian Counterclaim Hearing.

Valid answer families:

• custodian boundary affirmation;
• formal counterclaim;
• public testimony bridge;
• sponsor sideletter or managed silence;
• editorial chain shield;
• record absence or default.

Beat 4 - Future systems inherit the answer

Every branch leaves a durable reader. Archive enforcement, protected witness payroll, route custody, fan public, sponsor gate, cutroom use, broadcast reality, or a recovery route must know whether the answer was affirmed, contested, public, scoped private, edit-shielded, absent, hostile, captured, or recovery-only.

Beat 5 - Default blocks false-clean voice use

If source row, custodian, custodian state, custody proof, support, release record, handler, channel, answer mode, or future reader is hidden, Iris Custodian Counterclaim Default records who failed to answer and what future use became blocked, costlier, lawful-rider-required, public-rider-required, witness-payroll-due, enforcement-required, narrowed, false-owner-hardened, or recovery-only.

Branch Map

Branch	Immediate relief	Cost/scar	Future state
Custodian boundary affirmation	custody clarity, archive legitimacy, or future route acceptance improves	witness exposure, payroll, handler burden, or inspection heat rises	future citations must name the custodian boundary
Formal counterclaim	voice integrity, lawful custody, or proof accuracy improves	sponsor pressure, route asset pressure, bureau debt, or delay rises	archive enforcement or lawful rider is required
Public testimony bridge	public receipt, fan oxygen trust, or public witness strength improves	retaliation risk, pirate exposure, inspection heat, or payroll burden rises	protected witness payroll or public-route surcharge is due
Sponsor sideletter / managed silence	slot pressure or sponsor stop-loss pressure falls	contract capture, public distrust, loyalty doubt, or future blackmail cost rises	release record remains discoverable and surchargeable
Editorial chain shield	continuity or witness safety improves	edit debt, source ambiguity, archive debt, or future fraud cost rises	checksum annotation or lawful annex is required
Record absence / default	none cleanly	hostile custodian, false owner, missing support, or hidden future reader hardens	blocked, costlier, hostile, captured, or recovery-only voice afteruse

No branch may turn a custodian answer into universal permission for all future uses of Iris’s voice.

Missability And Recovery

This storyline is missed when implementation:

• consumes an Iris voice row without preserving the source boundary;
• hides the custodian or files the custodian only as a boolean;
• records Mara Fen as free permission instead of a protected, public, private, edited, captured, hostile, missed, or absent state;
• accepts sponsor silence without release record;
• accepts public testimony without protection cost;
• accepts edit shielding without checksum or lawful annex;
• omits future-reader effect;
• opens from fixed turn, fixed day/week, raw count, dashboard state, or lens health.

Recovery requires a new docket row naming the missing input and the scarred future reader. A recovered custodian answer can reopen route custody, enforcement, public acknowledgement, payroll, or cutroom use, but never as clean universal permission.