Voice Custodian Counterclaim / 声权保管人反诉机制

Voice Custodian Counterclaim governs the moment when a scoped Iris Vale voice probate or afteruse citation creates an affected custodian who can answer back. It now delegates the person-state side of Mara Fen to Mara Fen 保管压力机制, while this mechanism remains responsible for the counterclaim row and the future reader that will consume it.

A prior row may already say that Iris Vale’s memorial voice can be used, cited, quarantined, or breached. This mechanism asks whether Mara Fen or an equivalent custody witness accepts that afteruse boundary, contests it, sells a scoped release, testifies publicly, shields the chain through edit, disappears, or hardens into a hostile witness.

Primary playable question

When a later actor cites Iris’s voice beyond, near, or against its original boundary, does the custodian become an affirming witness, a formal counterclaimant, a protected public witness, a managed silence, an editorial shield, or the author of a future breach?

A valid answer must name the source afteruse row, custodian or explicit absence, custody proof, requested answer, protection or support surface, and future reader.

If the custodian is Mara, the implementation must also expose Mara’s state through Mara Fen 保管分岔案卷 or an equivalent row. Mara cannot be consumed as free permission.

State-triggered entry

Open this mechanism only from state pressure:

entry_state:
  trigger_kind: state_pressure
  source_probate_or_afteruse_row_present: true
  source_row_is_scoped: true
  requested_afteruse_or_breach_present: true
  affected_custodian_or_explicit_absence_visible: true
  custody_chain_known_or_testable: true
  requested_custodian_answer_present: true
  future_reader_or_route_asset_present: true
  player_can_assign_answer_proof_handler_or_record_absence: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true

Valid entry states include reader mismatch, sponsor repackaging, public overcite, checksum overcite, stale copy, quarantine breach, false probate citation, or a lawful citation that still requires custodian acknowledgement.

Required surfaces

A valid implementation has four surfaces when Mara is involved:

1. Counterclaim docket — records source voice row, afteruse pressure, custodian state, custody proof, requested answer, support need, and future reader.
2. Mara custody branch docket — records Mara-specific state, support need, answer posture, and future reader effect.
3. Counterclaim hearing — chooses affirmation, formal counterclaim, public testimony, sponsor sideletter, editorial shield, or absence/default.
4. Default event — mutates future play when the custodian is hidden, unsupported, bought without release, edited without proof, or allowed to narrate first as hostile witness.

Custodian counterclaim states

voice_custodian_counterclaim_states:
  - counterclaim_unopened
  - counterclaim_due
  - custodian_boundary_affirmed
  - formal_counterclaim_filed
  - public_testimony_armed
  - sponsor_sideletter_scoped
  - editorial_chain_shielded
  - custodian_absent_recorded
  - custodian_hidden_or_unpaid
  - hostile_custodian
  - false_owner_hardened
  - recovery_only_voice_afteruse

The implementation must preserve the difference between affirmation, counterclaim, public testimony, managed silence, editorial shield, absence, hostile custodian, false owner hardening, and recovery-only afteruse.

Branch contract

Branch A — Custodian boundary affirmation

The custodian confirms that the requested use is inside the scoped row or can pass with an acknowledgement rider.

Expected result:

• custody clarity, archive signature legitimacy, or future route acceptance improves;
• witness exposure, protection cost, inspection heat, or payroll duty rises;
• future citations must name the custodian boundary.

Branch B — Formal counterclaim

The custodian contests the afteruse and demands injunction, rider, quarantine, or stronger proof.

Expected result:

• voice integrity, lawful custody, or proof accuracy improves;
• sponsor pressure, route asset pressure, bureau debt, or public delay rises;
• 归档执行案卷 can consume the order or refusal.

Branch C — Public testimony bridge

The custodian or witness chain answers through public receipt, historian relay, fan oxygen queue, or audience testimony.

Expected result:

• public receipt legitimacy, fan oxygen trust, or public witness strength improves;
• retaliation risk, pirate exposure, inspection heat, or witness payroll burden rises;
• 受保护证人薪册 can consume the exposed person.

Branch D — Sponsor sideletter or managed silence

Management or sponsor pressure buys a scoped release, quiet window, or sideletter without making it universal.

Expected result:

• immediate slot pressure or sponsor stop-loss pressure improves;
• contract capture, public distrust, witness loyalty doubt, or future blackmail cost rises;
• the release record remains discoverable and future readers may surcharge or reject it.

Branch E — Editorial chain shield

Cutroom or black-box work masks the custodian’s exposure while preserving a checksum, annotation, or lawful annex.

Expected result:

• continuity hazard, retaliation risk, or source exposure decreases;
• edit debt, source ambiguity, archive debt, or future fraud cost rises;
• later use requires checksum annotation or lawful annex.

Branch F — Absence, hostile witness, or false owner default

The custodian is absent, hidden, unpaid, captured, bought without release, edited without proof, or allowed to narrate first.

Expected result:

• Iris 保管人反诉默认 fires or is armed;
• if Mara is the custodian, Mara Fen 敌对证人默认 also fires or is armed;
• at least one future route becomes blocked, costlier, hostile, captured, rider-required, or recovery-only;
• at least three counters or durable states change.

Counter contract

Every non-default branch must have one relief, one cost, and one future reader or route effect. Default has no clean relief.

Primary counters and durable states:

• custodian_counterclaim_state
• mara_fen_state
• voice_integrity
• custody_clarity
• archive_signature_legitimacy
• archive_debt
• inspection_heat
• witness_exposure
• witness_payroll_due
• public_receipt_legitimacy
• public_receipt_distrust
• fan_oxygen_trust
• fan_oxygen_resentment
• sponsor_stop_loss_pressure
• contract_capture
• route_asset_pressure
• source_ambiguity
• edit_debt
• future_blackmail_cost
• false_owner_hardening_risk

Mara integration requirement

When the custodian is Mara, a passing implementation must satisfy all of the following:

mara_integration:
  mara_state_or_explicit_absence_visible: true
  support_need_or_explicit_absence_visible: true
  answer_posture_visible: true
  future_reader_effect_changes_by_mara_state: true
  recruitment_not_universal_permission: true
  sponsor_suppression_not_clean_consent: true
  public_witness_not_lawful_chain_without_bridge: true
  editor_mask_not_raw_proof: true
  hostile_or_absent_default_durable: true

Integration notes

• With 验讫后用引证机制, this mechanism consumes the affected-party slot and asks whether that party can answer.
• With 纪念声权验讫机制, it protects the first probate row from being converted into a universal voice license.
• With Mara Fen 保管压力机制, it delegates Mara’s character-state costs instead of flattening her into a boolean.
• With 归档执行案卷, a formal counterclaim can become an enforceable order.
• With 受保护证人薪册, an exposed custodian becomes a person who must be paid, hidden, sheltered, or risked.
• With Route Assets and Custody, bad handling narrows, blocks, or scars future voice routes.
• With Broadcast Reality, a silent or hostile custodian can let aired memory drift into ownership.

Non-goals

• Not a second first-use probate.
• Not a generic legal objection.
• Not a fixed chronology beat.
• Not a free Mara Fen recruitment branch.
• Not valid if the custodian is only prose, mood, or an invisible field.
• Not valid unless a downstream route, reader, enforcement, payroll, custody, or broadcast state can consume the answer.