-
retraction_effects_step3_development_plan.md
Effort study: railspike-effort, v3/retractioneffects; ledger.
docs/plans/retraction_effects/retraction_effects_step3_development_plan.md Plans
-
retraction_effects_step3_split_history.md
Effort study: railspike-effort, cycle v3/retractioneffects; standing P2 enrollment; ledger.
docs/plans/retraction_effects/retraction_effects_step3_split_history.md Plans
-
retraction_effects_step4_implementation_summary.md
Effort study: railspike-effort, v3/retractioneffects; ledger.
docs/plans/retraction_effects/retraction_effects_step4_implementation_summary.md Plans
-
Retraction simplification — Railspike debug log
Debug mode enabled by project marker presence.
docs/plans/retraction_simplification/retraction_simplification_debug_log.md Plans
-
retraction_simplification_step1_solution_assessment.md
Effort study: railspike-effort / v3/retractionsimplification; standing P2 enrollment.
docs/plans/retraction_simplification/retraction_simplification_step1_solution_assessment.md Plans
-
retraction_simplification_step2_feature_description.md
Effort study: railspike-effort / v3/retractionsimplification; standing P2 enrollment.
docs/plans/retraction_simplification/retraction_simplification_step2_feature_description.md Plans
-
retraction_simplification_step3_development_plan.md
Effort study: railspike-effort / v3/retractionsimplification; P2 ledger.
docs/plans/retraction_simplification/retraction_simplification_step3_development_plan.md Plans
-
retraction_simplification_step4_implementation_summary.md
Effort study: railspike-effort / v3/retractionsimplification; ledger.
docs/plans/retraction_simplification/retraction_simplification_step4_implementation_summary.md Plans
-
Retraction simplification: agent handoff
2026-10-24.
docs/plans/retraction_simplification_handoff.md Plans
-
retraction_speed debug log
docs/plans/retraction_speed/retraction_speed_debug_log.md Plans
-
retraction_speed_step1_solution_assessment.md
Debug mode: enabled (debug log)
docs/plans/retraction_speed/retraction_speed_step1_solution_assessment.md Plans
-
retraction_speed_step2_feature_description.md
Debug mode: enabled (debug log)
docs/plans/retraction_speed/retraction_speed_step2_feature_description.md Plans
-
retraction_speed_step3_development_plan.md
Debug mode: enabled (debug log)
docs/plans/retraction_speed/retraction_speed_step3_development_plan.md Plans
-
retraction_speed_step4_implementation_summary.md
Debug mode: enabled (debug log)
docs/plans/retraction_speed/retraction_speed_step4_implementation_summary.md Plans
-
Retraction sweep evidence diagnostics report
Date: 2026-10-24.
docs/plans/retraction_sweep_evidence_diagnostics_report.md Plans
-
Retraction text format — Railspike diagnostics
No supported findings.
docs/plans/retraction_text_format/retraction_text_format_debug_log.md Plans
-
retraction_text_format_step1_solution_assessment.md
Effort study: railspike-effort / v3/retractiontextformat; ledger.
docs/plans/retraction_text_format/retraction_text_format_step1_solution_assessment.md Plans
-
retraction_text_format_step2_feature_description.md
Effort study: railspike-effort / v3/retractiontextformat; ledger.
docs/plans/retraction_text_format/retraction_text_format_step2_feature_description.md Plans
-
retraction_text_format_step3_development_plan.md
Effort study: railspike-effort / v3/retractiontextformat; ledger.
docs/plans/retraction_text_format/retraction_text_format_step3_development_plan.md Plans
-
retraction_text_format_step4_implementation_summary.md
Effort study: railspike-effort / v3/retractiontextformat; ledger.
docs/plans/retraction_text_format/retraction_text_format_step4_implementation_summary.md Plans
-
Root approval pages — Railspike debug log
Debug mode: enabled, inherited from the project marker for this new workflow.
docs/plans/root_approval_pages/root_approval_pages_debug_log.md Plans
-
root_approval_pages_step1_solution_assessment.md
We should make pages for the root approval posts.
docs/plans/root_approval_pages/root_approval_pages_step1_solution_assessment.md Plans
-
root_approval_pages_step2_feature_description.md
Account key history opens readable post pages for ordinary approvals but plaintext files for root approval seeds.
docs/plans/root_approval_pages/root_approval_pages_step2_feature_description.md Plans
-
root_approval_pages_step3_development_plan.md
docs/plans/root_approval_pages/root_approval_pages_step3_development_plan.md Plans
-
root_approval_pages_step4_implementation_summary.md
Status: Both stages complete and locally verified on feature/root-approval-pages.
docs/plans/root_approval_pages/root_approval_pages_step4_implementation_summary.md Plans
-
runtime_detail_pages_step1_solution_assessment.md
Most of the time this activity is not necessary, since we can dynamically generate the pages during runtime.
docs/plans/runtime_detail_pages/runtime_detail_pages_step1_solution_assessment.md Plans
-
runtime_detail_pages_step2_feature_description.md
Routine builds render every thread and post despite available runtime rendering, making builds unnecessarily slow.
docs/plans/runtime_detail_pages/runtime_detail_pages_step2_feature_description.md Plans
-
runtime_detail_pages_step3_development_plan.md
docs/plans/runtime_detail_pages/runtime_detail_pages_step3_development_plan.md Plans
-
runtime_detail_pages_step4_implementation_summary.md
docs/plans/runtime_detail_pages/runtime_detail_pages_step4_implementation_summary.md Plans
-
Same-author collapse toggle — Railspike debug log
No supported findings.
docs/plans/same_author_collapse_toggle/same_author_collapse_toggle_debug_log.md Plans
-
Same-author collapse toggle
Thread views automatically merge consecutive quick replies from the same author.
docs/plans/same_author_collapse_toggle/same_author_collapse_toggle_step2_feature_description.md Plans
-
Same-author collapse toggle — development plan
docs/plans/same_author_collapse_toggle/same_author_collapse_toggle_step3_development_plan.md Plans
-
Same-author collapse toggle — implementation
docs/plans/same_author_collapse_toggle/same_author_collapse_toggle_step4_implementation_summary.md Plans
-
same_username_operator debug log
No supported findings.
docs/plans/same_username_operator/same_username_operator_debug_log.md Plans
-
same_username_operator_step1_solution_assessment.md
Effort study: railspike-effort / v3/sameusernameoperator; host ledger.
docs/plans/same_username_operator/same_username_operator_step1_solution_assessment.md Plans
-
same_username_operator_step2_feature_description.md
Effort study: railspike-effort / v3/sameusernameoperator; host ledger.
docs/plans/same_username_operator/same_username_operator_step2_feature_description.md Plans
-
same_username_operator_step3_development_plan.md
Effort study: railspike-effort / v3/sameusernameoperator; host ledger.
docs/plans/same_username_operator/same_username_operator_step3_development_plan.md Plans
-
same_username_operator_step4_implementation_summary.md
Effort study: railspike-effort / v3/sameusernameoperator; host ledger.
docs/plans/same_username_operator/same_username_operator_step4_implementation_summary.md Plans
-
Scripture-Oriented Analysis Step 1 Solution Assessment
As a faithful user, I want another type of agentic analysis available to me:
docs/plans/scripture_oriented_analysis/scripture_oriented_analysis_step1_solution_assessment.md Plans
-
Scripture-Oriented Analysis Step 2 Feature Description
Readers can request several kinds of agent responses but cannot select a scriptural reflection on a post.
docs/plans/scripture_oriented_analysis/scripture_oriented_analysis_step2_feature_description.md Plans