zenmemes

New post

zenmemes Platform Docs

Docs home

Documents

1,790 documents

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

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

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

  4. User approval meaning — Railspike debug log

    No supported findings.

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

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

  6. user_approval_meaning_step3_development_plan.md

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

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

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

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

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

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

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

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

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

  13. viewer_nav_prepaint Railspike debug log

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

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

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

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

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

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

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

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

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

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

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

  24. Step 3: Development Plan — Visitor Statistics

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

  25. Step 4: Implementation Summary — Visitor Statistics

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

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

  27. Step 2: Feature Description — Aggregate Visitor Statistics Dashboard

    The current visitor-statistics page reports only daily aggregates in a three-row table, making its “24 hours” label inaccurate and leaving operators unable to…

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

  28. Step 3: Development Plan — Aggregate Visitor Statistics Dashboard

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

  29. Step 4: Implementation Summary — Aggregate Visitor Statistics Dashboard

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

  30. Vote Identity Readiness — Step 1: Solution Assessment

    Whenever I vote, it says "preparing identity..." first.

    docs/plans/vote_identity_readiness/vote_identity_readiness_step1_solution_assessment.md Plans Plans and history

  31. Vote Identity Readiness — Step 2: Feature Description

    A browser that already holds a usable local identity can still perform publication, verification, or identity-hint work only after a vote is clicked.

    docs/plans/vote_identity_readiness/vote_identity_readiness_step2_feature_description.md Plans Plans and history

  32. Vote Identity Readiness — Step 3: Development Plan

    docs/plans/vote_identity_readiness/vote_identity_readiness_step3_development_plan.md Plans Plans and history

  33. Vote Identity Readiness — Step 4: Implementation Summary

    docs/plans/vote_identity_readiness/vote_identity_readiness_step4_implementation_summary.md Plans Plans and history

  34. Debug log — word97_chicago_disabled_and_dark

    docs/plans/word97_disabled_and_dark_theme/word97_chicago_disabled_and_dark_debug_log.md Plans Plans and history

  35. Step 1: Solution Assessment — Word 97 disabled buttons and dark Chicago/Word 97

    From todo.txt:

    docs/plans/word97_disabled_and_dark_theme/word97_chicago_disabled_and_dark_step1_solution_assessment.md Plans Plans and history

  36. Step 2: Feature Description — Word 97 disabled buttons and dark Win9x theme

    In the Word 97 theme, disabled buttons do not look disabled.

    docs/plans/word97_disabled_and_dark_theme/word97_chicago_disabled_and_dark_step2_feature_description.md Plans Plans and history

  37. Step 3: Development Plan — Word 97 disabled buttons and dark Win9x theme

    Working name for the new theme: Win Dark (windark, mode dark); rename at review if preferred.

    docs/plans/word97_disabled_and_dark_theme/word97_chicago_disabled_and_dark_step3_development_plan.md Plans Plans and history

  38. Step 4: Implementation Summary — Word 97 disabled buttons and dark Win9x theme

    docs/plans/word97_disabled_and_dark_theme/word97_chicago_disabled_and_dark_step4_implementation_summary.md Plans Plans and history

  39. Word 97 Theme Improvements (round 2)

    The theme-word97 branch has the base theme plus three improvement commits

    docs/plans/word97_theme_improvements_plan_v1.md Plans Plans and history

  40. youtube_embed_layout_step1_solution_assessment.md

    YouTube embeds:

    docs/plans/youtube_embed_layout/youtube_embed_layout_step1_solution_assessment.md Plans Plans and history