-
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
-
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
-
gloss_theme debug log
No supported findings.
docs/plans/gloss_theme/gloss_theme_debug_log.md Plans
-
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
-
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
-
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
-
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
-
gpg_agent_leak debug log
docs/plans/gpg_agent_leak/gpg_agent_leak_debug_log.md Plans
-
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
-
Step 3: Development Plan – GPG agent leak
docs/plans/gpg_agent_leak/gpg_agent_leak_step3_development_plan.md Plans
-
Step 4: Implementation Summary – GPG agent leak
docs/plans/gpg_agent_leak/gpg_agent_leak_step4_implementation_summary.md Plans
-
Future Feature Note: Guest Keypair + Proof-of-Work Voting
Not scheduled yet.
docs/plans/guest_identity_proof_of_work_voting.md Plans
-
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
-
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
-
guided_php_setup_fallback_step3_development_plan.md
docs/plans/guided_php_setup_fallback/guided_php_setup_fallback_step3_development_plan.md Plans
-
guided_php_setup_fallback_step4_implementation_summary.md
docs/plans/guided_php_setup_fallback/guided_php_setup_fallback_step4_implementation_summary.md Plans
-
Hide Messages new-message form — Railspike debug log
docs/plans/hide_messages_new_message_form/hide_messages_new_message_form_debug_log.md Plans
-
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
-
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
-
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
-
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
-
High-traffic absent retractions — Railspike debug log
No supported findings.
docs/plans/high_traffic_absent_retractions/high_traffic_absent_retractions_debug_log.md Plans
-
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
-
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
-
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
-
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
-
high_traffic_diagnostic_explanation.txt
docs/plans/high_traffic_diagnostic_explanation.txt Plans
-
High-traffic mode — Railspike debug log
No supported findings.
docs/plans/high_traffic_mode/high_traffic_mode_debug_log.md Plans
-
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
-
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
-
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
-
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
-
high_traffic_toggle Railspike debug log
docs/plans/high_traffic_toggle/high_traffic_toggle_debug_log.md Plans
-
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
-
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
-
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
-
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
-
History purge — Railspike debug log
docs/plans/history_purge/history_purge_debug_log.md Plans
-
history_purge_step1_solution_assessment.md
Effort study: railspike-effort / v3/historypurge; ledger, standing P2 enrollment.
docs/plans/history_purge/history_purge_step1_solution_assessment.md Plans
-
history_purge_step2_feature_description.md
Effort study: railspike-effort / v3/historypurge; ledger, standing P2 enrollment.
docs/plans/history_purge/history_purge_step2_feature_description.md Plans