Support-Light Personhood Custody / 应援灯人格羁押线

Support-Light Personhood Custody is the system-facing storyline for the moment a D-17 support-light, voiceprint, fan receipt, archive stub, security tag, editor checksum, or K-404 static receipt can classify L-07 before Li Deng is treated as either a clean person or clean property.

The existing 璃灯应援灯人格线 asks whether 璃灯 can become a protected witness, fan route proof, static bridge, archive-only object, hostile echo, missed personhood claim, or recovery-only scar. This top-level storyline asks the broader systems question: did the classification row itself stay visible enough for future routes, witness payroll, K-404 bridge use, fan proof, archive appeal, security clearance, editor continuity, and route-asset custody to inherit it?

Playable Question

When a concrete L-07 row is contested, does the producer preserve Li Deng as a hologram witness, seal the row as lawful archive residue, publish fan personhood proof, route the proof through K-404, mute it as edit-safe noise, surrender it to a security property frame, defer it into recovery-only custody, or miss the hearing and let clearance define her first?

The answer must name:

• concrete personhood row;
• holder or explicit absence;
• claimant families;
• proof bridge or explicit absence;
• handler or explicit absence;
• selected posture;
• relief, cost, and future-route deltas;
• future route, witness, fan, archive, security, K-404, edit, or recovery effect.

State-Triggered Entry

Open this storyline only from state pressure:

entry_state_required:
  trigger_kind: state_pressure
  subject: char.li_deng
  concrete_l07_row_present: true
  row_kind_visible: voiceprint | support_light_shell | fan_receipt | static_receipt | archive_stub | security_tag | editor_checksum | equivalent
  holder_or_explicit_absence_visible: true
  claimant_families_min: 2
  future_route_depends_on_row: true
  proof_bridge_or_explicit_absence_visible: true
  handler_or_explicit_absence_visible: true
  player_can_preserve_seal_publish_bridge_mute_frame_defer_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Do not open this storyline from a fixed D-17 visit, chapter beat, raw support-light count, dashboard state, lens health, or atmospheric lost-property clue with no future reader.

Bound Content Pack

• 应援灯人格羁押机制 defines the classification state machine and future acceptance contract.
• 璃灯应援灯人格线 binds the named character route.
• K-404 Storyline can become the static bridge, but cannot classify the row cleanly without exposure cost.
• Huo Qian Storyline and fan proof can carry public personhood, but cannot erase witness risk.
• 璃灯应援灯人格案卷 records the row, holders, claimant families, proof bridge, posture, and future use.
• 应援灯人格听证 resolves preserve, seal, publish, bridge, mute, frame, defer, and default branches.
• 无主应援灯清场 fires or arms when another desk clears the row without posture, proof, handler, or future effect.
• Support-Light Personhood Custody Lens observes this system wrapper independently from the Li Deng character lens.

Storyline Spine

Beat 1 - L-07 becomes a row, not atmosphere

A voiceprint, support-light shell, fan receipt, static receipt, archive stub, security tag, editor checksum, or equivalent row becomes capable of changing future route access.

The row must identify what is being classified, who holds it, and why a later route cares. A vague D-17 mystery, ambient signal, or emotional clue is not enough.

Beat 2 - Claimants define the same row differently

At least two claimant families must be live or explicitly absent:

• fan public or Huo Qian treats the row as personhood proof;
• K-404 treats it as static receipt bridge;
• archive or inspector treats it as lawful residue;
• security treats it as property or clearance evidence;
• editor or cutroom treats it as usable noise;
• sponsor or management treats it as a suppressible liability;
• pirate relay treats it as public hostile echo.

The storyline records what each claimant gains, what each claimant risks, and what future route is changed if that claimant wins.

Beat 3 - The docket prices classification

Create or refresh Li Deng Support-Light Personhood Docket.

The docket must not record only Li Deng found or object recovered. It must expose row kind, holder, credibility anchor, claimant families, selected posture, proof bridge, handler, cost, and future route effect.

Beat 4 - The hearing selects a posture

Run Support-Light Personhood Hearing.

Valid posture families:

• preserve as hologram witness;
• seal as silent archive asset;
• publish fan personhood receipt;
• route through K-404 static receipt;
• mute as edit-safe noise;
• surrender to security property frame;
• defer into recovery-only;
• default clearance.

Beat 5 - Future play inherits the classification

Every branch leaves a durable future reader. Protected witness payroll, K-404 static bridge, fan public route, archive appeal, security clearance, editor continuity, sponsor stop-loss, or route-asset custody must know whether L-07 was preserved, sealed, publicized, bridged, muted, framed, deferred, deleted, hostile, or recovery-only.

If the row is hidden or consumed without posture, Unclaimed Light Clearance records the clearance outcome and blocks clean classification later.

Branch Map

Branch	Immediate relief	Cost/scar	Future state
Preserve hologram witness	Li Deng becomes assignable witness or protected route asset	inspection heat, witness exposure, handler burden, or fan expectation rises	protected witness payroll or future witness route is required
Seal as silent archive asset	row is not destroyed and lawful appeal remains possible	public route narrows, archive debt or fan resentment rises	lawful-only or public-costlier path
Publish fan personhood receipt	private erasure is blocked	sponsor pressure, inspection heat, witness risk, or fan oxygen liability rises	fan/public route opens with audit
Route through K-404 static receipt	machine-legible bridge controls source ambiguity	K-404 exposure, archive doubt, or static contamination rises	K-404 bridge required for clean use
Mute as edit-safe noise	current slot or continuity stabilizes	voice integrity falls, edit debt or future raw-proof cost rises	personhood recovery becomes costlier
Surrender to security property frame	immediate security or sponsor noise drops	personhood claim, fan trust, and custody integrity fall	personhood route becomes recovery-only
Defer into recovery-only	unsafe clean use is blocked and deletion is prevented	schedule pressure, route pressure, and recovery cost rise	later recovery hearing required
Default clearance	no clean relief	lost-property, archive-only, muted, hostile, or recovery-only state hardens	blocked, hostile, costlier, lawful-only, public-only, or recovery-only

No branch may make L-07 simultaneously clean personhood proof, clean archive property, clean fan receipt, clean edit asset, and clean security evidence.

Missability And Recovery

This storyline is missed when implementation:

• stores only a Li Deng clue without a row id or row kind;
• allows one authority to classify L-07 for every future use;
• hides holder, proof bridge, handler, claimant families, selected posture, cost, or future route effect;
• treats K-404, Huo Qian, security, editor, sponsor, or archive as a clean resolver;
• fires from fixed turn, fixed day/week, raw count, dashboard state, or lens health;
• lets Unclaimed Light Clearance delete Li Deng without a recoverable scar or future route mutation.

Recovery requires a new docket row naming the missing input and the scarred future reader. A recovered Li Deng classification can reopen witness, fan, archive, K-404, or recovery routes, but never as clean universal personhood.