zenmemes

New post

zenmemes Platform Docs

Docs home

Documents

2,573 documents

Filters
  1. 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 Plans and history

  2. 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 Plans and history

  3. 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 Plans and history

  4. Forte Unauthenticated Vote Identity Setup — Step 4: Implementation Summary

    docs/plans/forte_unauthenticated_vote_identity_setup/forte_unauthenticated_vote_identity_setup_step4_implementation_summary.md Plans Plans and history

  5. Lessons from Building Forte Users → Carry Back to Board/Activity

    Findings from implementing the Users three-pane view (docs/plans/archive/forteusersthreepanestep4implementationsummary.md) that are relevant to Board and Activ…

    docs/plans/forte_users_lessons_for_board_activity.md Plans Plans and history

  6. gloss_theme debug log

    No supported findings.

    docs/plans/gloss_theme/gloss_theme_debug_log.md Plans Plans and history

  7. gloss_theme_step1_solution_assessment.md

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

    docs/plans/gloss_theme/gloss_theme_step1_solution_assessment.md Plans Plans and history

  8. gloss_theme_step2_feature_description.md

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

    docs/plans/gloss_theme/gloss_theme_step2_feature_description.md Plans Plans and history

  9. gloss_theme_step3_development_plan.md

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

    docs/plans/gloss_theme/gloss_theme_step3_development_plan.md Plans Plans and history

  10. gloss_theme_step4_implementation_summary.md

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

    docs/plans/gloss_theme/gloss_theme_step4_implementation_summary.md Plans Plans and history

  11. gpg_agent_leak debug log

    docs/plans/gpg_agent_leak/gpg_agent_leak_debug_log.md Plans Plans and history

  12. Step 2: Feature Description – GPG agent leak

    Debug mode: enabled (project default via .railspikedebugon)

    docs/plans/gpg_agent_leak/gpg_agent_leak_step2_feature_description.md Plans Plans and history

  13. Step 3: Development Plan – GPG agent leak

    docs/plans/gpg_agent_leak/gpg_agent_leak_step3_development_plan.md Plans Plans and history

  14. Step 4: Implementation Summary – GPG agent leak

    docs/plans/gpg_agent_leak/gpg_agent_leak_step4_implementation_summary.md Plans Plans and history

  15. Future Feature Note: Guest Keypair + Proof-of-Work Voting

    Not scheduled yet.

    docs/plans/guest_identity_proof_of_work_voting.md Plans Plans and history

  16. guided_php_setup_fallback_step1_solution_assessment.md

    Please write Step 1 of docs/fdp/FEATUREDEVELOPMENTPROCESS.md for the more comprehensive no-PHP fallback we discussed before.

    docs/plans/guided_php_setup_fallback/guided_php_setup_fallback_step1_solution_assessment.md Plans Plans and history

  17. guided_php_setup_fallback_step2_feature_description.md

    The existing missing-PHP fallback points to general setup documentation, leaving users to find instructions for their environment.

    docs/plans/guided_php_setup_fallback/guided_php_setup_fallback_step2_feature_description.md Plans Plans and history

  18. guided_php_setup_fallback_step3_development_plan.md

    docs/plans/guided_php_setup_fallback/guided_php_setup_fallback_step3_development_plan.md Plans Plans and history

  19. guided_php_setup_fallback_step4_implementation_summary.md

    docs/plans/guided_php_setup_fallback/guided_php_setup_fallback_step4_implementation_summary.md Plans Plans and history

  20. Hide Messages new-message form — Railspike debug log

    docs/plans/hide_messages_new_message_form/hide_messages_new_message_form_debug_log.md Plans Plans and history

  21. hide_messages_new_message_form_step1_solution_assessment.md

    A user found the "New message" form on the /messages/ page confusing, thinking it is a registration form.

    docs/plans/hide_messages_new_message_form/hide_messages_new_message_form_step1_solution_assessment.md Plans Plans and history

  22. hide_messages_new_message_form_step2_feature_description.md

    The “New message” recipient form on /messages/ can be mistaken for registration.

    docs/plans/hide_messages_new_message_form/hide_messages_new_message_form_step2_feature_description.md Plans Plans and history

  23. hide_messages_new_message_form_step3_development_plan.md

    docs/plans/hide_messages_new_message_form/hide_messages_new_message_form_step3_development_plan.md Plans Plans and history

  24. hide_messages_new_message_form_step4_implementation_summary.md

    docs/plans/hide_messages_new_message_form/hide_messages_new_message_form_step4_implementation_summary.md Plans Plans and history

  25. High-traffic absent retractions — Railspike debug log

    No supported findings.

    docs/plans/high_traffic_absent_retractions/high_traffic_absent_retractions_debug_log.md Plans Plans and history

  26. high_traffic_absent_retractions_step1_solution_assessment.md

    Effort study: railspike-effort, cycle v3/hightrafficabsentretractions; host ledger, standing enrollment R1/P2.

    docs/plans/high_traffic_absent_retractions/high_traffic_absent_retractions_step1_solution_assessment.md Plans Plans and history

  27. high_traffic_absent_retractions_step2_feature_description.md

    Effort study: railspike-effort, cycle v3/hightrafficabsentretractions; host ledger, R1/P2.

    docs/plans/high_traffic_absent_retractions/high_traffic_absent_retractions_step2_feature_description.md Plans Plans and history

  28. high_traffic_absent_retractions_step3_development_plan.md

    Effort study: railspike-effort, cycle v3/hightrafficabsentretractions; host ledger, R1/P2.

    docs/plans/high_traffic_absent_retractions/high_traffic_absent_retractions_step3_development_plan.md Plans Plans and history

  29. high_traffic_absent_retractions_step4_implementation_summary.md

    Effort study: railspike-effort, cycle v3/hightrafficabsentretractions; ledger, R1/P2.

    docs/plans/high_traffic_absent_retractions/high_traffic_absent_retractions_step4_implementation_summary.md Plans Plans and history

  30. high_traffic_diagnostic_explanation.txt

    docs/plans/high_traffic_diagnostic_explanation.txt Plans Plans and history

  31. High-traffic mode — Railspike debug log

    No supported findings.

    docs/plans/high_traffic_mode/high_traffic_mode_debug_log.md Plans Plans and history

  32. high_traffic_mode_step1_solution_assessment.md

    I want to design high-traffic mode which uses the following structure:

    docs/plans/high_traffic_mode/high_traffic_mode_step1_solution_assessment.md Plans Plans and history

  33. high_traffic_mode_step2_feature_description.md

    Repeated public-page requests consume PHP capacity even when slightly stale shared HTML would suffice.

    docs/plans/high_traffic_mode/high_traffic_mode_step2_feature_description.md Plans Plans and history

  34. high_traffic_mode_step3_development_plan.md

    Deliver operator UI/CLI enable → bounded first generation → session-bearing Apache warm hit → atomic popularity-driven cron refresh → disable/recovery.

    docs/plans/high_traffic_mode/high_traffic_mode_step3_development_plan.md Plans Plans and history

  35. high_traffic_mode_step4_implementation_summary.md

    Branch: feature/high-traffic-mode.

    docs/plans/high_traffic_mode/high_traffic_mode_step4_implementation_summary.md Plans Plans and history

  36. high_traffic_toggle Railspike debug log

    docs/plans/high_traffic_toggle/high_traffic_toggle_debug_log.md Plans Plans and history

  37. high_traffic_toggle_step1_solution_assessment.md

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

    docs/plans/high_traffic_toggle/high_traffic_toggle_step1_solution_assessment.md Plans Plans and history

  38. high_traffic_toggle_step2_feature_description.md

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

    docs/plans/high_traffic_toggle/high_traffic_toggle_step2_feature_description.md Plans Plans and history

  39. high_traffic_toggle_step3_development_plan.md

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

    docs/plans/high_traffic_toggle/high_traffic_toggle_step3_development_plan.md Plans Plans and history

  40. high_traffic_toggle_step4_implementation_summary.md

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

    docs/plans/high_traffic_toggle/high_traffic_toggle_step4_implementation_summary.md Plans Plans and history