zenmemes

New post

zenmemes Platform Docs

Docs home

Documents

2,243 documents

Filters
  1. 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

  2. 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

  3. 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

  4. 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

  5. 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

  6. 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

  7. 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

  8. 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

  9. username_change_gate_step3_development_plan.md

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

  10. 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

  11. username_leak_conversation_log.txt

    docs/plans/username_leak_conversation_log.txt Plans Plans and history

  12. 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

  13. 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

  14. 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

  15. 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

  16. User approval meaning — Railspike debug log

    No supported findings.

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

  17. 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

  18. user_approval_meaning_step3_development_plan.md

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

  19. 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

  20. user_identities_tab debug log

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

  21. 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

  22. 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

  23. `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

  24. `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

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

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

  26. `v3` Status Command — Step 4 Implementation Summary

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

  27. viewer_nav_prepaint Railspike debug log

    docs/plans/viewer_nav_prepaint/viewer_nav_prepaint_debug_log.md Plans Plans and history

  28. viewer_nav_prepaint_step2_feature_description.md

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

    docs/plans/viewer_nav_prepaint/viewer_nav_prepaint_step2_feature_description.md Plans Plans and history

  29. viewer_nav_prepaint_step3_development_plan.md

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

    docs/plans/viewer_nav_prepaint/viewer_nav_prepaint_step3_development_plan.md Plans Plans and history

  30. viewer_nav_prepaint_step4_implementation_summary.md

    Debug mode: enabled (inherited from Step 3; debug log)

    docs/plans/viewer_nav_prepaint/viewer_nav_prepaint_step4_implementation_summary.md Plans Plans and history

  31. viewer_tag_lookup_memoization — Railspike debug log

    User requested enabling extended estimates for this cycle and updating Step 1 with them.

    docs/plans/viewer_tag_lookup_memoization/viewer_tag_lookup_memoization_debug_log.md Plans Plans and history

  32. viewer_tag_lookup_memoization_step1_solution_assessment.md

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

    docs/plans/viewer_tag_lookup_memoization/viewer_tag_lookup_memoization_step1_solution_assessment.md Plans Plans and history

  33. viewer_tag_lookup_memoization_step2_feature_description.md

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

    docs/plans/viewer_tag_lookup_memoization/viewer_tag_lookup_memoization_step2_feature_description.md Plans Plans and history

  34. viewer_tag_read_model — Railspike debug log

    First cycle of a B-then-A sequence, promoted from the predecessor memoization cycle's deferred Option B.

    docs/plans/viewer_tag_read_model/viewer_tag_read_model_debug_log.md Plans Plans and history

  35. viewer_tag_read_model_step1_solution_assessment.md

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

    docs/plans/viewer_tag_read_model/viewer_tag_read_model_step1_solution_assessment.md Plans Plans and history

  36. visitor_statistics_step1_solution_assessment.md

    As an operator, I'd like to see basic stats about clients/users visiting my instance.

    docs/plans/visitor_statistics/visitor_statistics_step1_solution_assessment.md Plans Plans and history

  37. Step 2: Feature Description — Visitor Statistics

    An operator has no consistent in-product view of the people and browser clients reaching an instance.

    docs/plans/visitor_statistics/visitor_statistics_step2_feature_description.md Plans Plans and history

  38. Step 3: Development Plan — Visitor Statistics

    docs/plans/visitor_statistics/visitor_statistics_step3_development_plan.md Plans Plans and history

  39. Step 4: Implementation Summary — Visitor Statistics

    docs/plans/visitor_statistics/visitor_statistics_step4_implementation_summary.md Plans Plans and history

  40. visitor_statistics_aggregate_dashboard_step1_solution_assessment.md

    Sounds good, please write Step 1 of docs/fdp/FEATUREDEVELOPMENTPROCESS.md.

    docs/plans/visitor_statistics_aggregate_dashboard/visitor_statistics_aggregate_dashboard_step1_solution_assessment.md Plans Plans and history