Core Character Pool Slot Claim

Core Character Pool Slot Claim turns the old first-chapter character pool into a playable receipt surface. The pool page names starter functions, weak points, company-use lines, self-rescue lines, and folded consequences. That is useful design scaffolding, but it is unsafe if a later schedule, route, sponsor package, or management report treats a pool function as clean permission to spend a character.

This storyline opens when a future reader tries to claim a core-pool candidate for a route or schedule slot before the claim has a durable, scoped receipt. It does not decide encounter access, relationship state, or route loadout compatibility. It records the first slot claim that turns a pool row into a route-facing obligation.

Playable Question

When production claims a core-pool character for a first-chapter route, does the game certify the source role, narrow the slot use, split the claim across readers, substitute another candidate, reserve the candidate with debt, publish explicit absence, or let a false starter-pool claim harden as default?

Every answer must name:

• the source core-pool row;
• the candidate character or explicit absence;
• the claimed pool function;
• the requested route, schedule, sponsor, public, lawful, archive, or management use;
• the excluded function, reader, or route;
• the holder of the claim or explicit absence;
• the selected posture;
• one relief surface;
• one cost surface;
• the future reader or route effect.

State-Triggered Entry

Open this storyline only when a concrete reader tries to consume the old pool row:

entry_state:
  trigger_kind: state_pressure
  source_core_pool_row_present: true
  candidate_or_explicit_absence_visible: true
  claimed_slot_role_visible: true
  requested_route_or_schedule_use_visible: true
  pool_function_scope_visible_or_explicit_absence: true
  excluded_function_or_reader_visible: true
  claim_holder_or_explicit_absence_visible: true
  future_reader_consumes_pool_slot_state: true
  player_can_certify_narrow_split_substitute_reserve_publish_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_character_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Do not open from a raw roster count, chapter index, dashboard state, lens-health state, or generic recruitment prompt. The trigger is a named future reader attempting to spend a pool function as if it were already a scoped route state.

Bound Content Pack

• Core Character Pool Slot Claim defines valid pool-claim states, forbidden promotions, and branch outputs.
• Core Character Pool Slot Docket records the source pool row, candidate, claimed function, requested use, excluded reader, holder, after-state, and future route effect.
• Core Character Pool Slot Claim Review resolves certification, narrowing, split claims, substitution, reservation with debt, published absence, or default.
• False Pool Slot Default records when a starter-pool claim is treated as wider proof than the pool row supports.
• Core Character Pool Slot Claim Lens observes the packet and evaluator contract.

Storyline Spine

Beat 1 - A pool function is claimed

A first-chapter slot, route tag, sponsor surface, public proof, lawful reader, archive docket, route asset, or management metric cites one of the core-pool roles.

Examples:

• a low-protection newcomer row is claimed as clean sacrificial capacity;
• a fan leader row is claimed as whole-public consent;
• an underground doctor row is claimed as facility access proof;
• a sponsor representative row is claimed as neutral funding;
• an AI idol row is claimed as safe substitute labor;
• an execution hand row is claimed as lawful exit authority without a warrant row.

The pool row is not enough. It describes design pressure; it does not certify the current route use.

Beat 2 - The docket separates design role from route use

Create or refresh Core Character Pool Slot Docket.

core_character_pool_slot_docket:
  source_core_pool_row: storyteller.storyline.core-character-pool-v1 | <equivalent>
  candidate_or_absence: <character id or explicit_absence>
  claimed_pool_function: star_asset | sacrificial_newcomer | resistance_key | archive_remnant | inspector_pressure | algorithm_proxy | fan_leader | underground_doctor | sponsor_representative | security_executor | board_heir | ai_idol | equivalent
  pool_function_scope_or_absence: first_chapter_hook | route_seed | pressure_source | mirror_right_seed | facility_seed | sponsor_seed | public_memory_seed | explicit_absence
  requested_route_or_schedule_use: forced_main_slot | golden_slot_side_route | company_route | intimate_route | liquidation_route | resistance_route | sponsor_package | public_receipt | lawful_reader | management_metric | route_asset_claim | equivalent
  excluded_function_or_reader: self_rescue_line | company_use_line | fan_public | lawful_reader | sponsor_reader | archive_reader | route_asset_reader | rival_route | explicit_absence
  claim_holder_or_absence: producer | sponsor | public_table | lawful_desk | archive | fan_public | route_asset_holder | management | explicit_absence
  prior_pool_text_or_absence: core_character_pool_v1 | chapter_one_outline | route_matrix | explicit_absence
  claim_state_after: source_role_certified | narrowed_slot_use | split_pool_claim | substituted_candidate | reserved_with_debt | explicit_absence_published | false_pool_slot
  future_reader_or_route_effect: accepted_with_scope | addendum_required | split_required | substitute_required | debt_attached | blocked | recovery_only | costlier

