Operator Witness Conclave / 操作员证词合议线

Operator Witness Conclave is a pressure-system storyline for the moment when several low-rank operator witnesses become relevant to one later case and their rows do not cleanly agree.

This storyline is built for the current post-green gap: Storyteller now has strong single-operator character lines. 楼刻字幕切换员线 can preserve caption scope. 陆纷切条分发跑腿线 can preserve clipped recap scars. 岑回逆流引座员线 can preserve late backflow receipts. But future play still needs a surface for the case where a route, recap, proof burden, or management report tries to consume more than one of them.

The dramatic question is:

When the staff rows conflict, does the producer seat the operators and preserve dissent, split readers, protect a minority row, publish the contradiction, seal it narrowly, summarize it with a scar, or let a senior proxy overwrite them into false consensus?

Gap this storyline fills

The current mesh already prevents many local cleanups:

• 字幕证词羁押线 prevents captions from becoming source truth.
• 公开回顾捕获线 prevents recap wording from erasing scars.
• 漏点名复核线 prevents all-clear rows from becoming universal presence.
• 受保护证人薪册 prices ongoing protection for a person who becomes evidence.
• 举证负荷再分配线 assigns continuing proof burden.
• 经营压缩台 prevents scarred success from becoming clean yield.

The remaining gap is cross-operator false consensus. A caption row, clip row, and backflow row can all be individually valid and still contradict one another. Without a playable conclave, a senior proxy can cite staff agreement and erase the operator who carried the inconvenient scar.

This storyline binds:

• 操作员证词合议机制;
• 操作员合议案卷;
• 操作员合议听证;
• 高位代理覆盖默认.

Primary playable question

A future reader needs a staff-derived truth. Multiple operator rows exist, but their reader scopes, source timing, and scar limits do not agree.

Do you:

• seat the conclave and preserve scoped contradiction;
• preserve the dissenting row as payable/protected witness state;
• split the future reader into public, lawful, access, sponsor, archive, or route-only surfaces;
• protect the minority operator before reuse;
• publish a contradiction addendum;
• seal the result lawful-only or archive-only;
• let management summarize the conflict with an explicit metric scar;
• or allow a senior proxy to overwrite the operators and arm a durable default?

Every answer must show source operator rows, requested merged claim, contradiction kind, harmed reader, beneficiary, operator state changes, future reader, relief, cost, and future route effect.

State-triggered entry

Open only from live state pressure:

entry_state_required:
  trigger_kind: state_pressure
  operator_rows_conflict_visible: true
  source_operator_rows_have_cards: true
  requested_merged_claim_present: true
  contradiction_kind_present: true
  harmed_reader_if_merged_visible_or_explicit_absence: true
  beneficiary_of_merge_visible_or_explicit_absence: true
  future_reader_or_route_consumes_result: true
  player_can_seat_preserve_split_protect_publish_seal_summarize_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_operator_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Invalid entry examples: fixed sequence position, chapter quota, raw staff count, generic aftercare phase, relationship score, dashboard state, lens-health state, or management anger without a future reader.

Storyline spine

Beat 1 — A future case asks for staff truth

A route, slot, recap, caption reliance claim, roll-call recheck, proof burden, management metric, archive release, sponsor package, or broadcast-reality check asks for one staff-derived answer.

Examples:

• a public recap wants to quote the caption track and clip package as if they match;
• a roll-call recheck wants the late backflow receipt to validate a prior all-clear;
• a sponsor package wants 陆纷’s clip and 楼刻’s caption to count as public consent;
• a proof-burden route wants one operator to maintain a row that another operator actually carried;
• a management report wants staff agreement to clean a scarred success.

Beat 2 — The operator rows disagree

Create or update 操作员合议案卷. The docket must name row-by-row operator, source card, source state, asserted truth, reader scope, scar or limit, future case, requested merged claim, contradiction kind, harmed reader, beneficiary, and future consumer.

The contradiction can be narrow:

• access caption proves a harmed reader saw a protected wording, while the sponsor clip omitted it;
• recap fragment preserved a scar tag, while backflow receipt shows the all-clear was narrower;
• a lawful-only seal proves admissibility, while public route tries to cite it as public agreement;
• a captured operator is being counted as neutral;
• an absent operator is being counted as staff agreement.

Beat 3 — The hearing chooses what happens to dissent

Run 操作员合议听证.

Branch families:

1. seat conclave;
2. preserve dissent;
3. split by reader;
4. protect minority operator;
5. publish contradiction addendum;
6. lawful/archive seal;
7. management summary with scar;
8. senior proxy overwrite/default.

Beat 4 — Operator states mutate future play

A valid branch changes at least one operator state and one future reader state. The outcome can make a route safer, but never universally clean.

Valid after-states include:

• dissent_preserved;
• reader_split_required;
• minority_operator_protected;
• contradiction_addendum_published;
• lawful_or_archive_seal_only;
• management_summary_with_scar;
• false_staff_consensus;
• hostile_overwritten_operator;
• operator_conclave_recovery_only.

Beat 5 — Default records the false consensus

If the docket is absent, source rows are merged without scope, dissent is hidden, a senior proxy files first, or a future route consumes staff consensus without operator states, 高位代理覆盖默认 fires or arms.

The default must name overwritten operator rows, false clean claim, default narrator, beneficiary, harmed reader, missing inputs, state after, future effect, and counter deltas.

Branch map

