-
Initial comparison: no qualifying candidate
The faster configuration demonstrates a latency improvement, but neither revised candidate meets the approved quality gate.
docs/plans/scripture_response_quality/evaluation/report.md Plans Plans and history
-
results.json
docs/plans/scripture_response_quality/evaluation/results.json Plans Plans and history
-
Scripture Response Quality Railspike Debug Log
No supported findings for this revision.
docs/plans/scripture_response_quality/scripture_response_quality_debug_log.md Plans Plans and history
-
Scripture Response Quality and Latency Step 1 Solution Assessment
We've been iterating on this issue for a bit now.
docs/plans/scripture_response_quality/scripture_response_quality_step1_solution_assessment.md Plans Plans and history
-
Scripture Response Quality and Latency Step 2 Feature Description
Scripture replies can take nearly a minute yet overwhelm ordinary questions with repeated advice and loosely applied passages.
docs/plans/scripture_response_quality/scripture_response_quality_step2_feature_description.md Plans Plans and history
-
Scripture Response Quality and Latency Development Plan
docs/plans/scripture_response_quality/scripture_response_quality_step3_development_plan.md Plans Plans and history
-
Scripture Response Quality and Latency Implementation Summary
Planning commit: 075f91e7.
docs/plans/scripture_response_quality/scripture_response_quality_step4_implementation_summary.md Plans Plans and history
-
Scripture response reliability evaluation
The candidate does not qualify for release.
docs/plans/scripture_response_reliability/evaluation/report.md Plans Plans and history
-
results.json
docs/plans/scripture_response_reliability/evaluation/results.json Plans Plans and history
-
Scripture Response Reliability Railspike Debug Log
docs/plans/scripture_response_reliability/scripture_response_reliability_debug_log.md Plans Plans and history
-
Scripture Response Reliability — Solution Assessment
That would be a great answer.
docs/plans/scripture_response_reliability/scripture_response_reliability_step1_solution_assessment.md Plans Plans and history
-
Scripture Response Reliability — Feature Description
Existing scripture replies can miss the reader's decision and publish inaccurate quotations despite explicit instructions.
docs/plans/scripture_response_reliability/scripture_response_reliability_step2_feature_description.md Plans Plans and history
-
Scripture Response Reliability — Development Plan
docs/plans/scripture_response_reliability/scripture_response_reliability_step3_development_plan.md Plans Plans and history
-
Scripture Response Reliability — Implementation Summary
Status: Stages 1–6 completed; Stage 7 blocked by failed initial release gates.
docs/plans/scripture_response_reliability/scripture_response_reliability_step4_implementation_summary.md Plans Plans and history
-
Scripture reliability revision: regression stop
The repaired Sol writer passed five of six known regressions, but neither writer
docs/plans/scripture_response_reliability_revision/evaluation/report.md Plans Plans and history
-
results.json
docs/plans/scripture_response_reliability_revision/evaluation/results.json Plans Plans and history
-
Scripture Response Reliability Revision Railspike Debug Log
docs/plans/scripture_response_reliability_revision/scripture_response_reliability_revision_debug_log.md Plans Plans and history
-
Scripture Response Reliability Revision — Solution Assessment
Please go ahead.
docs/plans/scripture_response_reliability_revision/scripture_response_reliability_revision_step1_solution_assessment.md Plans Plans and history
-
Scripture Response Reliability Revision — Feature Description
The failed candidate verifies published quotations but rejects ordinary quoted language and misreads practical or pastoral concerns.
docs/plans/scripture_response_reliability_revision/scripture_response_reliability_revision_step2_feature_description.md Plans Plans and history
-
Scripture Response Reliability Revision — Development Plan
Deliver existing scripture request → complete reply → optional Expand → explicit recovery, using a scripture-only writer and verified quotations.
docs/plans/scripture_response_reliability_revision/scripture_response_reliability_revision_step3_development_plan.md Plans Plans and history
-
Scripture Response Reliability Revision — Step 3 Evaluation Protocol
This protocol is part of the Step 3 development plan and its approval scope.
docs/plans/scripture_response_reliability_revision/scripture_response_reliability_revision_step3_evaluation_protocol.md Plans Plans and history
-
Scripture Reliability Revision — Implementation Summary
Approval: user authorized the original Step 3 plan and linked protocol.
docs/plans/scripture_response_reliability_revision/scripture_response_reliability_revision_step4_implementation_summary.md Plans Plans and history
-
Server cooperative content deletion debug log
docs/plans/server_cooperative_content_deletion/server_cooperative_content_deletion_debug_log.md Plans Plans and history
-
Server Cooperative Content Deletion Step 1 Solution Assessment
Explore server-cooperative content deletion.
docs/plans/server_cooperative_content_deletion/server_cooperative_content_deletion_step1_solution_assessment.md Plans Plans and history
-
Server Cooperative Content Deletion Step 2 Feature Description
Authors cannot retract their own posts; only operators can remove records, and that leaves content in Git history with no author authority.
docs/plans/server_cooperative_content_deletion/server_cooperative_content_deletion_step2_feature_description.md Plans Plans and history
-
Server Cooperative Content Deletion Step 3 Development Plan
docs/plans/server_cooperative_content_deletion/server_cooperative_content_deletion_step3_development_plan.md Plans Plans and history
-
Server Cooperative Content Deletion Step 4 Implementation Summary
docs/plans/server_cooperative_content_deletion/server_cooperative_content_deletion_step4_implementation_summary.md Plans Plans and history
-
Session Reauthentication Reference
The original report concerned requests arriving after a PHP session record expired or was cleaned up, before browser JavaScript could restore authentication.
docs/plans/session_reauthentication_reference.md Plans Plans and history
-
Shared Navigation Icons (Word 97 + Chicago)
Branch: feature/shared-nav-icons.
docs/plans/shared_nav_icons_checklist.md Plans Plans and history
-
Signed thread label records debug log
Supersedes the prior Step 2 report’s online thread-only scope assessment.
docs/plans/signed_thread_label_records/signed_thread_label_records_debug_log.md Plans Plans and history
-
Signed Thread Label Records Step 1 Solution Assessment
I would like this, I kinda thought it was already the case.
docs/plans/signed_thread_label_records/signed_thread_label_records_step1_solution_assessment.md Plans Plans and history
-
Signed Thread Label Records Step 2 Feature Description
Thread labels and post reactions (including likes and flags) name an author without preserving that author's signature over the saved record.
docs/plans/signed_thread_label_records/signed_thread_label_records_step2_feature_description.md Plans Plans and history
-
signed_thread_label_records_step3_development_plan.md
Waiting for "Approved Step 3" before branching, organizing/committing plans, or implementation.
docs/plans/signed_thread_label_records/signed_thread_label_records_step3_development_plan.md Plans Plans and history
-
Signed labels and reactions implementation
Branch: feature/signed-thread-label-records.
docs/plans/signed_thread_label_records/signed_thread_label_records_step4_implementation_summary.md Plans Plans and history
-
site_favicons_step1_solution_assessment.md
Our default favicon is a letter Z, which is kind of appropriate for zenmemes, but very inappropriate for other sites.
docs/plans/site_favicons/site_favicons_step1_solution_assessment.md Plans Plans and history
-
site_favicons_step2_feature_description.md
chouse and qdb show the zenmemes "Z" favicon in browser tabs, bookmarks and the installed-app icon.
docs/plans/site_favicons/site_favicons_step2_feature_description.md Plans Plans and history
-
site_favicons_step3_development_plan.md
Waiting for "Approved Step 3" before starting Step 4.
docs/plans/site_favicons/site_favicons_step3_development_plan.md Plans Plans and history
-
site_favicons_step4_implementation_summary.md
docs/plans/site_favicons/site_favicons_step4_implementation_summary.md Plans Plans and history
-
Site Feature Flags Slices V1
This document outlines an atomic implementation plan for making site feature flags visible, auditable, and eventually mutable through the site while preserving…
docs/plans/site_feature_flags_slices_v1.md Plans Plans and history
-
site_operations_page Railspike debug log
docs/plans/site_operations_page/site_operations_page_debug_log.md Plans Plans and history