tegwick
53bb65e7a6
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0e241-8285-7a63-8c0c-51c9cb824dc3
1.8 KiB
1.8 KiB
Offline recovery: mechanism mappings
0.1 research preview. Previously reviewed documentation locates partial mechanisms, not verified whole-pattern guarantees. Review dates/access limits are retained in LocalFirstEvidenceExpansion. Offline sequence.
| Decision | Located mechanism | Boundary |
|---|---|---|
| CAND-0002 — local acceptance | Joplin local SQLite storage, E04; local-first motivation E01 | Does not specify our revision-plus-pending atomic commit, acknowledgement/flush or crash contract |
| CAND-0003 — pending propagation | Joplin distinct sync process and per-item progress metadata E05/E06 | Does not verify deduplication, bounded completion or atomic supersession proposed by this candidate |
| CAND-0001 — preserve competing content | Joplin detected-note conflicts E07; Obsidian optional conflict-file mode E08 | Configuration and file-type scope differ; not a universal detection or no-loss guarantee |
| CAND-0004 — decide intended content | Documented manual comparison/recovery E07/E08 | Provenance, accessible interaction and recoverable resolution transaction remain proposed |
| Separate device-loss recovery | Obsidian backup distinction E11/E12 | No restore drill or recovery-point guarantee was executed in this research |
These are separate products and modes, not a prescription to combine them. An automatic merge may be preferable when domain semantics justify it. The authority/projection comparison explains why local availability, replica convergence and accepted domain meaning must remain distinct. Choose and fault-test a specific storage/receiver pair before promising the sequence's durability and retry behavior.