Inspect frontend recovery implementations and refine operation lifecycles
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
This commit is contained in:
parent
96d11431dc
commit
d7b2ea49ce
22 changed files with 1048 additions and 2 deletions
|
|
@ -31,3 +31,12 @@ Proposed connection: supports recovery from [Version-Checked Mutation](VersionCh
|
|||
T01–T05 refer to [TransactionalEvidenceExpansion](../reviews/TransactionalEvidenceExpansion.md).
|
||||
Connections are research proposals, not admitted graph edges.
|
||||
Reasoning exercise: [VC-01](../walkthroughs/VC01-TransactionalAdministration.md).
|
||||
|
||||
## Implementation evidence update — 2026-09-25
|
||||
|
||||
[Frontend recovery review](../reviews/FrontendRecoveryImplementations.md) R01/R03
|
||||
locates Zulip and Element draft storage/restoration at exact commits. These are two
|
||||
partial known uses of unsent-intent separation, not confirmation of the entire
|
||||
base/draft/current merge contract. Full-pattern recurrence remains unknown.
|
||||
A composer may hand submitted content to a separate pending record. Preserve the
|
||||
recoverable intent across that handoff; do not require the input box to stay filled.
|
||||
|
|
|
|||
|
|
@ -35,3 +35,14 @@ be valid there while remote propagation remains unacknowledged.
|
|||
T01–T05 refer to [TransactionalEvidenceExpansion](../reviews/TransactionalEvidenceExpansion.md).
|
||||
Connections are research proposals, not admitted graph edges.
|
||||
Reasoning exercise: [VC-01](../walkthroughs/VC01-TransactionalAdministration.md).
|
||||
|
||||
## Implementation evidence update — 2026-09-25
|
||||
|
||||
[Frontend recovery review](../reviews/FrontendRecoveryImplementations.md) R02/R04–R06
|
||||
locates failed-send recovery and echo reconciliation in two frontend families.
|
||||
These are partial uses, not verified implementations of all four proposed states.
|
||||
NOT_SENT or failed_request may reflect missing confirmation, not proven rejection.
|
||||
Correlation IDs, server deduplication and authoritative acceptance require separate
|
||||
evidence. A later matching authoritative event can resolve uncertainty; stale errors
|
||||
must not overwrite stronger evidence. Keep hypothesis maturity; assess whether this
|
||||
is best retained as a shared review model rather than a standalone pattern.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue