Storyteller Wiki

Protected Witness Payroll Lens / 受保护证人薪册 Lens

9 min read

Protected Witness Payroll Lens / 受保护证人薪册 Lens

This lens observes 受保护证人薪册, 受保护证人薪册机制, Route Assets and Custody, 归档执行案卷, 和解反震账本, and 认领撞锁.

It is observed through 受保护证人薪册, 证人薪册分诊, and 证人薪册泄露.

Observable promise

Storyteller must prove that recruited, protected, or exposed people are not free permanent route assets and not disposable flavor casualties.

A pass cannot be achieved by adding a generic wages counter, a relationship meter, or a prose line that a witness is safe. The implementation must expose a roster with source-person provenance, an assignable triage rite, divergent support branches, and leak/capture/hostile consequences that alter future route access or follower state.

Scope

This lens covers:

  • witnesses, carriers, followers, fan delegates, editor sources, archive clerks, memorial claimants, low-rank staffers, and equivalent people who can alter future routes;
  • states after recruitment/protection/exposure from custody, enforcement, claimant, aftershock, fan, editor, sponsor, or logistics content;
  • pay-and-shelter, audit oath, public shelter, sponsor retainer, editorial mask, defer, abandon, capture, hostile, disappearance, and sacrifice branches;
  • counter/state changes that include one visible relief and one visible cost;
  • multi-session proof that a person created in one replay can be loaded into a later support/payroll decision.

It does not cover generic staff salaries or passive affection.

State-triggered entry oracle

A valid replay or state inspection must open this lens from exposed-person support need, not fixed chronology.

Minimum entry evidence:

  1. a prior branch created, recruited, protected, exposed, or partially relied on a person;
  2. the person can still alter a future rite, route, proof chain, public receipt, archive order, sponsor claim, or broadcast reality state;
  3. the person has a support need or support risk: money, shelter, oath, alias, escort, fan oxygen support, sponsor retainer, edit mask, public apology, favor, or explicit missing support;
  4. at least two claimant pressures can reach the person or their record;
  5. the person is not terminally discharged, irreversibly captured, finally disappeared, or terminally hostile;
  6. a future route effect can be unlocked, blocked, made costlier, or converted to recovery-only.

Accepted source states include recruited, protected, route_asset, public_witness_recruited, carrier_protected_under_oath, runner_protected_under_oath, receipt_publicly_split, witness_route_asset, hostile, captured, missed, sacrificed, or equivalent.

Required observable content

Roster card

受保护证人薪册 or equivalent must record:

  • source storyline or source route state;
  • source session id and seed when available;
  • person id or explicit missing/hostile/captured state;
  • person state before payroll;
  • payroll/support state;
  • owed cost or explicit no-support failure;
  • handler or explicit no-handler failure;
  • claimant pressure;
  • future route effects.

Assignable triage rite

证人薪册分诊 or equivalent must require:

  • one roster or explicit missing-roster state;
  • one protected person or explicit missing/hostile/captured state;
  • one handler or explicit no-handler failure;
  • one support source or explicit no-support failure;
  • one claimant pressure target;
  • optional proof anchor or sacrifice/defer choice when relevant.

A famous handler alone must not satisfy this lens.

Leak event

证人薪册泄露 or equivalent must fire, resolve, or be recorded when support is unpaid, hidden, sponsor-captured, edit-contradicted, publicly overexposed, or captured by a claimant.

The leak must mutate future route access, route asset state, follower/witness state, blocked reasons, counters, or future difficulty. It cannot be mood text.

Required durable states

A satisfying implementation must expose durable states equivalent to at least eight of:

  • payroll_unopened
  • payroll_due
  • sheltered
  • paid_route_asset
  • audit_protected
  • public_shelter
  • sponsor_retained
  • masked_by_edit
  • payroll_deferred
  • unpaid_hostile
  • captured_witness
  • witness_disappeared
  • sacrificed_witness
  • terminal_clean_discharge

Branch divergence oracle

Branch A — Pay and shelter

Expected evidence:

  • assigned support is cash, safehouse, escort, staff favor, low-risk delivery support, or equivalent;
  • outcome sets sheltered, paid_route_asset, or equivalent;
  • witness retaliation risk, custody gap, or route asset pressure improves;
  • cash reserve, safehouse capacity, payroll leak, favor debt, or inspection heat worsens;
  • person remains assignable to at least one future rite.

Branch B — Audit oath protection

