Proxy Posture Chain / 代理人姿态链

Proxy Posture Chain is the storyline for the moment when Storyteller’s legal, sponsor, archive, fan, edit, and production pressures stop being abstract rows and become people.

The current corpus can already underwrite liability, call recourse, release collected targets, commit faction reserves, triage production lanes, protect witnesses, and mutate route assets. The missing RPG surface is the human carrier: the manager who signs the bridge, the fan organizer who speaks for oxygen, the archive clerk who knows which copy moved, the editor who patches the checksum, the inspector aide who can quietly admit a proof, the runner who carries a key, or the witness who becomes too visible.

This storyline makes that carrier recruitable, retainable, suppressible, exposable, tradable, missable, hostile, or recovery-only.

Primary playable question

When a management pressure row requires a person to carry it, does the player protect, recruit, temporarily retain, suppress, expose, trade, abandon, or lose that proxy — and how does that human posture mutate future route access, proof custody, staffing capacity, public legitimacy, faction posture, or broadcast reality?

Every branch must show:

• the source pressure that created the proxy;
• the proxy’s concrete name or role;
• who is claiming the proxy;
• what the proxy is asked to do;
• the player input or explicit absence;
• the proxy posture before and after;
• the relief gained;
• the future cost or scar.

Why this is the next useful expansion

The current green surface is strong along the legal and asset chain:

• 派系责任承保 makes future harm callable.
• 担保追偿级联 makes a payer’s recovery right collectible.
• 追偿放行线 makes seized targets releasable only through scars.
• 派系承诺账本 makes faction pressure finite.
• 制作分诊台 makes lanes and handlers scarce.

The uncovered gap is character posture inheritance. Those systems can mutate objects, rooms, routes, ledgers, receipts, and counters, but the person carrying the pressure can still be treated as a disposable helper. That weakens the management + RPG promise: the player should not only manage slots and legal claims; the player should also build, burn, suppress, or lose a living network.

This storyline binds:

• 代理人姿态链机制;
• 代理人姿态案卷;
• 代理人姿态听证;
• 代理人倒戈破口.

State-triggered entry

Open this storyline when all of the following are true:

1. a prior or current branch created a pressure row: liability exposure, recourse target, collection release, faction commitment, production triage ticket, public contrition receipt, witness reprisal row, facility access escort, route asset custody dispute, archive order, edit checksum, sponsor settlement, fan oxygen queue, or pirate relay;
2. that pressure requires a human carrier: signer, manager bridge, proof source, public voice, runner, escort, editor, clerk, inspector aide, fan organizer, security handler, witness guard, relay host, or substitute collateral;
3. at least two claimants would prefer different proxy postures;
4. the proxy has not reached terminal death, terminal disappearance, final faction lock, irreversible public discharge, or clean recruitment;
5. a branch can still mutate future route access, proof custody, faction posture, staffing capacity, public legitimacy, or broadcast reality.

This entry is driven by live pressure and proxy state. It has no fixed numbered trigger.

Storyline spine

Beat 1 — Pressure row asks for a person

A live surface demands a human carrier. The demand may come from a recourse docket, release receipt, faction commitment row, triage ticket, witness payroll entry, public contrition claim, facility access route, or edit/inspection proof gap.

The player receives or updates 代理人姿态案卷. The row names the proxy, source pressure, requested role, faction claim, rival claim, current posture, risk if used, and future route effect.

Beat 2 — Claimants try to define the proxy

At least two claimant families should disagree.

Examples:

• sponsor wants Shen Luo’s bridge to become private retainer, while Yu Lan wants public wording;
• inspector wants an aide to testify lawfully, while Baiya needs the same person to preserve checksum ambiguity;
• fan public wants an organizer exposed, while management needs them protected;
• archive wants a clerk to bind copy custody, while editor wants them quiet;
• production wants a runner for a facility key, while a witness chain needs the same runner for safehouse escort.

Beat 3 — Hearing resolves posture

The player opens 代理人姿态听证 and selects recruit, retain, suppress, expose, trade, or abandon/fail.

A valid branch must assign a handler or explicitly record absence. It must also assign protection, price, legal cover, public cover, edit credit, room route, proof anchor, route share, or explicit absence.

Beat 4 — Relief creates a human scar