The docket fails if it stores only candidate selected, starter role, route available, or character pool count without source row, claimed function, requested use, excluded reader, after-state, and future effect.

Beat 3 - The review chooses the claim posture

Resolve Core Character Pool Slot Claim Review with one of these branch families:

Branch	Relief	Cost	Future effect
certify_source_role	The pool row can support one named use.	All other functions still need receipts.	accepted_with_scope
narrow_slot_use	The route gets a usable, smaller claim.	Excluded reader remains live.	addendum_required or costlier
split_pool_claim	Company/public/lawful/sponsor readings are separated.	Future route must preserve split scope.	split_required
substitute_candidate	The claimed use moves to a safer or truer candidate.	Original pool row gains notice or resentment.	substitute_required
reserve_with_debt	Candidate remains available for a later route.	License, handler, fan, sponsor, or care debt is attached.	debt_attached
publish_explicit_absence	False availability is blocked.	Public, lawful, sponsor, or route cost rises.	blocked or recovery_only
false_pool_slot_default	No one scopes the claim before consumption.	Hidden pool function becomes false proof.	future_effect_any: costlier_or_recovery_only

Beat 4 - Future readers consume the after-state

Future readers must consume the claim state rather than the raw pool row. Examples:

• Weekly Broadcast Cycle Audit reads whether a first-week slot used the pool row within scope.
• Route Tag Momentum Collision reads whether the pool claim created a real route tag or a false one.
• Encounter Availability Routing reads whether the candidate was actually available, reserved, absent, or substituted.
• Branch Eligibility Receipts reads a blocked, narrowed, or recovery-only starter branch.
• Route Loadout Compatibility may later consume the slot claim as one asset, but only after the source scope is preserved.

Default

If a future reader consumes the pool role without a slot docket, arm False Pool Slot Default.

false_pool_slot_default:
  false_clean_pool_claim: true
  source_core_pool_row_or_absence: storyteller.storyline.core-character-pool-v1 | explicit_absence | <equivalent>
  requested_route_or_schedule_use: forced_main_slot | golden_slot_side_route | company_route | intimate_route | liquidation_route | resistance_route | sponsor_package | public_receipt | lawful_reader | management_metric | route_asset_claim | equivalent
  hidden_or_mismatched_pool_row: role_scope_absent | candidate_absent | company_line_used_as_self_rescue | self_rescue_line_sold_as_company_use | fan_public_claim_without_mandate | sponsor_claim_without_release | lawful_claim_without_proof | management_metric_without_reader | equivalent
  capturing_reader: producer | sponsor | public_table | lawful_desk | archive | fan_public | route_asset_holder | management | broadcast_reality | equivalent
  harmed_or_omitted_reader: self_rescue_line | company_use_line | fan_public | lawful_reader | sponsor_reader | archive_reader | route_asset_reader | rival_route | explicit_absence
  claim_state_after: false_role_claim | false_availability | false_consent | false_authority | blocked | recovery_only
  future_reader_or_route_effect: addendum_required | split_required | route_costlier | hostile_reader | substitute_required | blocked | recovery_only
  counter_deltas_min: 3
  durable_mutation: true

Non-Goals

• Not a replacement for Encounter Availability Routing.
• Not a route loadout compatibility check.
• Not a new character route or relationship system.
• Not a raw character-pool linter.
• Not valid if a starter role becomes clean permission for every route reader.