zenmemes

New post

zenmemes Platform Docs

Docs home

Documents

2,188 documents

Filters
  1. Step 1: Solution Assessment — Feature Flag Lock Explanation

    The /tools/feature-flags/ page hides why a flag is locked in a hover-only tooltip, and conflates that data-source lock with a separate, unshown root-approval p…

    docs/plans/feature_flag_lock_explanation/feature_flag_lock_explanation_step1_solution_assessment.md Plans

  2. Step 2: Feature Description — Feature Flag Lock Explanation

    The feature flags page doesn't explain why a flag is locked (reason is hidden in a hover-only tooltip) and shows mutable flags as apparently editable to viewer…

    docs/plans/feature_flag_lock_explanation/feature_flag_lock_explanation_step2_feature_description.md Plans

  3. Step 3: Development Plan — Feature Flag Lock Explanation

    docs/plans/feature_flag_lock_explanation/feature_flag_lock_explanation_step3_development_plan.md Plans

  4. Step 4: Implementation Summary — Feature Flag Lock Explanation

    docs/plans/feature_flag_lock_explanation/feature_flag_lock_explanation_step4_implementation_summary.md Plans

  5. Step 1: Solution Assessment — Feature Flag Write Triggers Spurious Read-Model Rebuild

    LocalWriteService::setFeatureFlag() commits a new git SHA but never updates the read model's stored repositoryhead metadata, so the very next request to hit Ap…

    docs/plans/feature_flag_readmodel_rebuild_fix/feature_flag_readmodel_rebuild_fix_step1_solution_assessment.md Plans

  6. Step 2: Feature Description — Feature Flag Write Triggers Spurious Read-Model Rebuild

    Feature-flag writes commit a new canonical-record SHA to git but never update the read model's stored repositoryhead metadata, so Application::ensureReadModel(…

    docs/plans/feature_flag_readmodel_rebuild_fix/feature_flag_readmodel_rebuild_fix_step2_feature_description.md Plans

  7. Step 3: Development Plan — Feature Flag Write Triggers Spurious Read-Model Rebuild

    docs/plans/feature_flag_readmodel_rebuild_fix/feature_flag_readmodel_rebuild_fix_step3_development_plan.md Plans

  8. Step 4: Implementation Summary — Feature Flag Read-Model Rebuild Fix

    docs/plans/feature_flag_readmodel_rebuild_fix/feature_flag_readmodel_rebuild_fix_step4_implementation_summary.md Plans

  9. feedback_work_restart_step1_solution_assessment.md

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

    docs/plans/feedback_work_restart/feedback_work_restart_step1_solution_assessment.md Plans

  10. feedback_work_restart_step2_feature_description.md

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

    docs/plans/feedback_work_restart/feedback_work_restart_step2_feature_description.md Plans

  11. feedback_work_restart_step3_development_plan.md

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

    docs/plans/feedback_work_restart/feedback_work_restart_step3_development_plan.md Plans

  12. feedback_work_restart_step4_implementation_summary.md

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

    docs/plans/feedback_work_restart/feedback_work_restart_step4_implementation_summary.md Plans

  13. Firefox Console Warnings Cause Notes

    This note documents the Firefox console warnings observed while loading the local app at http://127.0.0.1:8000.

    docs/plans/firefox_console_warnings_causes_v1.md Plans

  14. Forte Activity: per-kind left-pane filters — implementation summary

    Workflow: Direct (small, single-surface change).

    docs/plans/forte_activity_kind_filters/forte_activity_kind_filters_implementation_summary.md Plans

  15. Forte Activity parity — Railspike debug log

    Debug mode: enabled from the project marker for this new workflow.

    docs/plans/forte_activity_parity/forte_activity_parity_debug_log.md Plans

  16. forte_activity_parity_step2_feature_description.md

    Forte Activity and the default Activity page share activity data but differ in controls and presentation of evidence.

    docs/plans/forte_activity_parity/forte_activity_parity_step2_feature_description.md Plans

  17. forte_activity_parity_step3_development_plan.md

    docs/plans/forte_activity_parity/forte_activity_parity_step3_development_plan.md Plans

  18. forte_activity_parity_step4_implementation_summary.md

    Status: All three implementation stages complete and locally verified.

    docs/plans/forte_activity_parity/forte_activity_parity_step4_implementation_summary.md Plans

  19. Forte Board Memory-Safe Thread Loading Step 1 Solution Assessment

    Please help me debug this issue with the Forte interface:

    docs/plans/forte_board_memory_safe_thread_loading/forte_board_memory_safe_thread_loading_step1_solution_assessment.md Plans

  20. Forte Board Memory-Safe Thread Loading Step 2 Feature Description

    The Forte board includes every thread body and reply tree in its initial, hidden content pane.

    docs/plans/forte_board_memory_safe_thread_loading/forte_board_memory_safe_thread_loading_step2_feature_description.md Plans

  21. Forte Board Memory-Safe Thread Loading Step 3 Development Plan

    docs/plans/forte_board_memory_safe_thread_loading/forte_board_memory_safe_thread_loading_step3_development_plan.md Plans

  22. Forte Board Memory-Safe Thread Loading Step 4 Implementation Summary

    docs/plans/forte_board_memory_safe_thread_loading/forte_board_memory_safe_thread_loading_step4_implementation_summary.md Plans

  23. forte_dark_theme_step1_solution_assessment.md

    I want the Forte interface to respect the user's dark mode settings.

    docs/plans/forte_dark_theme/forte_dark_theme_step1_solution_assessment.md Plans

  24. forte_dark_theme_step2_feature_description.md

    Forte always renders in a fixed light palette, ignoring both the viewer's OS dark mode and the theme they chose on the site.

    docs/plans/forte_dark_theme/forte_dark_theme_step2_feature_description.md Plans

  25. forte_dark_theme_step3_development_plan.md

    docs/plans/forte_dark_theme/forte_dark_theme_step3_development_plan.md Plans

  26. forte_dark_theme_step4_implementation_summary.md

    docs/plans/forte_dark_theme/forte_dark_theme_step4_implementation_summary.md Plans

  27. Forte — FDP Cycle Backlog

    Exhaustive, ordered list of every Feature Development Process cycle needed to close the gaps identified in forteroadmap.md Section A.

    docs/plans/forte_fdp_cycles.md Plans

  28. Step 1: Solution Assessment — Forte Mobile-Friendliness

    The paned three-column views (Users, Board, Activity) and the rest of Forte rely on ad hoc, per-component breakpoints (site.css has 5 separate @media blocks, n…

    docs/plans/forte_mobile_friendly/forte_mobile_friendly_step1_solution_assessment.md Plans

  29. Forte Mobile Stacked Panes — Step 1: Solution Assessment

    On mobile views (narrow screens), I want the Forte view to stack all 3 panes vertically, so that it is usable.

    docs/plans/forte_mobile_stacked_panes/forte_mobile_stacked_panes_step1_solution_assessment.md Plans

  30. Forte Mobile Stacked Panes — Step 2: Feature Description

    At narrow viewport widths, Forte retains its desktop side-by-side pane layout, making the list and content panes too narrow to use.

    docs/plans/forte_mobile_stacked_panes/forte_mobile_stacked_panes_step2_feature_description.md Plans

  31. Forte Mobile Stacked Panes — Step 3: Development Plan

    docs/plans/forte_mobile_stacked_panes/forte_mobile_stacked_panes_step3_development_plan.md Plans

  32. Forte Mobile Stacked Panes — Step 4: Implementation Summary

    docs/plans/forte_mobile_stacked_panes/forte_mobile_stacked_panes_step4_implementation_summary.md Plans

  33. Forte Reply Likes — Step 1: Solution Assessment

    Forte lets readers Like a top-level thread and Flag any post, but its comments and nested replies lack a Like control.

    docs/plans/forte_reply_likes/forte_reply_likes_step1_solution_assessment.md Plans

  34. Forte Reply Likes — Step 2: Feature Description

    Forte renders Flag for every comment and nested reply but not Like, unlike the classic post interface.

    docs/plans/forte_reply_likes/forte_reply_likes_step2_feature_description.md Plans

  35. Forte Reply Likes — Step 3: Development Plan

    Reply Approved Step 3 to begin implementation.

    docs/plans/forte_reply_likes/forte_reply_likes_step3_development_plan.md Plans

  36. Forte Reply Likes — Step 4: Implementation Summary

    docs/plans/forte_reply_likes/forte_reply_likes_step4_implementation_summary.md Plans

  37. Forte Interface — Feature Roadmap

    Consolidated backlog of what's still missing, deliberately excluded, or rough around the edges in Forte, based on a gap analysis against the classic UI's full…

    docs/plans/forte_roadmap.md Plans

  38. Forte Unauthenticated Vote Identity Setup — Step 1: Solution Assessment

    For a Forte visitor without a prepared browser identity, a vote can fail with a generic reload instruction instead of loading identity setup or explaining why…

    docs/plans/forte_unauthenticated_vote_identity_setup/forte_unauthenticated_vote_identity_setup_step1_solution_assessment.md Plans

  39. Forte Unauthenticated Vote Identity Setup — Step 2: Feature Description

    An unsigned Forte visitor who votes before preparing a browser identity can receive a generic reload message that conceals the failed prerequisite and leaves t…

    docs/plans/forte_unauthenticated_vote_identity_setup/forte_unauthenticated_vote_identity_setup_step2_feature_description.md Plans

  40. Forte Unauthenticated Vote Identity Setup — Step 3: Development Plan

    docs/plans/forte_unauthenticated_vote_identity_setup/forte_unauthenticated_vote_identity_setup_step3_development_plan.md Plans