The selected posture can improve a route, proof, public legitimacy, staffing capacity, room access, or pressure row. It must also create a future cost: protection debt, payroll debt, contract capture, bureau favor debt, fan resentment, witness exposure, edit debt, source ambiguity, facility access pressure, route asset pressure, claimant hostility, or black-screen pressure.

No clean recruitment, clean suppression, or clean trade is valid.

Beat 5 — Miss, defection, or recovery persists

If the proxy is missed, unpaid, unprotected, overexposed, suppressed badly, traded without scar, claimed first by a faction, or recruited too cleanly, 代理人倒戈破口 fires or is recorded.

The break does not have to delete the proxy. It can leave hostile, faction-bound, missing, or recovery-only state.

Branch model

Branch A — Recruit proxy

The player protects, pays, legitimizes, or proves enough to turn the proxy into a durable ally, follower, handler, witness bridge, edit bridge, legal bridge, route asset, or public organizer.

Expected outcomes:

proxy_posture_after: recruited
relief: route_unlocked | proof_custody_up | staffing_capacity_up | public_legitimacy_up | claimant_collision_down
cost: protection_debt_up | faction_hostility_up | witness_exposure_up | handler_fatigue_up | payroll_debt_up
future_route_effect: ally_route_unlocked_with_debt | proxy_protection_ticket_armed

Branch B — Retain proxy temporarily

The player buys or shelters one task without durable loyalty.

Expected outcomes:

proxy_posture_after: retained
relief: immediate_default_down | task_completed | route_delay_secured | room_access_unlocked
cost: payroll_debt_up | contract_capture_up | future_availability_costlier | manager_debt_up
future_route_effect: short_bridge_open | follow_up_hearing_required

Branch C — Suppress proxy

The player hides, quarantines, legally freezes, edits out, intimidates, or denies the proxy.

Expected outcomes:

proxy_posture_after: suppressed
relief: immediate_exposure_down | sponsor_default_down | inspection_contradiction_down | public_panic_down
cost: public_receipt_distrust_up | fan_resentment_up | proxy_hostility_armed | archive_debt_up
future_route_effect: clean_recruit_blocked | hostile_leak_possible

Branch D — Expose proxy publicly

The player makes the proxy visible as proof, witness, signatory, public voice, or counterclaim.

Expected outcomes:

proxy_posture_after: exposed
relief: public_receipt_legitimacy_up | false_owner_pressure_down | private_capture_blocked | fan_oxygen_balance_up
cost: witness_exposure_up | inspection_heat_up | sponsor_stop_loss_pressure_up | pirate_exposure_up
future_route_effect: public_route_open_with_retaliation | protection_required

Branch E — Trade proxy to faction

The player lets sponsor, inspector, archive, editor, fan public, pirate relay, manager desk, or another claimant bind the proxy in exchange for immediate relief.

Expected outcomes:

proxy_posture_after: faction_bound
relief: immediate_pressure_down | recourse_target_protected | lawful_use_possible | room_access_unlocked
cost: route_capture_up | contract_capture_up | bureau_favor_debt_up | source_ambiguity_up | public_distrust_up
future_route_effect: faction_gate_required | proxy_route_costlier | lawful_or_public_only

Branch F — Abandon, miss, or default

The player lacks handler, protection, proof, room access, public cover, legal cover, price, route share, or attention. A faction, crisis, or blackout system claims the proxy by default.

Expected outcomes:

proxy_posture_after: hostile | missing | recovery_only
emitted_event: storyteller.event.proxy_defection_break.v1
cost: route_blocked | hostile_counterclaim_up | proof_custody_down | staffing_capacity_down | black_screen_slots_up
future_route_effect: recovery_only_route_remains | hostile_proxy_branch_armed | route_blocked_until_substitute

Core states and counters

Primary states:

• proxy_posture
• proxy_availability
• proxy_claimant
• proxy_requested_role
• proxy_protection_state
• proxy_source_pressure
• future_route_effect

Primary counters:

• proxy_protection_debt
• proxy_hostility
• proxy_exposure
• staffing_capacity
• handler_fatigue
• payroll_debt
• public_receipt_legitimacy
• public_receipt_distrust
• fan_oxygen_balance
• fan_oxygen_resentment
• witness_exposure
• inspection_heat
• bureau_favor_debt
• contract_capture
• edit_debt
• source_ambiguity
• facility_access_pressure
• route_asset_pressure
• claimant_hostility
• black_screen_slots

