-
case_insensitive_tags_step3_development_plan.md
Every stage includes tests and a summary in its commit before the next begins.
docs/plans/case_insensitive_tags/case_insensitive_tags_step3_development_plan.md Plans Plans and history
-
case_insensitive_tags_step4_implementation_summary.md
Feature branch: feature/case-insensitive-tags.
docs/plans/case_insensitive_tags/case_insensitive_tags_step4_implementation_summary.md Plans Plans and history
-
Checkout overview debug log
No supported findings.
docs/plans/checkout_overview/checkout_overview_debug_log.md Plans Plans and history
-
checkout_overview_step1_solution_assessment.md
Effort study: railspike-effort / v3/checkoutoverview; standing P2 enrollment.
docs/plans/checkout_overview/checkout_overview_step1_solution_assessment.md Plans Plans and history
-
checkout_overview_step2_feature_description.md
Effort study: railspike-effort / v3/checkoutoverview; standing P2 enrollment.
docs/plans/checkout_overview/checkout_overview_step2_feature_description.md Plans Plans and history
-
checkout_overview_step3_development_plan.md
Effort study: railspike-effort / v3/checkoutoverview; standing P2 enrollment.
docs/plans/checkout_overview/checkout_overview_step3_development_plan.md Plans Plans and history
-
checkout_overview_step4_implementation_summary.md
Effort study: railspike-effort / v3/checkoutoverview; ledger, v1/R1/P2, Codex single exposed rater.
docs/plans/checkout_overview/checkout_overview_step4_implementation_summary.md Plans Plans and history
-
terminal_acceptance.txt
docs/plans/checkout_overview/terminal_acceptance.txt Plans Plans and history
-
timing_acceptance.json
docs/plans/checkout_overview/timing_acceptance.json Plans Plans and history
-
timing_acceptance_initial.json
docs/plans/checkout_overview/timing_acceptance_initial.json Plans Plans and history
-
Chicago post actions — Railspike debug log
docs/plans/chicago_post_actions/chicago_post_actions_debug_log.md Plans Plans and history
-
Chicago post actions — one-shot
Cycle: v3/chicagopostactions; Mode: one-shot; Record/index: this file, plans index
docs/plans/chicago_post_actions/chicago_post_actions_one_shot.md Plans Plans and history
-
Hosting chouse.club on this framework — plan v1
zenmemes.com as two separate communities (separate content, separate
docs/plans/chouse_club_hosting_plan_v1.md Plans Plans and history
-
Chouse Production Release — Step 1: Solution Assessment
The existing placeholder chouse site must be replaced by this codebase on
docs/plans/chouse_production_readiness/chouse_production_readiness_step1_solution_assessment.md Plans Plans and history
-
Codebase Cleanup Audit — Phase 0 Findings
Output of Phase 0 (inventory) from codebasecleanupauditplanv1.md.
docs/plans/codebase_cleanup_audit_findings_v1.md Plans Plans and history
-
Codebase Cleanup & Readability Audit — Plan v1
Prep for a demo to a code-review-literate audience.
docs/plans/codebase_cleanup_audit_plan_v1.md Plans Plans and history
-
Codebase Page Source Details Step 3 Development Plan
docs/plans/codebase_page_source_details/codebase_page_source_details_step3_development_plan.md Plans Plans and history
-
codex_session_model_isolation_debug_log.md
docs/plans/codex_session_model_isolation_debug_log.md Plans Plans and history
-
codex_session_model_isolation_step1_solution_assessment.md
I'm running multiple concurrent Codex CLI instances under the same WSL user.
docs/plans/codex_session_model_isolation_step1_solution_assessment.md Plans Plans and history
-
Composer anchor and exit — Railspike debug log
No supported findings.
docs/plans/composer_anchor_exit_debug_log.md Plans Plans and history
-
composer_anchor_exit_step1_solution_assessment.md
Effort study: railspike-effort / v3/composeranchorexit · Host ledger · Standing enrollment P2
docs/plans/composer_anchor_exit_step1_solution_assessment.md Plans Plans and history
-
compose_keyboard_fit Railspike debug log
Mode: enabled by the project marker .railspikedebugon (new workflow, no explicit request).
docs/plans/compose_keyboard_fit/compose_keyboard_fit_debug_log.md Plans Plans and history
-
compose_keyboard_fit_step1_solution_assessment.md
Debug mode: enabled (.railspikedebugon present at the project root; new workflow)
docs/plans/compose_keyboard_fit/compose_keyboard_fit_step1_solution_assessment.md Plans Plans and history
-
compose_keyboard_fit_step2_feature_description.md
Effort study: railspike-effort / v3/composekeyboardfit (ledger); standing enrollment P2
docs/plans/compose_keyboard_fit/compose_keyboard_fit_step2_feature_description.md Plans Plans and history
-
compose_keyboard_fit_step3_development_plan.md
Effort study: railspike-effort / v3/composekeyboardfit (ledger); standing enrollment P2
docs/plans/compose_keyboard_fit/compose_keyboard_fit_step3_development_plan.md Plans Plans and history
-
compose_keyboard_fit_step4_implementation_summary.md
Effort study: railspike-effort / v3/composekeyboardfit (ledger); standing enrollment P2
docs/plans/compose_keyboard_fit/compose_keyboard_fit_step4_implementation_summary.md Plans Plans and history
-
Compose thread declutter — Railspike debug log
Debug mode enabled via the repository's .railspikedebugon flag file.
docs/plans/compose_thread_declutter/compose_thread_declutter_debug_log.md Plans Plans and history
-
compose_thread_declutter_step1_solution_assessment.md
As a user, I feel intimidated by the /compose/thread page.
docs/plans/compose_thread_declutter/compose_thread_declutter_step1_solution_assessment.md Plans Plans and history
-
compose_thread_declutter_step2_feature_description.md
The full-page thread composer shows a heading, an implementation-detail intro, tags, subject, body, four event inputs, the image uploader, and three action but…
docs/plans/compose_thread_declutter/compose_thread_declutter_step2_feature_description.md Plans Plans and history
-
compose_thread_declutter_step3_development_plan.md
docs/plans/compose_thread_declutter/compose_thread_declutter_step3_development_plan.md Plans Plans and history
-
compose_thread_declutter_step4_implementation_summary.md
docs/plans/compose_thread_declutter/compose_thread_declutter_step4_implementation_summary.md Plans Plans and history
-
Concurrent checkouts debug log
No supported findings.
docs/plans/concurrent_checkouts/concurrent_checkouts_debug_log.md Plans Plans and history
-
concurrent_checkouts_step1_solution_assessment.md
Effort study: railspike-effort / v3/concurrentcheckouts; standing P2 enrollment.
docs/plans/concurrent_checkouts/concurrent_checkouts_step1_solution_assessment.md Plans Plans and history
-
concurrent_checkouts_step2_feature_description.md
Effort study: railspike-effort / v3/concurrentcheckouts; standing P2 enrollment.
docs/plans/concurrent_checkouts/concurrent_checkouts_step2_feature_description.md Plans Plans and history
-
concurrent_checkouts_step3_development_plan.md
Effort study: railspike-effort / v3/concurrentcheckouts; standing P2 enrollment.
docs/plans/concurrent_checkouts/concurrent_checkouts_step3_development_plan.md Plans Plans and history
-
concurrent_checkouts_step4_implementation_summary.md
Effort study: railspike-effort / v3/concurrentcheckouts; ledger, R1/P2, scope v4.
docs/plans/concurrent_checkouts/concurrent_checkouts_step4_implementation_summary.md Plans Plans and history
-
terminal_acceptance.txt
docs/plans/concurrent_checkouts/terminal_acceptance.txt Plans Plans and history
-
console_palette_implementation.txt
docs/plans/console_palette_implementation.txt Plans Plans and history
-
Deadlus Post Response And Content Assessment Outline V1
This document brainstorms a post-write feature for asking the Deadlus Labs API to:
docs/plans/deadlus_post_response_and_content_assessment_outline_v1.md Plans Plans and history
-
Dedalus Agent Reply Implementation Slices
Implement a fully automatic, transparent agentic reply agent.
docs/plans/dedalus_agent_reply_implementation_slices_v1.md Plans Plans and history