-
QDB Site News — Step 3: Development Plan
docs/plans/qdb_site_news/qdb_site_news_step3_development_plan.md Plans Plans and history
-
QDB Site News — Step 4: Implementation Summary
docs/plans/qdb_site_news/qdb_site_news_step4_implementation_summary.md Plans Plans and history
-
QDB Site News Compact — Step 1: Solution Assessment
For the site news module on the qdb theme, the entire news item should be displayed, not just the title.
docs/plans/qdb_site_news_compact/qdb_site_news_compact_step1_solution_assessment.md Plans Plans and history
-
QDB Site News Compact — Step 2: Feature Description
The QDB Welcome page's Site News panel shows only a linked title and long-form timestamp per item, so readers must click through to read any news.
docs/plans/qdb_site_news_compact/qdb_site_news_compact_step2_feature_description.md Plans Plans and history
-
QDB Site News Compact — Step 3: Development Plan
docs/plans/qdb_site_news_compact/qdb_site_news_compact_step3_development_plan.md Plans Plans and history
-
QDB Site News Compact — Step 4: Implementation Summary
docs/plans/qdb_site_news_compact/qdb_site_news_compact_step4_implementation_summary.md Plans Plans and history
-
QDB Tag View Filter Scope — Step 1: Solution Assessment
On the QDB site, if I access /tags/general, I want to still see all the content.
docs/plans/qdb_tag_view_filter_scope/qdb_tag_view_filter_scope_step1_solution_assessment.md Plans Plans and history
-
QDB Tag View Filter Scope — Step 2: Feature Description
QDB quote eligibility must not narrow shared tag pages.
docs/plans/qdb_tag_view_filter_scope/qdb_tag_view_filter_scope_step2_feature_description.md Plans Plans and history
-
QDB Tag View Filter Scope — Step 3: Development Plan
docs/plans/qdb_tag_view_filter_scope/qdb_tag_view_filter_scope_step3_development_plan.md Plans Plans and history
-
QDB Tag View Filter Scope — Step 4: Implementation Summary
docs/plans/qdb_tag_view_filter_scope/qdb_tag_view_filter_scope_step4_implementation_summary.md Plans Plans and history
-
QDB Theme Fidelity Checklist
Working checklist, not a committed FDP artifact.
docs/plans/qdb_theme_fidelity_checklist.md Plans Plans and history
-
QDB Vote Caption Sets — Step 1: Solution Assessment
If we review the backed-up QDB database in ~/qdbdatabase, we'll find that
docs/plans/qdb_vote_caption_sets/qdb_vote_caption_sets_step1_solution_assessment.md Plans Plans and history
-
QDB Vote Caption Sets — Step 2: Feature Description
QDB's +/- controls write generic tags and omit the archive's per-page
docs/plans/qdb_vote_caption_sets/qdb_vote_caption_sets_step2_feature_description.md Plans Plans and history
-
QDB Vote Caption Sets — Step 3: Development Plan
permalink and presses a displayed caption vote.
docs/plans/qdb_vote_caption_sets/qdb_vote_caption_sets_step3_development_plan.md Plans Plans and history
-
QDB Vote Caption Sets — Step 4: Implementation Summary
read model, with an optional deployment path override.
docs/plans/qdb_vote_caption_sets/qdb_vote_caption_sets_step4_implementation_summary.md Plans Plans and history
-
QR theme — Railspike debug log
Mode source: Host-root .railspikedebugon file present at new-cycle entry.
docs/plans/qr_theme/qr_theme_debug_log.md Plans Plans and history
-
qr_theme_step1_solution_assessment.md
Effort study: railspike-effort / v3/qrtheme; standing P2 enrollment; ledger
docs/plans/qr_theme/qr_theme_step1_solution_assessment.md Plans Plans and history
-
qr_theme_step2_feature_description.md
Effort study: railspike-effort / v3/qrtheme; standing P2 enrollment; ledger
docs/plans/qr_theme/qr_theme_step2_feature_description.md Plans Plans and history
-
qr_theme_step3_development_plan.md
Effort study: railspike-effort / v3/qrtheme; standing P2 enrollment; ledger
docs/plans/qr_theme/qr_theme_step3_development_plan.md Plans Plans and history
-
qr_theme_step4_implementation_summary.md
Effort study: railspike-effort / v3/qrtheme; standing P2 enrollment; ledger
docs/plans/qr_theme/qr_theme_step4_implementation_summary.md Plans Plans and history
-
Railspike Workflow Reading — Debug Log
No supported findings.
docs/plans/railspike_workflow_reading_debug_log.md Plans Plans and history
-
railspike_workflow_reading_step1_solution_assessment.md
Effort study: railspike-effort / v3/railspikeworkflowreading, standing P2 enrollment; split follow-up to v3/railspikeworkflowvisibility.
docs/plans/railspike_workflow_reading_step1_solution_assessment.md Plans Plans and history
-
Railspike Workflow Visibility — Debug Log
No supported findings.
docs/plans/railspike_workflow_visibility/railspike_workflow_visibility_debug_log.md Plans Plans and history
-
railspike_workflow_visibility_step1_solution_assessment.md
Effort study: railspike-effort / v3/railspikeworkflowvisibility, standing enrollment under P2.
docs/plans/railspike_workflow_visibility/railspike_workflow_visibility_step1_solution_assessment.md Plans Plans and history
-
railspike_workflow_visibility_step2_feature_description.md
Effort study: railspike-effort / v3/railspikeworkflowvisibility, scope v2, standing P2 enrollment.
docs/plans/railspike_workflow_visibility/railspike_workflow_visibility_step2_feature_description.md Plans Plans and history
-
railspike_workflow_visibility_step3_development_plan.md
Effort study: railspike-effort / v3/railspikeworkflowvisibility, scope v2, P2 ledger.
docs/plans/railspike_workflow_visibility/railspike_workflow_visibility_step3_development_plan.md Plans Plans and history
-
railspike_workflow_visibility_step4_implementation_summary.md
Effort study: railspike-effort / v3/railspikeworkflowvisibility, scope v2, P2 ledger.
docs/plans/railspike_workflow_visibility/railspike_workflow_visibility_step4_implementation_summary.md Plans Plans and history
-
Feature Plans
This directory holds planning artifacts for current and recently completed work.
docs/plans/README.md Plans Plans and history
-
Step 1: Read-Model Failure Experience — Solution Assessment
When an outdated read-model SQLite cache lacks threads.votecount, the site labels the failure as PHP host misconfiguration and exposes its raw SQL exception in…
docs/plans/read_model_failure_experience/read_model_failure_experience_step1_solution_assessment.md Plans Plans and history
-
Step 2: Read-Model Failure Experience — Feature Description
An obsolete read-model cache can expose raw SQL as a PHP configuration error.
docs/plans/read_model_failure_experience/read_model_failure_experience_step2_feature_description.md Plans Plans and history
-
Step 3: Read-Model Failure Experience — Development Plan
docs/plans/read_model_failure_experience/read_model_failure_experience_step3_development_plan.md Plans Plans and history
-
Step 4: Read-Model Failure Experience — Implementation Summary
docs/plans/read_model_failure_experience/read_model_failure_experience_step4_implementation_summary.md Plans Plans and history
-
read_model_hot_indexes — Railspike debug log
Revision of the 2026-10-24 Step 3 entry above (does not supersede its findings; adds the extended-mode observation).
docs/plans/read_model_hot_indexes/read_model_hot_indexes_debug_log.md Plans Plans and history
-
read_model_hot_indexes_step1_solution_assessment.md
Effort study: railspike-effort / v3/readmodelhotindexes; ledger, standing enrollment P2.
docs/plans/read_model_hot_indexes/read_model_hot_indexes_step1_solution_assessment.md Plans Plans and history
-
read_model_hot_indexes_step2_feature_description.md
Effort study: railspike-effort / v3/readmodelhotindexes; ledger, standing enrollment P2.
docs/plans/read_model_hot_indexes/read_model_hot_indexes_step2_feature_description.md Plans Plans and history
-
read_model_hot_indexes_step3_development_plan.md
Effort study: railspike-effort / v3/readmodelhotindexes; ledger, standing enrollment P2.
docs/plans/read_model_hot_indexes/read_model_hot_indexes_step3_development_plan.md Plans Plans and history
-
Step 4 — Implementation Summary
Effort study: railspike-effort / v3/readmodelhotindexes; ledger, standing enrollment P2.
docs/plans/read_model_hot_indexes/read_model_hot_indexes_step4_implementation_summary.md Plans Plans and history
-
read_model_schema_version_integrity_step1_solution_assessment.md
This has not been the case in the past.
docs/plans/read_model_schema_version_integrity/read_model_schema_version_integrity_step1_solution_assessment.md Plans Plans and history
-
read_model_schema_version_integrity_step2_feature_description.md
Read-model schema freshness relies on a manually incremented version number.
docs/plans/read_model_schema_version_integrity/read_model_schema_version_integrity_step2_feature_description.md Plans Plans and history
-
read_model_schema_version_integrity_step3_development_plan.md
Waiting for "Approved Step 3" before creating the feature branch or beginning implementation.
docs/plans/read_model_schema_version_integrity/read_model_schema_version_integrity_step3_development_plan.md Plans Plans and history