zenmemes Platform Docs

Docs home

Documents

2,230 documents

Filters
  1. Private message history synchronization storage findings

    The user selected a separate private database for history-sync transfers and metadata after reviewing the storage choices.

    docs/plans/private_message_history_sync/private_message_history_sync_storage_findings.md Plans Plans and history

  2. Private Message Reader Refinement: Step 1 Solution Assessment

    Please make decrypt and verify an automatic action, get rid of the “decrypt and verify” button below it, delete the status below it as well, put “signature ver…

    docs/plans/private_message_reader_refinement/private_message_reader_refinement_step1_solution_assessment.md Plans Plans and history

  3. Private Message Reader Refinement: Step 2 Feature Description

    Inbox and sent-mail cards require a manual decrypt-and-verify action and expose reader diagnostics that interrupt normal reading.

    docs/plans/private_message_reader_refinement/private_message_reader_refinement_step2_feature_description.md Plans Plans and history

  4. Private Message Reader Refinement: Step 3 Development Plan

    docs/plans/private_message_reader_refinement/private_message_reader_refinement_step3_development_plan.md Plans Plans and history

  5. Private Message Reader Refinement: Step 4 Implementation Summary

    docs/plans/private_message_reader_refinement/private_message_reader_refinement_step4_implementation_summary.md Plans Plans and history

  6. messaging_regressions.json

    docs/plans/private_message_sender_history_sync/evidence/messaging_regressions.json Plans Plans and history

  7. release_verification.json

    docs/plans/private_message_sender_history_sync/evidence/release_verification.json Plans Plans and history

  8. same_account_journey.json

    docs/plans/private_message_sender_history_sync/evidence/same_account_journey.json Plans Plans and history

  9. sender_journey.json

    docs/plans/private_message_sender_history_sync/evidence/sender_journey.json Plans Plans and history

  10. Sender-assisted private message history synchronization — Step 1

    “Looks good so far.

    docs/plans/private_message_sender_history_sync/private_message_sender_history_sync_step1_solution_assessment.md Plans Plans and history

  11. Sender-assisted private message history synchronization — Step 2

    Recipients can lose historical access while senders retain readable copies.

    docs/plans/private_message_sender_history_sync/private_message_sender_history_sync_step2_feature_description.md Plans Plans and history

  12. Sender-assisted private message history synchronization — Step 3

    Steps 1–3 approved.

    docs/plans/private_message_sender_history_sync/private_message_sender_history_sync_step3_development_plan.md Plans Plans and history

  13. Sender-assisted private message history synchronization — Step 4

    Planning commit: 95d1dfa8.

    docs/plans/private_message_sender_history_sync/private_message_sender_history_sync_step4_implementation_summary.md Plans Plans and history

  14. Private-message idle synchronization — debug log

    Verification: Compared the client batch/acknowledgment loop, account/sender work service, sync store, unread service and existing sender privacy requirements.

    docs/plans/private_message_sync_idle/private_message_sync_idle_debug_log.md Plans Plans and history

  15. private_message_sync_idle_step1_solution_assessment.md

    Effort study: railspike-effort / v3/privatemessagesyncidle — ledger, standing P2 enrollment

    docs/plans/private_message_sync_idle/private_message_sync_idle_step1_solution_assessment.md Plans Plans and history

  16. private_message_sync_idle_step2_feature_description.md

    Effort study: railspike-effort / v3/privatemessagesyncidle — ledger, standing P2 enrollment

    docs/plans/private_message_sync_idle/private_message_sync_idle_step2_feature_description.md Plans Plans and history

  17. private_message_sync_idle_step3_development_plan.md

    Effort study: railspike-effort / v3/privatemessagesyncidle — ledger, standing P2 enrollment

    docs/plans/private_message_sync_idle/private_message_sync_idle_step3_development_plan.md Plans Plans and history

  18. private_message_sync_idle_step4_implementation_summary.md

    Effort study: railspike-effort / v3/privatemessagesyncidle — ledger

    docs/plans/private_message_sync_idle/private_message_sync_idle_step4_implementation_summary.md Plans Plans and history

  19. private_message_sync_idle_reload_diagnostic.txt

    docs/plans/private_message_sync_idle_reload_diagnostic.txt Plans Plans and history

  20. Compact unavailable private messages rollout and rollback

    Unavailable messages use compact details.

    docs/plans/private_message_unavailable/private_message_unavailable_rollout.md Plans Plans and history

  21. Compact unavailable private messages Step 1 solution assessment

    Amazing work, please merge into main and then continue to the next one.

    docs/plans/private_message_unavailable/private_message_unavailable_step1_solution_assessment.md Plans Plans and history

  22. Compact unavailable private messages Step 2 feature description

    Repeated decryption errors and retry buttons overwhelm conversation history.

    docs/plans/private_message_unavailable/private_message_unavailable_step2_feature_description.md Plans Plans and history

  23. Compact unavailable private messages Step 3 development plan

    docs/plans/private_message_unavailable/private_message_unavailable_step3_development_plan.md Plans Plans and history

  24. Compact unavailable private messages Step 4 implementation summary

    docs/plans/private_message_unavailable/private_message_unavailable_step4_implementation_summary.md Plans Plans and history

  25. Private message unread state rollout and rollback

    Related: implementation and verification · approved plan.

    docs/plans/private_message_unread/private_message_unread_rollout.md Plans Plans and history

  26. Private message unread state Step 1 solution assessment

    Looks good.

    docs/plans/private_message_unread/private_message_unread_step1_solution_assessment.md Plans Plans and history

  27. Private message unread state Step 2 feature description

    Messages does not identify conversations needing attention.

    docs/plans/private_message_unread/private_message_unread_step2_feature_description.md Plans Plans and history

  28. Private message unread state Step 3 development plan

    docs/plans/private_message_unread/private_message_unread_step3_development_plan.md Plans Plans and history

  29. Private message unread state Step 4 implementation summary

    docs/plans/private_message_unread/private_message_unread_step4_implementation_summary.md Plans Plans and history

  30. Private Messaging Step 1 Solution Assessment

    As a user, I want to be able to private-message another user.

    docs/plans/private_messaging/private_messaging_step1_solution_assessment.md Plans Plans and history

  31. Private Messaging Step 2 Feature Description

    Members can identify one another and hold OpenPGP keys but cannot communicate privately without taking the conversation off-site.

    docs/plans/private_messaging/private_messaging_step2_feature_description.md Plans Plans and history

  32. Private Messaging Step 3 Development Plan

    docs/plans/private_messaging/private_messaging_step3_development_plan.md Plans Plans and history

  33. Private Messaging Step 4 Implementation Summary

    docs/plans/private_messaging/private_messaging_step4_implementation_summary.md Plans Plans and history

  34. Private Messaging Mermaid Diagrams: Checklist

    Target doc: docs/architecture/privatemessaging.md.

    docs/plans/private_messaging_diagrams_checklist.md Plans Plans and history

  35. private_messaging_feature_flag_step1_solution_assessment.md

    As an admin/operator, I want to be able to gate whether the PM/DM (messages) feature is enabled on the server with a feature flag.

    docs/plans/private_messaging_feature_flag/private_messaging_feature_flag_step1_solution_assessment.md Plans Plans and history

  36. private_messaging_feature_flag_step2_feature_description.md

    Operators cannot currently disable private messaging server-wide.

    docs/plans/private_messaging_feature_flag/private_messaging_feature_flag_step2_feature_description.md Plans Plans and history

  37. private_messaging_feature_flag_step3_development_plan.md

    docs/plans/private_messaging_feature_flag/private_messaging_feature_flag_step3_development_plan.md Plans Plans and history

  38. private_messaging_feature_flag_step4_implementation_summary.md

    Implementation on feature/private-messaging-feature-flag; planning commit 5e926950.

    docs/plans/private_messaging_feature_flag/private_messaging_feature_flag_step4_implementation_summary.md Plans Plans and history

  39. Private Messaging Live Navigation — Railspike Debug Log

    No supported findings.

    docs/plans/private_messaging_live_navigation/private_messaging_live_navigation_debug_log.md Plans Plans and history

  40. private_messaging_live_navigation_step1_solution_assessment.md

    Great job!

    docs/plans/private_messaging_live_navigation/private_messaging_live_navigation_step1_solution_assessment.md Plans Plans and history