Case file TP-0204

Rejected connection returned to first position in a later session

During a comparison with a second profile, a rejected transfer connection returned to the top after the timetable refreshed. The preferred result persisted only after another override. No second device was involved.

Observed sequence

Available evidence

Session log and screen sequence with a repeat test.

Technical alternative

Refreshed timetable data.

Archive assessment

A comparison test reproduced the effect through refreshed timetable data. The Protocol interpretation was rejected.

Interpretive limit: Classification describes correspondence with the archive model. It does not establish intent, coordination or a shared technical cause.