Expected evidence:

  • assigned actor/proof is official: Han Yanshuang, Inspector Rhee, archive seal, lawful oath, audit proof, or equivalent;
  • outcome sets audit_protected or equivalent;
  • archive signature legitimacy, custody clarity, public witness legitimacy, or admissibility improves;
  • inspection heat, bureau favor debt, sponsor pressure, or archive debt rises.

Branch C — Public shelter

Expected evidence:

  • assigned actor/proof is public-facing: Yu Lan, fan oxygen queue, public receipt, audience testimony, pirate relay, public witness chain, or equivalent;
  • outcome sets public_shelter or equivalent;
  • public receipt legitimacy, public witness legitimacy, fan oxygen balance, or audience stability improves;
  • fan oxygen liability, sponsor pressure, inspection heat, pirate exposure, or witness retaliation risk rises.

Branch D — Sponsor retainer / managed quiet

Expected evidence:

  • assigned actor/cost is managerial or sponsor-facing: Shen Luo, Orion Breath, sponsor quiet money, clean package, retainer language, manager bridge, or equivalent;
  • outcome sets sponsor_retained, payroll_deferred, or equivalent;
  • immediate slot, money, or retaliation pressure improves or pauses;
  • contract capture, public distrust, witness loyalty doubt, future blackmail cost, or fan resentment rises.

Branch E — Editorial mask

Expected evidence:

  • assigned actor/proof is editor/black-box-facing: Baiya, edit mask, alias, black-box cut, checksum, redaction, source tape patch, or equivalent;
  • outcome sets masked_by_edit or equivalent;
  • exposure, retaliation risk, or sponsor targeting decreases;
  • edit debt, reality drift, archive debt, public distrust, or future fraud cost rises.

Branch F — Abandon, suppress, sell, capture, disappear, or sacrifice

Expected evidence:

  • missing support, hidden roster, claimant first contact, sponsor/archive purchase, deliberate suppression, or witness sacrifice is recorded;
  • outcome sets unpaid_hostile, captured_witness, witness_disappeared, sacrificed_witness, or equivalent;
  • leak event or equivalent visible consequence fires;
  • future route access becomes blocked, costlier, hostile, captured, recovery-only, or sacrifice-only;
  • at least three relevant counters or durable states change.

Oracle assertions

A binding check should fail unless all assertions below are true.

  1. Primary links exist — the lens has populated observes and observed_through arrays pointing to concrete Storyteller pages.
  2. Entry is state-triggered — the surface opens from exposed-person support need, not fixed turn count.
  3. Source person exists — a prior branch created, recruited, protected, exposed, or relied on a person.
  4. Prior success remains true — payroll pressure cannot retcon the earlier recruitment/protection success.
  5. Support need is visible — money, shelter, oath, alias, escort, fan support, sponsor retainer, edit mask, apology, favor, or explicit absence is recorded.
  6. Roster memory exists — source person, person state, support state, owed cost, handler, claimant pressure, and future route effect are visible.
  7. Triage assignment exists — the rite requires roster, person, handler, support, claimant pressure, and blocked reasons or explicit absences.
  8. At least four branch families are playable — pay/shelter, audit oath, public shelter, sponsor retainer, editorial mask, and abandon/capture/sacrifice must not collapse into one result.
  9. No free permanent follower — success must spend or risk money, shelter capacity, payroll leak, favor debt, inspection heat, public exposure, sponsor capture, edit debt, or equivalent.
  10. Leak mutates state — leak, capture, hostile witness, disappearance, or sacrifice changes future route access, route asset state, follower/witness state, blocked reasons, counters, or future difficulty.
  11. Low-rank logistics can matter — at least one low-rank carrier, public witness, route asset, clerk, fan delegate, or editor source can be paid, protected, missed, hostile, captured, or sacrificed.
  12. Blocked reasons are visible — no person, terminal disappearance, absent handler, absent support, absent claimant pressure, no future route effect, or no visible cost must be reported.
  13. Multi-session provenance survives — evidence can show a person created in one replay/session being loaded into a later payroll triage without losing source state.
  14. No prose-only safety — implementation cannot pass with flavor text that a person is safe unless roster, rite, event, counters, and route/follower states are visible.

Progress metric

