zenmemes

New post

zenmemes Platform Docs

Docs home

Documents

2,638 documents

Filters
  1. ui_tools_launcher_step3_development_plan.md

    Effort study: railspike-effort / v3/uitoolslauncher — ledger (standing P2 enrollment)

    docs/plans/ui_tools_launcher/ui_tools_launcher_step3_development_plan.md Plans Plans and history

  2. ui_tools_launcher_step4_implementation_summary.md

    Effort study: railspike-effort / v3/uitoolslauncher — ledger (standing P2 enrollment)

    docs/plans/ui_tools_launcher/ui_tools_launcher_step4_implementation_summary.md Plans Plans and history

  3. unified_reaction_records Railspike debug log

    docs/plans/unified_reaction_records/unified_reaction_records_debug_log.md Plans Plans and history

  4. Unified Reaction Records Step 1 Solution Assessment

    Effort study: railspike-effort / v3/unifiedreactionrecords; standing enrollment P2

    docs/plans/unified_reaction_records/unified_reaction_records_step1_solution_assessment.md Plans Plans and history

  5. Unified Reaction Records Step 2 Feature Description

    Effort study: railspike-effort / v3/unifiedreactionrecords; standing enrollment P2

    docs/plans/unified_reaction_records/unified_reaction_records_step2_feature_description.md Plans Plans and history

  6. Unified Reaction Records Step 3 Development Plan

    Effort study: railspike-effort / v3/unifiedreactionrecords; standing enrollment P2

    docs/plans/unified_reaction_records/unified_reaction_records_step3_development_plan.md Plans Plans and history

  7. Unified Reaction Records Step 4 Implementation Summary

    Effort study: railspike-effort / v3/unifiedreactionrecords; standing enrollment P2

    docs/plans/unified_reaction_records/unified_reaction_records_step4_implementation_summary.md Plans Plans and history

  8. Unified removal format — Railspike debug log

    No supported findings.

    docs/plans/unified_removal_format/unified_removal_format_debug_log.md Plans Plans and history

  9. unified_removal_format_step1_solution_assessment.md

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

    docs/plans/unified_removal_format/unified_removal_format_step1_solution_assessment.md Plans Plans and history

  10. unified_removal_format_step2_feature_description.md

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

    docs/plans/unified_removal_format/unified_removal_format_step2_feature_description.md Plans Plans and history

  11. unified_removal_format_step3_development_plan.md

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

    docs/plans/unified_removal_format/unified_removal_format_step3_development_plan.md Plans Plans and history

  12. unified_removal_format_step4_implementation_summary.md

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

    docs/plans/unified_removal_format/unified_removal_format_step4_implementation_summary.md Plans Plans and history

  13. Unintended One-Time Lobby Redirect Investigation

    After clearing a browser identity and setting up a new one, the first navbar navigation can redirect to /lobby/ even when approved-members-only mode is disable…

    docs/plans/unintended_one_time_lobby_redirect_investigation.md Plans Plans and history

  14. unsigned_attribution Railspike debug log

    docs/plans/unsigned_attribution/unsigned_attribution_debug_log.md Plans Plans and history

  15. unsigned_attribution_step1_solution_assessment.md

    Effort study: railspike-effort / v3/unsignedattribution · Host ledger · Standing enrollment P2

    docs/plans/unsigned_attribution/unsigned_attribution_step1_solution_assessment.md Plans Plans and history

  16. unsigned_attribution_step1_solution_assessment_superseded.md

    Effort study: railspike-effort / v3/unsignedattribution · Host ledger · Standing enrollment P2

    docs/plans/unsigned_attribution/unsigned_attribution_step1_solution_assessment_superseded.md Plans Plans and history

  17. unsigned_attribution_step2_feature_description.md

    Effort study: railspike-effort / v3/unsignedattribution · Host ledger · Standing enrollment P2

    docs/plans/unsigned_attribution/unsigned_attribution_step2_feature_description.md Plans Plans and history

  18. unsigned_attribution_step2_feature_description_superseded.md

    Effort study: railspike-effort / v3/unsignedattribution · Host ledger · Standing enrollment P2

    docs/plans/unsigned_attribution/unsigned_attribution_step2_feature_description_superseded.md Plans Plans and history

  19. unsigned_attribution_step3_development_plan.md

    Effort study: railspike-effort / v3/unsignedattribution · Host ledger · Standing enrollment P2

    docs/plans/unsigned_attribution/unsigned_attribution_step3_development_plan.md Plans Plans and history

  20. unsigned_attribution_step4_implementation_summary.md

    Effort study: railspike-effort / v3/unsignedattribution · Host ledger · Standing enrollment P2

    docs/plans/unsigned_attribution/unsigned_attribution_step4_implementation_summary.md Plans Plans and history

  21. Username change gate — Railspike debug log

    Debug mode: enabled (new workflow; project-root .railspikedebugon file present).

    docs/plans/username_change_gate/username_change_gate_debug_log.md Plans Plans and history

  22. Username change gate — Step 1: Solution Assessment

    We need to fix this situation in two ways:

    docs/plans/username_change_gate/username_change_gate_step1_solution_assessment.md Plans Plans and history

  23. username_change_gate_step2_feature_description.md

    Same-key username changes shipped on 2026-10-15 for everyone, with no operator control and no activity entry.

    docs/plans/username_change_gate/username_change_gate_step2_feature_description.md Plans Plans and history

  24. username_change_gate_step3_development_plan.md

    docs/plans/username_change_gate/username_change_gate_step3_development_plan.md Plans Plans and history

  25. username_change_gate_step4_implementation_summary.md

    Branch: feature/username-change-gate.

    docs/plans/username_change_gate/username_change_gate_step4_implementation_summary.md Plans Plans and history

  26. username_leak_conversation_log.txt

    docs/plans/username_leak_conversation_log.txt Plans Plans and history

  27. Step 1: Solution Assessment — Show Approver on `/user/{username}` Page

    The /user/{username} page (ProfilePageController::username(), templates/pages/username.php) lists a user's approved profiles but does not show who approved eac…

    docs/plans/username_page_approver_attribution/username_page_approver_attribution_step1_solution_assessment.md Plans Plans and history

  28. Step 2: Feature Description — Show Approver on `/user/{username}` Page

    On /user/{username}, there's no way to see who vouched for/approved this user's account(s), even though that information already exists and is shown elsewhere…

    docs/plans/username_page_approver_attribution/username_page_approver_attribution_step2_feature_description.md Plans Plans and history

  29. Step 3: Development Plan — Show Approver on `/user/{username}` Page

    docs/plans/username_page_approver_attribution/username_page_approver_attribution_step3_development_plan.md Plans Plans and history

  30. Step 4: Implementation Summary — Show Approver on `/user/{username}` Page

    docs/plans/username_page_approver_attribution/username_page_approver_attribution_step4_implementation_summary.md Plans Plans and history

  31. User approval meaning — Railspike debug log

    No supported findings.

    docs/plans/user_approval_meaning/user_approval_meaning_debug_log.md Plans Plans and history

  32. user_approval_meaning_step2_feature_description.md

    Feature 03 in the Zenmemes feedback summary asks that approving a user explain the approver is vouching for that person's conduct and integrity.

    docs/plans/user_approval_meaning/user_approval_meaning_step2_feature_description.md Plans Plans and history

  33. user_approval_meaning_step3_development_plan.md

    docs/plans/user_approval_meaning/user_approval_meaning_step3_development_plan.md Plans Plans and history

  34. user_approval_meaning_step4_implementation_summary.md

    Step 3 approved.

    docs/plans/user_approval_meaning/user_approval_meaning_step4_implementation_summary.md Plans Plans and history

  35. user_identities_tab debug log

    docs/plans/user_identities_tab/user_identities_tab_debug_log.md Plans Plans and history

  36. user_identities_tab_one_shot.md

    Cycle: v3/useridentitiestab; Mode: one-shot; Record: this file; Index: plans index

    docs/plans/user_identities_tab/user_identities_tab_one_shot.md Plans Plans and history

  37. User Specific Archives Step 1 Solution Assessment

    Users need downloadable archives of their own visible forum contributions without making bespoke archive generation cheap to spam.

    docs/plans/user_specific_archives/user_specific_archives_step1_solution_assessment.md Plans Plans and history

  38. `v3` Status Command — Step 1 Solution Assessment

    Operators need one ./v3 status command that summarizes operational health, including whether a read-model rebuild is queued, running, blocked, stale, or ready.

    docs/plans/v3_status_command/v3_status_command_step1_solution_assessment.md Plans Plans and history

  39. `v3` Status Command — Step 2 Feature Description

    Operators currently have to combine the read-model status API, task-queue status, and lock symptoms to understand whether the system needs attention.

    docs/plans/v3_status_command/v3_status_command_step2_feature_description.md Plans Plans and history

  40. `v3` Status Command — Step 3 Development Plan

    docs/plans/v3_status_command/v3_status_command_step3_development_plan.md Plans Plans and history