zenmemes Platform Docs

Documents

• Clear all

2,633 documents

Search unavailable. Retry or refresh the library.

1. Scripture Response Reliability Revision — Feature Description

   The failed candidate verifies published quotations but rejects ordinary quoted language and misreads practical or pastoral concerns.

   docs/plans/scripture_response_reliability_revision/scripture_response_reliability_revision_step2_feature_description.md Plans Plans and history

2. Scripture Response Reliability Revision — Development Plan

   Deliver existing scripture request → complete reply → optional Expand → explicit recovery, using a scripture-only writer and verified quotations.

   docs/plans/scripture_response_reliability_revision/scripture_response_reliability_revision_step3_development_plan.md Plans Plans and history

3. Scripture Response Reliability Revision — Step 3 Evaluation Protocol

   This protocol is part of the Step 3 development plan and its approval scope.

   docs/plans/scripture_response_reliability_revision/scripture_response_reliability_revision_step3_evaluation_protocol.md Plans Plans and history

4. Scripture Reliability Revision — Implementation Summary

   Approval: user authorized the original Step 3 plan and linked protocol.

   docs/plans/scripture_response_reliability_revision/scripture_response_reliability_revision_step4_implementation_summary.md Plans Plans and history

5. Collection-selection fixes

   Authorization: User requested QDB welcome selection first, then offline candidate selection, in separate commits, with this ongoing checklist.

   docs/plans/selection_fixes_checklist.md Plans Plans and history

6. Server cooperative content deletion debug log

   docs/plans/server_cooperative_content_deletion/server_cooperative_content_deletion_debug_log.md Plans Plans and history

7. Server Cooperative Content Deletion Step 1 Solution Assessment

   Explore server-cooperative content deletion.

   docs/plans/server_cooperative_content_deletion/server_cooperative_content_deletion_step1_solution_assessment.md Plans Plans and history

8. Server Cooperative Content Deletion Step 2 Feature Description

   Authors cannot retract their own posts; only operators can remove records, and that leaves content in Git history with no author authority.

   docs/plans/server_cooperative_content_deletion/server_cooperative_content_deletion_step2_feature_description.md Plans Plans and history

9. Server Cooperative Content Deletion Step 3 Development Plan

   docs/plans/server_cooperative_content_deletion/server_cooperative_content_deletion_step3_development_plan.md Plans Plans and history

10. Server Cooperative Content Deletion Step 4 Implementation Summary

    docs/plans/server_cooperative_content_deletion/server_cooperative_content_deletion_step4_implementation_summary.md Plans Plans and history

11. Session Reauthentication Reference

    The original report concerned requests arriving after a PHP session record expired or was cleaned up, before browser JavaScript could restore authentication.

    docs/plans/session_reauthentication_reference.md Plans Plans and history

12. Decision: signing in must not quietly sign the browser out

    Status: decided 2026-10-30 — option A with a 30-second grace period; implemented on fix/session-rotation-race (see Implementation).

    docs/plans/session_rotation_race_decision.md Plans Plans and history

13. Shared Navigation Icons (Word 97 + Chicago)

    Branch: feature/shared-nav-icons.

    docs/plans/shared_nav_icons_checklist.md Plans Plans and history

14. signed_post_speed debug log

    docs/plans/signed_post_speed/signed_post_speed_debug_log.md Plans Plans and history

15. signed_post_speed_step1_solution_assessment.md

    Debug mode: enabled (debug log)

    docs/plans/signed_post_speed/signed_post_speed_step1_solution_assessment.md Plans Plans and history

16. signed_post_speed_step2_feature_description.md

    Debug mode: enabled (debug log)

    docs/plans/signed_post_speed/signed_post_speed_step2_feature_description.md Plans Plans and history

17. signed_post_speed_step3_development_plan.md

    Debug mode: enabled (debug log)

    docs/plans/signed_post_speed/signed_post_speed_step3_development_plan.md Plans Plans and history

18. signed_post_speed_step4_implementation_summary.md

    Debug mode: enabled (debug log)

    docs/plans/signed_post_speed/signed_post_speed_step4_implementation_summary.md Plans Plans and history

19. Signed thread label records debug log

    Supersedes the prior Step 2 report’s online thread-only scope assessment.

    docs/plans/signed_thread_label_records/signed_thread_label_records_debug_log.md Plans Plans and history