Every branch must record at least three deltas, with both relief and future cost visible.

Integration notes

• With 派系责任承保, every guarantor can require a proxy signer, bridge, public face, editor, or legal aide whose posture outlives the guarantee.
• With 担保追偿级联, recourse collection can seize or bind a proxy as collateral, but release must leave human scar state.
• With 追偿放行线, release can be lawful-only, public-only, split, or conditional because the proxy who carries it has a posture and claimant.
• With 派系承诺账本, faction pressure spends leverage through concrete people rather than infinite desk reactions.
• With 制作分诊台, assigning a person to a lane can change their posture, not only lane availability.
• With 证人报复链, public exposure and protection failures can turn proxy state into reprisal pressure.
• With Oxygen Claim Exchange Storyline, fan oxygen can recruit or expose an organizer instead of only moving a pool.
• With 公开悔过账本, apology and receipt wording can bind a proxy to public voice, sponsor silence, or hostile counterclaim.
• With Route Assets and Custody, a recruited, faction-bound, missing, or hostile proxy can become a route asset or route gate.

Character hooks

This storyline is not a replacement for individual character storylines. It creates cross-pressure entry points that can feed them.

• Shen Luo can be a sponsor bridge, quiet settlement handler, or manager retainer whose help creates contract capture.
• Yu Lan can be a public voice, unauthorized history carrier, or fan organizer whose exposure creates witness risk.
• Baiya can be an edit operator or checksum witness whose suppression creates source ambiguity.
• Han Yanshuang can be lawful cover or white-glove pressure whose aid creates bureau favor debt.
• Han Cutroom can turn final-cut custody into a person-state commitment.
• Inspector Rhee Archive can bind archive admissibility to a clerk, aide, or proof route.

Missability and recovery

This storyline is missable when the player treats a proxy as a free helper, resolves pressure without recording who carried it, suppresses a proxy without future hostility, exposes a proxy without protection, trades a proxy without route cost, or recruits someone cleanly with no debt.

Recovery is allowed only with scars:

• public protection after private suppression;
• legal appeal after unlawful exposure;
• sponsor buyback after hostile leak;
• fan oxygen shelter after missing organizer;
• edit checksum after source ambiguity;
• facility extraction after faction-bound escort;
• substitute proxy after route block.

Replay/session evidence shape

storyline: storyteller.storyline.proxy_posture_chain.v1
session_id: lens-proxy-posture-chain-v1-<timestamp>
seed: <deterministic-seed>
source_pressure:
  source_storyline: faction_liability_underwriting | guarantee_recourse_cascade | recourse_collection_release | faction_commitment_ledger | production_triage_desk | witness_reprisal_chain | equivalent
  source_session_id: <session that created pressure>
  source_seed: <seed>
  pressure_id: <ledger, docket, receipt, route asset, ticket, or event id>
entry_state:
  proxy_row_before:
    proxy_id: <stable id>
    proxy_name: <name or role>
    proxy_family: <family>
    current_posture: unclaimed | approached | retained | suppressed | exposed | faction_bound | hostile | missing | recovery_only
    faction_claim: <claimant>
    rival_claim: <claimant or absent>
    requested_role: <role>
offered:
  card: storyteller.card.proxy_posture_docket.v1
  rite: storyteller.rite.proxy_posture_hearing.v1
branch_runs:
  recruit:
    outcome: ally_route_unlocked_with_debt
  suppress:
    outcome: clean_recruit_blocked_and_hostile_leak_possible
  miss:
    emitted_event: storyteller.event.proxy_defection_break.v1
    outcome: hostile_proxy_branch_armed
assertions:
  - entry_is_state_driven
  - proxy_row_names_source_pressure_claimants_role_and_posture
  - recruit_retain_suppress_expose_trade_and_miss_are_non_equivalent
  - every_branch_has_relief_and_future_cost
  - proxy_posture_mutates_future_route_or_staffing_state
  - no_fixed_turn_trigger

Non-goals

• Not a generic follower system.
• Not a romance or approval meter.
• Not raw character-count satisfaction.
• Not bulk NPC filler.
• Not a fixed recruitment phase.
• Not governance content.
• Not a universal rescue mechanic.
• Not satisfied by naming a person in flavor; the proxy must inherit pressure state and mutate future play.