Branch	Immediate relief	Cost/scar	Future state
Seat conclave	source contradiction becomes legible	delay, handler burden, exposure	future reader sees scoped conflict
Preserve dissent	minority row cannot be erased	protected witness payroll, retaliation, route delay	dissent preserved; addendum required
Split by reader	incompatible publics proceed separately	edit debt, route delay, contradiction pressure	public-only/lawful-only/access-only/sponsor-only
Protect minority operator	endangered operator remains usable	payroll, safehouse, lawful seal, schedule cost	protected operator required before reuse
Publish contradiction addendum	public or route truth improves	public distrust, sponsor pressure, license heat	addendum required before reuse
Lawful/archive seal	evidentiary survival improves	lawful-only gate, archive debt, inspection heat	lawful-only or archive-only acceptance
Management summary with scar	board route proceeds without full merge	metric scar, management compression pressure	management summary remains costed
Senior proxy overwrite/default	fastest clean story files first	false consensus, hostile operator, correction cost	blocked, costlier, recovery-only, ending scar

No branch may let one operator row, one senior proxy, or one clean summary satisfy public, lawful, sponsor, access, archive, route asset, management, and broadcast-reality readers at once.

Character hooks

• 楼刻 can make an access-caption row legible, but cannot make the full source clean.
• 陆纷 can preserve clip scar tags, but cannot make a short fragment equal the recap.
• 岑回 can carry late backflow proof, but cannot clean the prior all-clear.
• Shen Luo can chair a management summary only if metric scar and harmed reader remain visible.
• Yu Lan can publish contradiction, but public distrust, witness exposure, or sponsor pressure rises.
• Han Yanshuang can seal a row lawful-only, but public consensus and route cleanliness remain unresolved.
• Baiya can attach checksum or edit proof, but source ambiguity or edit debt must remain.

Named handlers are not free overrides. They mutate scope, proof, cost, operator state, or future route state.

Counter contract

Every resolved or defaulted branch must mutate at least three surfaces:

counter_deltas_required:
  relief: at_least_one
  cost: at_least_one
  future_reader_or_route_effect: at_least_one

Primary surfaces:

• source_contradiction_legibility
• operator_conclave_integrity
• false_staff_consensus
• operator_exposure
• handler_burden
• protected_witness_payroll_due
• management_pressure
• producer_license_pressure
• sponsor_stop_loss_pressure
• archive_debt
• public_receipt_legitimacy
• public_receipt_distrust
• access_harm_erasure
• route_asset_integrity
• route_delay
• correction_required
• recovery_only_pressure

Missability and recovery

The storyline is missed when future play consumes staff agreement, operator corroboration, senior staff summary, one clean caption, one clean clip, late receipt clean all-clear, or management consensus without 操作员合议案卷.

Missed/default states include:

• senior_proxy_overwrite;
• false_staff_consensus;
• hostile_overwritten_operator;
• captured_dissent;
• correction_required;
• route_blocked;
• operator_conclave_recovery_only;
• ending_scar.

Recovery is allowed only with visible scar:

• reopen the docket;
• seat the hearing;
• publish contradiction addendum;
• split readers;
• protect or payroll the overwritten operator;
• apply lawful/archive-only seal;
• mark management summary as scarred;
• accept public-only, lawful-only, sponsor-only, blocked, costlier, hostile, or recovery-only future use.

Replay evidence expectation

storyline_id: storyteller.storyline.operator_witness_conclave.v1
session_id: lens-operator-witness-conclave-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  operator_rows_conflict_visible: true
  source_operator_rows_have_cards: true
  requested_merged_claim_present: true
  contradiction_kind_present: true
  future_reader_or_route_consumes_result: true
  no_fixed_turn_trigger: true
source_operator_rows:
  - operator: <operator id>
    source_card: <card id>
    source_state: <state>
    asserted_truth: <truth>
    reader_scope: <scope>
    scar_or_limit: <scar or explicit_absence>
conflict_surface:
  future_case_id: <case>
  requested_merged_claim: <claim>
  contradiction_kind: <kind>
  harmed_reader_if_merged: <reader or explicit_absence>
  beneficiary_of_merge: <actor or explicit_absence>
offered:
  card: storyteller.card.operator_conclave_docket.v1
  rite: storyteller.rite.operator_conclave_hearing.v1
branch_result:
  selected_posture: seat_conclave | preserve_dissent | split_by_reader | minority_operator_protection | publish_contradiction_addendum | lawful_or_archive_seal | management_summary | senior_proxy_overwrite_default
  conclave_state_after: <state>
  operator_state_changes: []
  future_reader_or_route_effect: <effect>
  emitted_event_or_absence: storyteller.event.senior_proxy_overwrite_default.v1 | explicit_absence
  counter_deltas:
    relief: []
    cost: []
    future: []
assertions:
  - entry_is_state_triggered
  - source_operator_rows_are_separate
  - contradiction_and_future_reader_are_visible
  - dissent_or_overwrite_state_is_visible
  - branch_outcomes_diverge
  - every_success_has_relief_cost_and_future_effect
  - senior_proxy_default_mutates_future_play
  - no_universal_staff_consensus
  - no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_trigger

Non-goals

• Not a governance or design-method page.
• Not a raw lens-count addition.
• Not a generic staff meeting.
• Not a fixed-turn escalation.
• Not a replacement for the individual operator lines.
• Not a clean proof aggregation system.
• Not valid unless conflicting operator rows change future route, proof burden, management report, public recap, roll-call, caption reliance, or ending-scar play.