20. Signed Thread Label Records Step 1 Solution Assessment

    I would like this, I kinda thought it was already the case.

    docs/plans/signed_thread_label_records/signed_thread_label_records_step1_solution_assessment.md Plans Plans and history

21. Signed Thread Label Records Step 2 Feature Description

    Thread labels and post reactions (including likes and flags) name an author without preserving that author's signature over the saved record.

    docs/plans/signed_thread_label_records/signed_thread_label_records_step2_feature_description.md Plans Plans and history

22. signed_thread_label_records_step3_development_plan.md

    Waiting for "Approved Step 3" before branching, organizing/committing plans, or implementation.

    docs/plans/signed_thread_label_records/signed_thread_label_records_step3_development_plan.md Plans Plans and history

23. Signed labels and reactions implementation

    Branch: feature/signed-thread-label-records.

    docs/plans/signed_thread_label_records/signed_thread_label_records_step4_implementation_summary.md Plans Plans and history

24. Single-request posting — Railspike debug log

    Source: step1solutionassessment.md, compare options and preserve intent.

    docs/plans/single_request_posting/single_request_posting_debug_log.md Plans Plans and history

25. single_request_posting_step1_solution_assessment.md

    Effort study: railspike-effort / v3/singlerequestposting; ledger, standing P2 enrollment

    docs/plans/single_request_posting/single_request_posting_step1_solution_assessment.md Plans Plans and history

26. single_request_posting_step2_feature_description.md

    Effort study: railspike-effort / v3/singlerequestposting; ledger, standing P2 enrollment

    docs/plans/single_request_posting/single_request_posting_step2_feature_description.md Plans Plans and history

27. single_request_posting_step3_development_plan.md

    Effort study: railspike-effort / v3/singlerequestposting; ledger, standing P2 enrollment

    docs/plans/single_request_posting/single_request_posting_step3_development_plan.md Plans Plans and history

28. single_request_posting_step4_implementation_summary.md

    Effort study: railspike-effort / v3/singlerequestposting; ledger

    docs/plans/single_request_posting/single_request_posting_step4_implementation_summary.md Plans Plans and history

29. site_favicons_step1_solution_assessment.md

    Our default favicon is a letter Z, which is kind of appropriate for zenmemes, but very inappropriate for other sites.

    docs/plans/site_favicons/site_favicons_step1_solution_assessment.md Plans Plans and history

30. site_favicons_step2_feature_description.md

    chouse and qdb show the zenmemes "Z" favicon in browser tabs, bookmarks and the installed-app icon.

    docs/plans/site_favicons/site_favicons_step2_feature_description.md Plans Plans and history

31. site_favicons_step3_development_plan.md

    Waiting for "Approved Step 3" before starting Step 4.

    docs/plans/site_favicons/site_favicons_step3_development_plan.md Plans Plans and history

32. site_favicons_step4_implementation_summary.md

    docs/plans/site_favicons/site_favicons_step4_implementation_summary.md Plans Plans and history

33. Site Feature Flags Slices V1

    This document outlines an atomic implementation plan for making site feature flags visible, auditable, and eventually mutable through the site while preserving…

    docs/plans/site_feature_flags_slices_v1.md Plans Plans and history

34. site_operations_page Railspike debug log

    docs/plans/site_operations_page/site_operations_page_debug_log.md Plans Plans and history

35. site_operations_page_step2_feature_description.md

    Effort study: railspike-effort / v3/siteoperationspage; ledger.

    docs/plans/site_operations_page/site_operations_page_step2_feature_description.md Plans Plans and history

36. site_operations_page_step3_development_plan.md

    Effort study: railspike-effort / v3/siteoperationspage; ledger.

    docs/plans/site_operations_page/site_operations_page_step3_development_plan.md Plans Plans and history

37. site_operations_page_step4_implementation_summary.md

    Effort study: railspike-effort / v3/siteoperationspage; ledger.

    docs/plans/site_operations_page/site_operations_page_step4_implementation_summary.md Plans Plans and history

38. site_purpose debug log

    No supported findings.

    docs/plans/site_purpose/site_purpose_debug_log.md Plans Plans and history

39. site_purpose_step1_solution_assessment.md

    Effort study: railspike-effort / v3/sitepurpose; host ledger.

    docs/plans/site_purpose/site_purpose_step1_solution_assessment.md Plans Plans and history

40. site_purpose_step2_feature_description.md

    Effort study: railspike-effort / v3/sitepurpose; host ledger.

    docs/plans/site_purpose/site_purpose_step2_feature_description.md Plans Plans and history