-
Scripture Response Guidance and Expansion Step 2 Feature Description
Readers need complete scripture responses shaped by the question, with optional expansion for further depth.
docs/plans/agent_reply_length/agent_reply_length_step2_feature_description.md Plans Plans and history
-
Scripture Response Guidance and Expansion Step 3 Development Plan
docs/plans/agent_reply_length/agent_reply_length_step3_development_plan.md Plans Plans and history
-
Scripture Response Guidance and Expansion Implementation Summary
docs/plans/agent_reply_length/agent_reply_length_step4_implementation_summary.md Plans Plans and history
-
Agent Reply Manual Trigger and Cron Plan
Let operators intentionally trigger a reply-agent response for a specific post,
docs/plans/agent_reply_manual_trigger_and_cron_plan_v1.md Plans Plans and history
-
Agent Reply One-Step Analyze/Publish Plan
Make automatic agent reply publishing happen inside POST /api/analyzepost, while keeping POST /api/generateagentreply as an idempotent compatibility and manual…
docs/plans/agent_reply_one_step_analyze_publish_plan_v1.md Plans Plans and history
-
Agent Reply Task Queue Merge Step 1 Solution Assessment
As an operator, I want the agent reply queue and general purpose queue to be merged into the general purpose queue.
docs/plans/agent_reply_task_queue_merge/agent_reply_task_queue_merge_step1_solution_assessment.md Plans Plans and history
-
Agent Reply Task Queue Merge Step 2 Feature Description
Agent replies and maintenance work currently use separate queues, workers, locks, cron entries, and operational status paths.
docs/plans/agent_reply_task_queue_merge/agent_reply_task_queue_merge_step2_feature_description.md Plans Plans and history
-
Agent Reply Task Queue Merge Step 3 Development Plan
docs/plans/agent_reply_task_queue_merge/agent_reply_task_queue_merge_step3_development_plan.md Plans Plans and history
-
Agent Reply Task Queue Merge Step 4 Implementation Summary
docs/plans/agent_reply_task_queue_merge/agent_reply_task_queue_merge_step4_implementation_summary.md Plans Plans and history
-
Agent Response Direct Preflight Step 1 Solution Assessment
I agree with this, can it be a one-shot, or should we do docs/fdp/FEATUREDEVELOPMENTPROCESS.md again?
docs/plans/agent_response_direct_preflight/agent_response_direct_preflight_step1_solution_assessment.md Plans Plans and history
-
Agent Response Direct Preflight Step 2 Feature Description
Requested response modes currently wait for full model-backed post analysis even though the resulting legacy suggested reply is not used.
docs/plans/agent_response_direct_preflight/agent_response_direct_preflight_step2_feature_description.md Plans Plans and history
-
Agent Response Direct Preflight Step 3 Development Plan
docs/plans/agent_response_direct_preflight/agent_response_direct_preflight_step3_development_plan.md Plans Plans and history
-
Agent Response Direct Preflight Step 4 Implementation Summary
docs/plans/agent_response_direct_preflight/agent_response_direct_preflight_step4_implementation_summary.md Plans Plans and history
-
Agent Response Dropdown Viewport Fit – Solution Assessment
The request agent response dropdown does not always fully display in-page.
docs/plans/agent_response_dropdown_viewport_fit/agent_response_dropdown_viewport_fit_step1_solution_assessment.md Plans Plans and history
-
Agent Response Dropdown Viewport Fit – Feature Description
The mode menu opened from the "request agent reply" button is placed once on open, so it can be clipped by the viewport and does not stay attached to its butto…
docs/plans/agent_response_dropdown_viewport_fit/agent_response_dropdown_viewport_fit_step2_feature_description.md Plans Plans and history
-
Agent Response Dropdown Viewport Fit – Development Plan
docs/plans/agent_response_dropdown_viewport_fit/agent_response_dropdown_viewport_fit_step3_development_plan.md Plans Plans and history
-
Agent Response Dropdown Viewport Fit – Implementation Summary
docs/plans/agent_response_dropdown_viewport_fit/agent_response_dropdown_viewport_fit_step4_implementation_summary.md Plans Plans and history
-
Agent Response Harness Simplification Step 1 Solution Assessment
Please write Step 1 of docs/fdp/FEATUREDEVELOPMENTPROCESS.md for simplifying the agent response harness in preparation for the response type selector.
docs/plans/agent_response_harness_simplification/agent_response_harness_simplification_step1_solution_assessment.md Plans Plans and history
-
Agent Response Harness Simplification Step 2 Feature Description
Requested agent replies are currently extracted from a broad structured analysis, rather than generated as focused response tasks.
docs/plans/agent_response_harness_simplification/agent_response_harness_simplification_step2_feature_description.md Plans Plans and history
-
Agent Response Harness Simplification Step 3 Development Plan
docs/plans/agent_response_harness_simplification/agent_response_harness_simplification_step3_development_plan.md Plans Plans and history
-
Agent Response Harness Simplification Step 4 Implementation Summary
docs/plans/agent_response_harness_simplification/agent_response_harness_simplification_step4_implementation_summary.md Plans Plans and history
-
Agent Response Modes Step 1 Solution Assessment
The "Request agent response" button is really vague about what it does.
docs/plans/agent_response_modes/agent_response_modes_step1_solution_assessment.md Plans Plans and history
-
Agent Response Modes Step 2 Feature Description
“Request agent response” gives readers no meaningful indication of the response they will receive.
docs/plans/agent_response_modes/agent_response_modes_step2_feature_description.md Plans Plans and history
-
Agent Response Modes Step 3 Development Plan
docs/plans/agent_response_modes/agent_response_modes_step3_development_plan.md Plans Plans and history
-
Agent Response Modes Step 4 Implementation Summary
docs/plans/agent_response_modes/agent_response_modes_step4_implementation_summary.md Plans Plans and history
-
Anonymous Reaction Scoring — Step 1: Solution Assessment
Reactions (like/flag, and now upvote/downvote) always write a canonical
docs/plans/anonymous_reaction_scoring/anonymous_reaction_scoring_step1_solution_assessment.md Plans Plans and history
-
Anonymous Reply Vouching Options Plan
Let approved users vouch for anonymous replies without pretending that the
docs/plans/anonymous_reply_vouching_options_plan_v1.md Plans Plans and history
-
approval_seed_immediate_refresh_step1_solution_assessment.md
I've been told that ./v3 approve or ./v3 approval seed requires a complete rebuild.
docs/plans/approval_seed_immediate_refresh/approval_seed_immediate_refresh_step1_solution_assessment.md Plans Plans and history
-
approval_seed_immediate_refresh_step2_feature_description.md
./v3 approve and ./v3 approval seed currently require a full read-model rebuild before reporting success.
docs/plans/approval_seed_immediate_refresh/approval_seed_immediate_refresh_step2_feature_description.md Plans Plans and history
-
approval_seed_immediate_refresh_step3_development_plan.md
Every stage requires verification, summary update, and a commit before its successor.
docs/plans/approval_seed_immediate_refresh/approval_seed_immediate_refresh_step3_development_plan.md Plans Plans and history
-
approval_seed_immediate_refresh_step4_implementation_summary.md
docs/plans/approval_seed_immediate_refresh/approval_seed_immediate_refresh_step4_implementation_summary.md Plans Plans and history
-
Activity Commit File Manifest — Step 1: Solution Assessment
Classic Activity and Forte Activity show only the activity record's source file, even when its commit atomically changes additional canonical files, and do not…
docs/plans/archive/activity_commit_file_manifest_step1_solution_assessment.md Plans Plans and history
-
Activity Commit File Manifest — Step 2: Feature Description
An activity event represents one record, but its commit can change several files.
docs/plans/archive/activity_commit_file_manifest_step2_feature_description.md Plans Plans and history
-
Activity Commit File Manifest — Step 3: Development Plan
Reply Approved Step 3 to begin implementation on a feature branch.
docs/plans/archive/activity_commit_file_manifest_step3_development_plan.md Plans Plans and history
-
Activity Commit File Manifest — Step 4: Implementation Summary
docs/plans/archive/activity_commit_file_manifest_step4_implementation_summary.md Plans Plans and history
-
Activity Manifest Readability — Step 2: Feature Description
Activity cards repeat source/signature filenames above the commit manifest, and inline manifest paths are hard to scan.
docs/plans/archive/activity_manifest_readability_step2_feature_description.md Plans Plans and history
-
Activity Manifest Readability — Step 3: Development Plan
Reply Approved Step 3 to begin implementation on a feature branch.
docs/plans/archive/activity_manifest_readability_step3_development_plan.md Plans Plans and history
-
Activity Manifest Readability — Step 4: Implementation Summary
docs/plans/archive/activity_manifest_readability_step4_implementation_summary.md Plans Plans and history
-
Activity Source Links Slices Plan
Make the activity page source metadata actionable:
docs/plans/archive/activity_source_links_slices_v1.md Plans Plans and history
-
Agent Reply Request Button Step 1 Solution Assessment
Users need an intentional in-page control that requests a reply-agent response for a specific post without relying on automatic browser-triggered reply work.
docs/plans/archive/agent_reply_request_button_step1_solution_assessment.md Plans Plans and history