-
Step 1: Solution Assessment — Forte Activity Instant Loading
Forte Activity eagerly prepares every first-page record for five activity filters, including hidden detail panes and technical source metadata, so its initial…
docs/plans/backlog/forte_activity_instant_loading_step1_solution_assessment.md Plans Plans and history
-
Forte Activity Instant Loading — Step 2: Feature Description
Opening Forte Activity delays the first usable view because it eagerly prepares rows and technical details that are not yet visible.
docs/plans/backlog/forte_activity_instant_loading_step2_feature_description.md Plans Plans and history
-
Forte Activity Instant Loading — Step 3: Development Plan
Share this document for review — Approved Step 3 is required before Step 4.
docs/plans/backlog/forte_activity_instant_loading_step3_development_plan.md Plans Plans and history
-
Forte Activity Instant Loading — Step 4: Implementation Summary
docs/plans/backlog/forte_activity_instant_loading_step4_implementation_summary.md Plans Plans and history
-
Forte activity read-model compatibility and recovery plan
/forte/activity/ now renders a persisted Commits pane on every request.
docs/plans/backlog/forte_activity_read_model_compatibility_error_handling_plan.md Plans Plans and history
-
Gamification Leaderboard Step 1 Solution Assessment
Users want to explore gamification ideas such as leaderboards, node counts, and LLM-assessed funny points.
docs/plans/backlog/gamification_leaderboard_step1_solution_assessment.md Plans Plans and history
-
General-Purpose Agent Response Step 1 Solution Assessment
Approved users need to request useful task-specific agent responses, such as translating an entire referenced post by commenting an instruction and requesting…
docs/plans/backlog/general_purpose_agent_response_step1_solution_assessment.md Plans Plans and history
-
General-Purpose Agent Response Step 2 Feature Description
Agent responses currently rely on a classifier's conventional-reply suggestion rather than independently carrying out a user's task.
docs/plans/backlog/general_purpose_agent_response_step2_feature_description.md Plans Plans and history
-
Hide Numbers Focus Toggle Step 1 Solution Assessment
Users need an optional focus mode that hides counts, dates, likes, and similar numbers while preserving access for admins and power users.
docs/plans/backlog/hide_numbers_focus_toggle_step1_solution_assessment.md Plans Plans and history
-
Identity Rename Option Step 1 Solution Assessment
Users need a safe re-setup or change-name option that can create a public rename or link record and clarify approval implications.
docs/plans/backlog/identity_rename_option_step1_solution_assessment.md Plans Plans and history
-
Image Support Logistics Step 1 Solution Assessment
Users need image-support logistics clarified before the forum accepts or displays images.
docs/plans/backlog/image_support_logistics_step1_solution_assessment.md Plans Plans and history
-
Imported Feature Requests Implementation Routing Plan V1
docs/plans/backlog/imported_feature_requests_implementation_routing_plan_v1.txt Plans Plans and history
-
improve_messaging.txt
docs/plans/backlog/improve_messaging.txt Plans Plans and history
-
iPhone Database Web UI Step 1 Solution Assessment
iPhone users need a database web UI that works without desktop SQLite tools.
docs/plans/backlog/iphone_database_webui_step1_solution_assessment.md Plans Plans and history
-
Local Dev Begin Development FDP UI Step 1 Solution Assessment
Local development should offer a "Begin development" action beside agent-response controls, with UI for the four FDP stages.
docs/plans/backlog/local_dev_begin_development_fdp_ui_step1_solution_assessment.md Plans Plans and history
-
Love Button Reaction Step 1 Solution Assessment
Users want to consider adding a Love reaction alongside existing reaction controls.
docs/plans/backlog/love_button_reaction_step1_solution_assessment.md Plans Plans and history
-
New User Profile Creation Notice Step 1 Solution Assessment
New users need notice before posting that they may be asked to create or register a public profile.
docs/plans/backlog/new_user_profile_creation_notice_step1_solution_assessment.md Plans Plans and history
-
Extended Offline Parity Roadmap
Product direction and backlog.
docs/plans/backlog/offline_support_extended_roadmap.md Plans Plans and history
-
Offline Support Roadmap
This records product direction and sequencing; each
docs/plans/backlog/offline_support_roadmap.md Plans Plans and history
-
Page Asset Performance — Step 1: Solution Assessment
After theme splitting, standard pages still ship shared CSS, scripts, inline critical CSS, and static-artifact assets that may not serve their route; reduce tr…
docs/plans/backlog/page_asset_performance_step1_solution_assessment.md Plans Plans and history
-
PHP 5.6 and Subdirectory Hosting — Step 1 Solution Assessment
Make the application runnable from PHP 5.6 under a user-directory URL such as https://www.mit.edu/~igulko/, while preserving operation on modern PHP and, where…
docs/plans/backlog/php56_subdirectory_compatibility_step1_solution_assessment.md Plans Plans and history
-
Product Mention Links Step 1 Solution Assessment
Users want product mentions in posts to link to relevant product pages.
docs/plans/backlog/product_mention_links_step1_solution_assessment.md Plans Plans and history
-
qdb_todo.txt
docs/plans/backlog/qdb_todo.txt Plans Plans and history
-
Planning Backlog
This directory collects early-stage planning artifacts that have not yet been
docs/plans/backlog/README.md Plans Plans and history
-
Read-model maintenance follow-ups (from viewer_tag_read_model_and_memoization)
Two cross-cutting items surfaced during the viewertagreadmodelandmemoization
docs/plans/backlog/read_model_maintenance_followups.md Plans Plans and history
-
related_feature_requests.txt
docs/plans/backlog/related_feature_requests.txt Plans Plans and history
-
Second brain Railspike debug log
No supported findings.
docs/plans/backlog/second_brain_debug_log.md Plans Plans and history
-
second_brain_step1_solution_assessment.md
Please review secondbrain.txt and write an outline of features we have and don't have that would make this possible.
docs/plans/backlog/second_brain_step1_solution_assessment.md Plans Plans and history
-
Server cooperative content deletion discussion
Discussion date: 2026-10-10.
docs/plans/backlog/server_cooperative_content_deletion_discussion.md Plans Plans and history
-
Tools Page Mobile Clickability Step 1 Solution Assessment
iPhone users need the tools page to render correctly and expose clickable tool actions.
docs/plans/backlog/tools_page_mobile_clickability_step1_solution_assessment.md Plans Plans and history
-
Unapproved Agent Response Notice Step 1 Solution Assessment
Unapproved users need to understand why the agent response feature is unavailable instead of seeing the control silently hidden.
docs/plans/backlog/unapproved_agent_response_notice_step1_solution_assessment.md Plans Plans and history
-
Undo Accidental Flag Step 1 Solution Assessment
Users need a way to recover from accidentally flagging a post.
docs/plans/backlog/undo_accidental_flag_step1_solution_assessment.md Plans Plans and history
-
Usenet Forte Agent Interface Step 1 Solution Assessment
Users want to explore a Usenet/Forte Agent-like interface using the existing forum backend and frontend capabilities.
docs/plans/backlog/usenet_forte_agent_interface_step1_solution_assessment.md Plans Plans and history
-
V3 Approval Seed Shortcut Step 1 Solution Assessment
Operators need an easier CLI shortcut from ./v3 approve to the existing approval seed command.
docs/plans/backlog/v3_approval_seed_shortcut_step1_solution_assessment.md Plans Plans and history
-
v3_private_config_editor_step1_solution_assessment.md
Please write Step 1 of docs/fdp/FEATUREDEVELOPMENTPROCESS.md for the next step.
docs/plans/backlog/v3_private_config_editor_step1_solution_assessment.md Plans Plans and history
-
v3_private_config_editor_step2_feature_description.md
The read-only terminal dashboard exposes private-configuration state, but operators must still manually edit PHP to change an LLM connection safely.
docs/plans/backlog/v3_private_config_editor_step2_feature_description.md Plans Plans and history
-
v3_private_config_editor_step3_development_plan.md
docs/plans/backlog/v3_private_config_editor_step3_development_plan.md Plans Plans and history
-
v3_private_config_editor_step4_implementation_summary.md
docs/plans/backlog/v3_private_config_editor_step4_implementation_summary.md Plans Plans and history
-
V3 Start Port Shorthand Step 1 Solution Assessment
Developers need ./v3 start 8001 and ./v3 start :8001 to start the local server on that port without address errors.
docs/plans/backlog/v3_start_port_shorthand_step1_solution_assessment.md Plans Plans and history
-
v3_terminal_operator_ui_step1_solution_assessment.md
I saw this in our todo.txt:
docs/plans/backlog/v3_terminal_operator_ui_step1_solution_assessment.md Plans Plans and history