-
Reply title directive — Step 3: Development Plan
Effort study: railspike-effort / v3/replytitledirective — host ledger; standing enrollment under protocol P2
docs/plans/reply_title_directive/reply_title_directive_step3_development_plan.md Plans
-
Reply title directive — Step 4: Implementation Summary
Effort study: railspike-effort / v3/replytitledirective — host ledger; standing enrollment under protocol P2
docs/plans/reply_title_directive/reply_title_directive_step4_implementation_summary.md Plans
-
Reply title live update — Railspike debug log
Debug mode: enabled (project marker .railspikedebugon).
docs/plans/reply_title_live_update/reply_title_live_update_debug_log.md Plans
-
reply_title_live_update_one_shot.md
Cycle: v3/replytitleliveupdate; Mode: one-shot; Record: this file; Index: plans index; Predecessor: v3/replytitledirective
docs/plans/reply_title_live_update/reply_title_live_update_one_shot.md Plans
-
repository_archive_readme_step1_solution_assessment.md
Effort study: railspike-effort / v3/repositoryarchivereadme; host ledger.
docs/plans/repository_archive_readme/repository_archive_readme_step1_solution_assessment.md Plans
-
repository_archive_readme_step2_feature_description.md
Effort study: railspike-effort / v3/repositoryarchivereadme; host ledger.
docs/plans/repository_archive_readme/repository_archive_readme_step2_feature_description.md Plans
-
repository_archive_readme_step3_development_plan.md
Effort study: railspike-effort / v3/repositoryarchivereadme; ledger.
docs/plans/repository_archive_readme/repository_archive_readme_step3_development_plan.md Plans
-
repository_archive_readme_step4_implementation_summary.md
Effort study: railspike-effort / v3/repositoryarchivereadme; ledger.
docs/plans/repository_archive_readme/repository_archive_readme_step4_implementation_summary.md Plans
-
History-free repository exports — one-shot implementation
2026-10-24.
docs/plans/repository_content_export_one_shot_summary.md Plans
-
Repository Directory Cleanup — Railspike Debug Log
Debug mode: enabled, inherited from Step 1 and the explicit user request.
docs/plans/repository_directory_cleanup/repository_directory_cleanup_debug_log.md Plans
-
repository_directory_cleanup_step1_solution_assessment.md
I want to clean up the top-level directory for this project and possibly other second-level directories, so that the project looks neater on GitHub.
docs/plans/repository_directory_cleanup/repository_directory_cleanup_step1_solution_assessment.md Plans
-
repository_directory_cleanup_step2_feature_description.md
Loose notes and reference documents obscure the project's structure on GitHub.
docs/plans/repository_directory_cleanup/repository_directory_cleanup_step2_feature_description.md Plans
-
repository_directory_cleanup_step3_development_plan.md
docs/plans/repository_directory_cleanup/repository_directory_cleanup_step3_development_plan.md Plans
-
repository_directory_cleanup_step4_implementation_summary.md
docs/plans/repository_directory_cleanup/repository_directory_cleanup_step4_implementation_summary.md Plans
-
repository_import_compatibility_debug_log.md
Source: Step 1 option comparison, shared-contract reuse and normal-entry recovery.
docs/plans/repository_import_compatibility_debug_log.md Plans
-
repository_import_compatibility_step1_solution_assessment.md
Effort study: railspike-effort / v3/repositoryimportcompatibility; P2 ledger
docs/plans/repository_import_compatibility_step1_solution_assessment.md Plans
-
request_path_cheap_wins — Railspike debug log
Drafted Step 2 grounded in the three target files (FastmodMetaRead, FrontController/RouteServices, AssetFingerprint).
docs/plans/request_path_cheap_wins/request_path_cheap_wins_debug_log.md Plans
-
request_path_cheap_wins_step1_solution_assessment.md
Approval: APPROVED — user — 2026-10-25T16:41:40-04:00 — scope v1 (explicit "Approved Step 1" in session)
docs/plans/request_path_cheap_wins/request_path_cheap_wins_step1_solution_assessment.md Plans
-
request_path_cheap_wins_step2_feature_description.md
Approval: APPROVED — user — 2026-10-25T17:16:00-04:00 — scope v1 (explicit "Approved Step 2" in session)
docs/plans/request_path_cheap_wins/request_path_cheap_wins_step2_feature_description.md Plans
-
request_path_cheap_wins_step3_development_plan.md
Approval: APPROVED — user — 2026-10-25T17:17:37-04:00 — scope v1 (explicit "Approved Step 3" in session)
docs/plans/request_path_cheap_wins/request_path_cheap_wins_step3_development_plan.md Plans
-
Step 4 — Implementation Summary
Approval: N/A — Step 4 is the implementation record; Steps 1–3 are APPROVED for scope v1 (recorded in their documents).
docs/plans/request_path_cheap_wins/request_path_cheap_wins_step4_implementation_summary.md Plans
-
Restore invitation prompt diagnostics
Necessary/useful instructions:
docs/plans/restore_invitation_prompt/restore_invitation_prompt_debug_log.md Plans
-
restore_invitation_prompt_step1_solution_assessment.md
Effort study: railspike-effort / v3/restoreinvitationprompt; ledger
docs/plans/restore_invitation_prompt/restore_invitation_prompt_step1_solution_assessment.md Plans
-
restore_invitation_prompt_step2_feature_description.md
Effort study: railspike-effort / v3/restoreinvitationprompt; ledger
docs/plans/restore_invitation_prompt/restore_invitation_prompt_step2_feature_description.md Plans
-
restore_invitation_prompt_step3_development_plan.md
Effort study: railspike-effort / v3/restoreinvitationprompt; ledger
docs/plans/restore_invitation_prompt/restore_invitation_prompt_step3_development_plan.md Plans
-
restore_invitation_prompt_step4_implementation_summary.md
Effort study: railspike-effort / v3/restoreinvitationprompt; ledger
docs/plans/restore_invitation_prompt/restore_invitation_prompt_step4_implementation_summary.md Plans
-
Railspike debug log: retracted_posts_hidden_from_listings
Mode source: .railspikedebugon project marker (new workflow, no explicit request).
docs/plans/retracted_posts_hidden_from_listings/retracted_posts_hidden_from_listings_debug_log.md Plans
-
retracted_posts_hidden_from_listings_step1_solution_assessment.md
When a post is deleted/retracted, it should no longer show up in listing pages.
docs/plans/retracted_posts_hidden_from_listings/retracted_posts_hidden_from_listings_step1_solution_assessment.md Plans
-
retracted_posts_hidden_from_listings_step2_feature_description.md
Retracted threads and posts still appear in listing pages as placeholder rows.
docs/plans/retracted_posts_hidden_from_listings/retracted_posts_hidden_from_listings_step2_feature_description.md Plans
-
retracted_posts_hidden_from_listings_step3_development_plan.md
docs/plans/retracted_posts_hidden_from_listings/retracted_posts_hidden_from_listings_step3_development_plan.md Plans
-
retracted_posts_hidden_from_listings_step4_implementation_summary.md
Branch: feat/retracted-posts-hidden-from-listings.
docs/plans/retracted_posts_hidden_from_listings/retracted_posts_hidden_from_listings_step4_implementation_summary.md Plans
-
retracted_post_llm_exchange_privacy_step1_solution_assessment.md
That's good.
docs/plans/retracted_post_llm_exchange_privacy/retracted_post_llm_exchange_privacy_step1_solution_assessment.md Plans
-
retracted_post_llm_exchange_privacy_step2_feature_description.md
LLM exchange logs can disclose a retracted post directly or through another post's recorded context.
docs/plans/retracted_post_llm_exchange_privacy/retracted_post_llm_exchange_privacy_step2_feature_description.md Plans
-
retracted_post_llm_exchange_privacy_step3_development_plan.md
docs/plans/retracted_post_llm_exchange_privacy/retracted_post_llm_exchange_privacy_step3_development_plan.md Plans
-
retracted_post_llm_exchange_privacy_step4_implementation_summary.md
docs/plans/retracted_post_llm_exchange_privacy/retracted_post_llm_exchange_privacy_step4_implementation_summary.md Plans
-
Retraction design mistakes checklist
Date: 2026-10-24.
docs/plans/retraction_design_mistakes_checklist.md Plans
-
Retraction effects — Railspike debug log
No supported findings.
docs/plans/retraction_effects/retraction_effects_debug_log.md Plans
-
retraction_effects_step1_solution_assessment.md
Effort study: railspike-effort, cycle v3/retractioneffects; standing P2 enrollment; ledger.
docs/plans/retraction_effects/retraction_effects_step1_solution_assessment.md Plans
-
retraction_effects_step2_feature_description.md
Effort study: railspike-effort, cycle v3/retractioneffects; standing P2 enrollment; ledger.
docs/plans/retraction_effects/retraction_effects_step2_feature_description.md Plans
-
retraction_effects_step2_v4_historical.md
Effort study: railspike-effort, cycle v3/retractioneffects; standing P2 enrollment; ledger.
docs/plans/retraction_effects/retraction_effects_step2_v4_historical.md Plans