coulomb/frontend-patterns
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Test competing navigation ownership and review research thread

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
This commit is contained in:
tegwick 2026-09-27 00:45:54 +02:00
parent e484cae45f
commit e8ccb73a12
22 changed files with 4981 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

16
research/candidates/URLAddressableState.md
View file

@ -47,3 +47,19 @@ a fragment served as a full document in Chromium and Firefox; correct selection
keeps representations distinct, without promising cache retention or freshness.
See [NH01–NH06](../reviews/NavigationHistoryExperiment.md). One authored application
with a real package, not independent deployed recurrence. Hypothesis retained.
## Competing completion ownership — 2026-09-27
[NO01–NO06](../reviews/NavigationOwnershipExperiment.md) show a delayed history response
replacing content/title while a newer URL remains selected in the unguarded fixture.
Treat navigation initiation, including Back/Forward, as intent with an explicit
completion owner. Before applying an asynchronous result, check that it still owns
the selected route; include URL, content, title and feedback in that decision.
A response to obsolete intent is not made current by arriving last or succeeding.
The experiment's latest-intent policy keeps the last committed view and newest error
when a newer request fails; it does not revive older pending navigation implicitly.
Other policies require an explicit contract. Browser history can change the URL before
loading completes: pending-state disclosure/recovery is still unresolved here.
The authored guard supports this obligation only in the tested schedules, not a
portable router or proof of independent application recurrence.