Core Character Pool Slot Claim

This mechanic prevents a first-chapter core-pool role from becoming universal route permission. A pool row can identify a character’s design function, but it cannot by itself prove schedule access, consent, sponsor release, lawful standing, public mandate, management closure, route-asset ownership, or encounter availability.

Contract

core_character_pool_slot_claim:
  trigger_kind: state_pressure
  source_core_pool_row_required: true
  candidate_or_explicit_absence_required: true
  claimed_slot_role_required: true
  requested_route_or_schedule_use_required: true
  pool_function_scope_or_explicit_absence_required: true
  excluded_function_or_reader_required: true
  claim_holder_or_explicit_absence_required: true
  future_reader_consumes_pool_slot_state: true
  no_fixed_turn_trigger: true
  no_raw_character_count_trigger: true

The mechanic is active when all of these are true:

• a route, schedule, sponsor, public, lawful, archive, or management reader cites a core-pool role;
• the candidate row is absent, narrower than the requested use, or contested by an excluded reader;
• the requested use would change route access, route tag, slot state, claimant pressure, or future cost;
• a player-facing branch can certify, narrow, split, substitute, reserve, publish absence, or default.

Required Docket Shape

core_character_pool_slot_docket_required:
  source_core_pool_row: required
  candidate_or_absence: required
  claimed_pool_function: required
  pool_function_scope_or_absence: required
  requested_route_or_schedule_use: required
  excluded_function_or_reader: required
  claim_holder_or_absence: required
  claim_state_after: required
  future_reader_or_route_effect: required

The docket keeps the static pool role, the candidate, and the attempted future consumption separate. A row cannot close cleanly with only a starter roster label.

Claim States

State	Meaning	Valid future use
source_role_certified	The source role supports one named use.	Accepted only for that reader and use.
narrowed_slot_use	The character can fill a smaller route slot.	Future readers need addendum or cost.
split_pool_claim	Company, self-rescue, public, lawful, sponsor, or route readings diverge.	Each reader consumes only its segment.
substituted_candidate	A safer or truer candidate carries the claim.	Original row gains notice, scar, or exclusion.
reserved_with_debt	Candidate remains available but not free.	Later route must pay attached debt.
explicit_absence_published	The claimed candidate or function is absent.	False availability is blocked.
false_pool_slot	The pool row was consumed beyond scope.	Default scars the reader and future route.

Forbidden Promotions

These promotions are invalid unless the slot docket explicitly permits them:

• pool role to clean schedule eligibility;
• company-use line to self-rescue proof;
• self-rescue line to sponsor-safe package;
• fan leader to whole-public mandate;
• sponsor representative to neutral funding proof;
• security executor to lawful exit authority;
• AI idol to clean substitute labor;
• starter candidate to global encounter availability.

Branch Requirements

Every Core Character Pool Slot Claim Review branch must provide:

• one relief surface;
• one cost surface;
• a named future reader or route effect;
• claim_state_after;
• a note about which pool function remains forbidden or requires a new receipt;
• at least three counter or route-flag moves on default or scar branches.

Valid branch families are:

• certify_source_role;
• narrow_slot_use;
• split_pool_claim;
• substitute_candidate;
• reserve_with_debt;
• publish_explicit_absence;
• false_pool_slot_default.

Default Rule

If a future reader consumes the pool role while source row, candidate, scope, excluded reader, or claim holder is absent or mismatched, fire False Pool Slot Default.

The default records who captured the false value, which pool role was overread, which reader was omitted, and how later route, schedule, encounter, or management play becomes costlier, blocked, hostile, split, or recovery-only.