Offline Participation MVP Checklist

Status: MVP implementation tracking. Checked items are delivered by the initial Outbox release; remaining items are deliberate follow-up work.

MVP scope

• Deliver these four features: a shared Outbox, supported offline voting, offline replies, and offline new-thread compose.

• Show every queued intent from the other three features in the Outbox.

• Keep flags, tagging, deletion, moderation, account actions, invitations, attachments, and privileged actions out of this MVP.

• Treat an offline item as local until the server confirms acceptance.

• Automatically attempt queued work when an open Outbox or offline-reader page regains a connection; drafts remain local and are never sent automatically.

Feature 1 — Outbox

• Provide a normal UI entry point with a pending-item count.

• List all items across supported action types, newest first by default.

• Show action type, safe target description, local creation time, last attempt time, current state, and—where available—separate signed action and server integration times.

• Keep the list compact as one expandable row per local item.

• Support the MVP states: draft, queued, waiting for connection, sending, accepted, rejected, conflicted, cancelled, and needs attention.

• Provide accessible counts and a plain-language explanation for each non-ready state.

• Allow only state-appropriate actions: open/edit draft, queue, send/retry, cancel, discard, and export.

• Retain accepted/rejected outcomes long enough to be understandable, with a clear remove-history action.

Feature 2 — Offline voting

• Define exactly which existing reaction(s) are eligible for queueing.

• Queue an intent instead of presenting an offline change as server truth.

• Sign supported offline Likes at click time for both threads and replies.

• Make repeat/undo behavior unambiguous before the original intent is sent.

• Reconcile target removal, hidden content, authorization changes, and duplicate server acceptance.

Feature 3 — Offline replies

• Store reply content as an editable local draft before it is queued.

• Preserve target-thread context and explain when it is absent, locked, hidden, or removed.

• Require an explicit online send/retry path that completes the existing prepare, signing, and finalization lifecycle.

• Map an accepted local intent to its canonical server post and link it from the Outbox.

• Keep queued content visibly distinct from published content in every UI.

Feature 4 — Offline new-thread compose

• Store subject and body as an editable local draft before it is queued.

• Restore, edit, export, discard, and queue a new-thread draft after a browser restart.

• Require an explicit online send/retry path that completes the existing prepare, signing, and finalization lifecycle.

• Map an accepted local intent to its canonical thread/post and link it from the Outbox.

• Keep queued new threads visibly distinct from published threads in every UI.

Shared trust, privacy, and data lifecycle

• Keep pending work outside the public offline-reader snapshot/cache.

• Define device/shared-browser retention, clear-data, export, and discard behavior before persisting any compose content.

• Avoid storing private keys or exposing authenticated data through the public cache.

• Use stable local intent identifiers and require server-side idempotency before retries are possible.

• Make browser storage failure, quota pressure, and unavailable storage visible before a person loses work.

Shared connection and reconciliation

• Work without Background Sync; an open page performs foreground automatic delivery when connectivity returns.

• Detect offline/online changes without claiming that reconnection means submission succeeded.

• Recheck authorization, target availability, and validation at send time.

• Record safe failure/conflict explanations and leave recoverable items in the Outbox.

• Ensure cancelling or clearing data cannot accidentally send an item.

Verification and release gates

• Unit-test state transitions, ordering, counts, and allowed controls.

• Test each action through offline creation, restart, reconnect, accepted, rejected, conflicted, and cancelled outcomes.

• Test duplicate retries and server idempotency.

• Test storage clearing, quota/storage failure, unavailable signing, and missing/locked/hidden reply targets.

• Run browser QA with and without Background Sync on supported browsers.

• Publish a concise user guide describing drafts, queued items, outcomes, privacy, and recovery.

MVP acceptance demo

• Offline: queue one supported vote, one reply, and one new thread; inspect all three in the Outbox without a network connection.

• Restart: confirm their state and editable content survive as documented.

• Reconnect with the Outbox or offline reader open: observe automatic delivery of queued items and accepted, rejected, or needs-attention results without duplicate server actions.

• Recover: cancel/export/discard an item and clear offline data only after an explicit warning about pending work.