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

Refine recovery guidance and explore navigation and rendering

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
This commit is contained in:
tegwick 2026-09-26 21:22:53 +02:00
parent 21030784b1
commit 642163a1ed
21 changed files with 407 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

11
research/candidates/PendingSynchronization.md
View file

@ -32,3 +32,14 @@ offline operation; untracked best-effort upload, which lacks restart recovery.
Proposed connections: [Local Commit Boundary](LocalCommitBoundary.md) provides a
persistent origin; detected divergence may create context for [Conflict Copy](ConflictCopy.md).
Neither relation implies every sync needs a conflict copy. See the VC-02 walkthrough.
## Supersession contract — 2026-09-26
If reconciliation replaces pending operation P with revision c and operation Q,
commit c, Q and P's superseded/non-retryable status in one recoverable transaction.
After a restart, the queue must not retry P as active work. An already transmitted
P cannot be recalled by this local transaction: the receiver still needs appropriate
version/ancestry preconditions or reconciliation. A late receipt for P updates P's
history, never clears Q or overwrites c. Trace both crash boundaries and in-flight
races before asserting this contract. This is proposed guidance, not an executed
storage test; see [shared guidance revision](../reviews/SharedGuidanceRevision.md).