Contrast navigation ownership with pinned Zulip sources
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
This commit is contained in:
parent
f3ac569d8e
commit
da06464f6b
17 changed files with 611 additions and 17 deletions
|
|
@ -14,9 +14,10 @@ Problem: an address change can conceal state that only exists in the current tab
|
|||
Addressability competes with private/transient state and URL/schema stability.
|
||||
|
||||
Proposed solution: encode the public, stable resource identity and relevant view
|
||||
selection in path/query parameters. Define parameter validation, defaults and route
|
||||
resolution so direct entry and reload reconstruct that selection under current
|
||||
authorization. A URL identifies a view, not necessarily immutable bytes or guaranteed
|
||||
selection in path/query parameters, or in a fragment when a declared client runtime
|
||||
reconstructs the view. Define validation, defaults and the required resolution path
|
||||
so direct entry and reload reconstruct that selection under current authorization.
|
||||
A client-fragment contract does not imply no-script availability. A URL identifies a view, not necessarily immutable bytes or guaranteed
|
||||
future availability. Use an explicit version if a stable historical snapshot matters.
|
||||
|
||||
Do not place secrets, private draft content, focus or every transient interaction
|
||||
|
|
@ -63,3 +64,17 @@ Other policies require an explicit contract. Browser history can change the URL
|
|||
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.
|
||||
|
||||
## Independent application source contrast — 2026-09-27
|
||||
|
||||
[Zulip ZN01–ZN08](../reviews/ZulipNavigationSourceStudy.md) locates pinned hash-to-view
|
||||
reconstruction, separate history pointer/offset state, and current-list guards on
|
||||
main fetch continuations. It supplies static partial application evidence; no direct
|
||||
load or Back race was executed in Zulip. Auxiliary lookup/anchor paths and deferred
|
||||
focus remain unverified.
|
||||
|
||||
Applicability belongs to each effect: noncurrent results can still populate cached
|
||||
data without acquiring the right to change current selection. Object/list identity
|
||||
and a navigation generation are different implementation policies; neither alone
|
||||
proves freshness. Keep addressability separate from no-script enhancement and from
|
||||
within-session focus/scroll restoration. Full-contract recurrence remains unassessed.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue