Back in the same workspace, but which visit owns the result?

An A→B→A navigation can make an old request look current again. The application controls completion time and compares a generation check with a version missing that check. If the first request for A finishes only after switching back to A, determining which visit owns the result becomes ambiguous. The workspace name matches, but the first request has not turned into a new request.

The application needs a distinguishable marker to identify visits. Orca submitted a change that gives one object responsibility for pending requests and temporarily stored results. The implementation attaches a "valid-at-the-time" marker to a request. When switching or resetting, the old marker is retired. Returning to the initial workspace does not reactivate the first visit's marker.

The code refers to these distinct periods as "generations." Recognizing the workspace name alone is insufficient, as changes may have occurred during switching. The experiment used a specific scenario (A→B→A) to build a controlled timing test. The original module detects a generation check, which rejects stale results. Removing this check allows the old result to be stored and read later.

The modified version helps explain the mechanism and is not a historical Orca release. Omitting the signal of identity change does not establish a defect in the real login flow. Another observation reveals that temporarily stored contents (cache) are separate steps. Reading only the "committed" verdict misses the second part of the protection.

The application must report identity changes, such as reauthentication or moving execution to another computer. These events can make earlier results obsolete. The application needs signals from the caller or environment to determine when a result is obsolete. Developers should consider how many updates a request produces and how request markers should constrain updates.

Returning to the same workspace does not reverse time; the application still needs to know which visit owns the result.