Skip to main content
How Can We Help?
< All Topics
Print

Conflict: Thread Delete Lifecycle Status Difference

Posted
Updated
ByJstar269

Stable ID: CONFLICT-THREAD-DELETE-STATUS-001

Record type: Conflict / contradiction. Status: MEASURED DIFFERENCE / REPLICATION WANTED.

Issue

The source-owned lifecycle probe reports a status difference at thread deletion: the observed aggregate includes a 0x20 mask difference between the compared values 0x1fff and 0x1fdf. The difference is not treated as a universal firmware rule.

Source A and source B

  • Source A: PSP-3001, firmware 6.61 with ARK, source-owned lifecycle probe.
  • Source B: Nakagawa lifecycle implementation and its public status interpretation.

Smallest supported conclusion

The two observations disagree at a bounded delete-lifecycle status bit. This is an implementation target for a controlled follow-up, not evidence about ExitDeleteThread, module self-unload, or every PSP model.

Resolving experiment

Repeat the same lifecycle with a second PSP model and a fresh public-safe scalar transcript, then isolate the status word before and after delete. Keep private captures and game inputs withheld.

Related records: EXP-THREAD-DELETE-LIFECYCLE-20260805-A · REG-CONTRADICTIONS-001 · REG-EXPERIMENTS-001

Current source anchor — Wave 4

The lifecycle implementation context was refreshed against src/rt/sched.c at main 04daf156; the measured status difference remains scoped to the reported PSP-3001 fixture.

Table of Contents