protectedWitnessPayrollProgress = 0..10:

  • 0: no source protected/exposed person.
  • 1: source person records an earlier recruited/protected/exposed state.
  • 2: person can affect at least one future rite, route, proof, receipt, archive order, sponsor claim, or broadcast reality state.
  • 3: 受保护证人薪册 or equivalent enters play with source person and support state.
  • 4: handler and support source are assignable or explicitly absent.
  • 5: claimant pressure and future route effect are assignable or explicitly absent.
  • 6: at least three branch choices are visible and gated by person/handler/support/claimant state.
  • 7: at least two successful or partial-success branches produce distinct payroll states and at least three deltas.
  • 8: leak, hostile witness, capture, disappearance, or sacrifice creates durable future route/follower cost.
  • 9: at least one protected person remains assignable or becomes blocked/captured/hostile due to payroll handling.
  • 10: multi-session or loaded-state replay proves source person provenance survives into payroll triage.

Evidence shape

lens_id: storyteller.lens.protected_witness_payroll.v1
session_id: lens-protected-witness-payroll-v1-<timestamp>
seed: <deterministic-seed>
source_person:
  source_session_id: <session_that_created_or_exposed_the_person>
  source_seed: <source_seed_if_available>
  source_storyline: archive_enforcement_docket | settlement_aftershock_ledger | claimant_collision_lock | field_logistics_runner | equivalent
  person_id: <witness_or_follower_or_route_asset_id>
  person_state_before: recruited | protected | route_asset | public_witness_recruited | carrier_protected_under_oath | hostile | captured | missed | sacrificed | equivalent
  prior_relief_recorded:
    - <counter_or_state_that_improved_due_to_that_person>
  prior_debt_recorded:
    - <counter_or_state_that_worsened_or_remains_unpaid>
state_context:
  roster: card.protected_witness_payroll_roster | equivalent | explicit_missing_roster
  payroll_state_before: payroll_unopened | payroll_due | sheltered | deferred | sponsor_retained | masked_by_edit | equivalent
  support_need: cash | safehouse | oath | alias | escort | fan_support | sponsor_retainer | edit_mask | apology | favor | explicit_absent
  live_claimants:
    sponsor: active | quiet | hostile | absent
    inspector_archive: active | quiet | hostile | absent
    fan_public: active | quiet | hostile | absent
    editor_blackbox: active | quiet | hostile | absent
    false_owner: active | quiet | hostile | absent
    pirate_relay: active | quiet | hostile | absent
  future_route_effect_before:
    usable_in_rites: []
    blocked_or_costlier_rites: []
offered_choices:
  - rite.witness_payroll_triage
  - pay_and_shelter
  - audit_oath_protection
  - public_shelter
  - sponsor_retainer_or_managed_quiet
  - editorial_mask
  - abandon_suppress_sell_capture_disappear_or_sacrifice
branch_runs:
  pay_and_shelter:
    selected_person: <id>
    selected_handler: security | lin_qiao | yu_lan | equivalent
    selected_support: cash | safehouse | escort | favor | equivalent
    outcome: sheltered | paid_route_asset
    counter_deltas:
      witness_retaliation_risk: -1
      payroll_leak: +1
      favor_debt: +1
    future_route_effects:
      unlocked:
        - <future_rite_accepts_person>
  public_shelter:
    selected_person: <id>
    selected_handler: yu_lan | fan_public | equivalent
    selected_support: fan_support | public_receipt | apology | equivalent
    outcome: public_shelter
    counter_deltas:
      public_receipt_legitimacy: +1
      fan_oxygen_liability: +1
      sponsor_stop_loss_pressure: +1
  negative_branch:
    selected_person: <id_or_absent>
    selected_handler: absent | suppressing_authority | sponsor | equivalent
    selected_support: absent | hidden_roster | sacrifice | equivalent
    event: event.witness_payroll_leak | equivalent
    outcome: unpaid_hostile | captured_witness | witness_disappeared | sacrificed_witness
    counter_deltas:
      route_asset_pressure: +1
      witness_loyalty_doubt: +1
      false_owner_hardening_risk: +1
assertions:
  - entry is state-triggered
  - roster records source person and support state
  - triage requires person handler support and claimant pressure
  - success has nonzero cost
  - negative branch changes future availability or difficulty
  - multi-session provenance survives

Non-goals

  • Not raw content scale.
  • Not a turn-count progression.
  • Not a generic salary economy.
  • Not a passive relationship system.
  • Not a free protection mechanic.
  • Not a governance or dashboard page.
  • Not satisfied by prose-only safety; branch evidence must come from replay/session state.

Graph View