-
PHP Post And Comment Flagging Slices V1
This document outlines an implementation plan for letting approved users flag posts and comments, with automatic hiding for flagged reply-agent content.
docs/plans/php_post_comment_flagging_slices_v1.md Plans Plans and history
-
PHP Production Deployment Checklist V1
This document tracks the remaining work between the current implementation state and a responsible production deployment.
docs/plans/php_production_deployment_checklist_v1.md Plans Plans and history
-
PHP Reply Implementation Three-Slice Outline V1
This document outlines a clean three-slice plan for implementing replies in the PHP forum rewrite.
docs/plans/php_reply_implementation_three_slice_outline_v1.md Plans Plans and history
-
PHP Slice-Based Development Note V1
This project is being built in slices.
docs/plans/php_slice_based_development_note_v1.md Plans Plans and history
-
PHP Thread Labels After Creation Implementation Checklist V1
This document turns the retained proposal in docs/plans/phpthreadlabelsaftercreationproposalv1.md into a concrete implementation checklist for the current PHP…
docs/plans/php_thread_labels_after_creation_implementation_checklist_v1.md Plans Plans and history
-
PHP Thread Labels After Creation Proposal V1
This document proposes a retained design for adding labels to an existing thread after the thread has already been created.
docs/plans/php_thread_labels_after_creation_proposal_v1.md Plans Plans and history
-
PHP Unicode Authored Text Feature Flag Slices V1
This document outlines an atomic implementation plan for supporting readable non-Latin authored text, such as Cyrillic, while preserving inspector-friendly can…
docs/plans/php_unicode_authored_text_feature_flag_slices_v1.md Plans Plans and history
-
PHP Unicode Risk Detection Slices V1
This document outlines an atomic implementation plan for detecting suspicious or hard-to-inspect Unicode in authored content after Unicode prose support is int…
docs/plans/php_unicode_risk_detection_slices_v1.md Plans Plans and history
-
PHP User Approval Vouching Slices V1
This document outlines the implementation slices for adding operator-facing user approval through user-to-user vouching.
docs/plans/php_user_approval_vouching_slices_v1.md Plans Plans and history
-
PHP User Directory Page Slices V1
This document outlines the implementation slices for adding a user directory page to the PHP forum rewrite.
docs/plans/php_user_directory_page_slices_v1.md Plans Plans and history
-
Public Platform Docs — Step 1 Solution Assessment
The platform's architecture and extension guidance live in the repository but
docs/plans/platform_docs/platform_docs_step1_solution_assessment.md Plans Plans and history
-
Public Platform Docs — Step 2 Feature Description
Platform architecture and extension guidance are public in the repository but
docs/plans/platform_docs/platform_docs_step2_feature_description.md Plans Plans and history
-
Public Platform Docs — Step 3 Development Plan
promoted on the catalog.
docs/plans/platform_docs/platform_docs_step3_development_plan.md Plans Plans and history
-
Public Platform Docs — Step 4 Implementation Summary
only Markdown files beneath docs/ may resolve, paths cannot traverse out of
docs/plans/platform_docs/platform_docs_step4_implementation_summary.md Plans Plans and history
-
Post Card Standardization Plan v1
This plan standardizes thread/post display cards so the site stops duplicating similar markup across page templates.
docs/plans/post_card_standardization_plan_v1.md Plans Plans and history
-
post_markdown Railspike debug log
docs/plans/post_markdown/post_markdown_debug_log.md Plans Plans and history
-
post_markdown_step1_solution_assessment.md
Debug mode: enabled (.railspikedebugon present at the project root; new workflow)
docs/plans/post_markdown/post_markdown_step1_solution_assessment.md Plans Plans and history
-
post_markdown_step2_feature_description.md
Effort study: railspike-effort / v3/postmarkdown (ledger); standing enrollment P2
docs/plans/post_markdown/post_markdown_step2_feature_description.md Plans Plans and history
-
post_markdown_step3_development_plan.md
Effort study: railspike-effort / v3/postmarkdown (ledger); standing enrollment P2
docs/plans/post_markdown/post_markdown_step3_development_plan.md Plans Plans and history
-
post_markdown_step4_implementation_summary.md
Effort study: railspike-effort / v3/postmarkdown (ledger); standing enrollment P2
docs/plans/post_markdown/post_markdown_step4_implementation_summary.md Plans Plans and history
-
post_retraction_sweep_debug_log.md
Final stage commit: 8a1d73da.
docs/plans/post_retraction_sweep/post_retraction_sweep_debug_log.md Plans Plans and history
-
post_retraction_sweep_step1_solution_assessment.md
We have implemented basic post retraction, but the content still stays in multiple places.
docs/plans/post_retraction_sweep/post_retraction_sweep_step1_solution_assessment.md Plans Plans and history
-
post_retraction_sweep_step2_feature_description.md
Retraction hides content, but retained local payloads and interrupted artifact cleanup remain.
docs/plans/post_retraction_sweep/post_retraction_sweep_step2_feature_description.md Plans Plans and history
-
post_retraction_sweep_step3_development_plan.md
docs/plans/post_retraction_sweep/post_retraction_sweep_step3_development_plan.md Plans Plans and history
-
post_retraction_sweep_step4_implementation_summary.md
Planning commit: 6c6683f2.
docs/plans/post_retraction_sweep/post_retraction_sweep_step4_implementation_summary.md Plans Plans and history
-
Post Summary and Thread Context for Agent Replies Plan V1
Add a neutral one-sentence postsummary to stored post analysis, then use each thread comment's postsummary and full body text as context when deciding/generate…
docs/plans/post_summary_thread_context_agent_reply_plan_v1.md Plans Plans and history
-
preexisting_test_failures Railspike debug log
docs/plans/preexisting_test_failures/preexisting_test_failures_debug_log.md Plans Plans and history
-
preexisting_test_failures_one_shot.md
Cycle: v3/preexistingtestfailures; Mode: one-shot; Record/index: this file, plans index; related: fastdefaulttestsoutliers, parked fastdefaulttests Step 1
docs/plans/preexisting_test_failures/preexisting_test_failures_one_shot.md Plans Plans and history
-
prepared_thread_event_fields_step2_feature_description.md
The signed "Create thread" submit path (used by any identity-authenticated member, as opposed to "Create thread anonymously") silently drops eventdate/eventtim…
docs/plans/prepared_thread_event_fields/prepared_thread_event_fields_step2_feature_description.md Plans Plans and history
-
prepared_thread_event_fields_step3_development_plan.md
Waiting for "Approved Step 3" before branching and starting Step 4.
docs/plans/prepared_thread_event_fields/prepared_thread_event_fields_step3_development_plan.md Plans Plans and history
-
prepared_thread_event_fields_step4_implementation_summary.md
docs/plans/prepared_thread_event_fields/prepared_thread_event_fields_step4_implementation_summary.md Plans Plans and history
-
Private message chat refinement Step 1 solution assessment
Looks good, please merge into main and write Step 1 of the next one.
docs/plans/private_message_chat_refinement/private_message_chat_refinement_step1_solution_assessment.md Plans Plans and history
-
Private message chat refinement Step 2 feature description
Tall message cards and a large composer make conversations cumbersome.
docs/plans/private_message_chat_refinement/private_message_chat_refinement_step2_feature_description.md Plans Plans and history
-
Private message chat refinement Step 3 development plan
docs/plans/private_message_chat_refinement/private_message_chat_refinement_step3_development_plan.md Plans Plans and history
-
Private message chat refinement Step 4 implementation summary
docs/plans/private_message_chat_refinement/private_message_chat_refinement_step4_implementation_summary.md Plans Plans and history
-
Private Message Composite-User Composer: Step 1 Solution Assessment
We want private messages to be encrypted for every approved key in a composed profile, and we want the private message form to be available on the /user/xyz pa…
docs/plans/private_message_composite_user_composer/private_message_composite_user_composer_step1_solution_assessment.md Plans Plans and history
-
Private Message Composite-User Composer: Step 2 Feature Description
/user/<username> represents an approved composite user but does not offer the private-message form available from an individual approved profile.
docs/plans/private_message_composite_user_composer/private_message_composite_user_composer_step2_feature_description.md Plans Plans and history
-
Private Message Composite-User Composer: Step 3 Development Plan
docs/plans/private_message_composite_user_composer/private_message_composite_user_composer_step3_development_plan.md Plans Plans and history
-
Private Message Composite-User Composer: Step 4 Implementation Summary
docs/plans/private_message_composite_user_composer/private_message_composite_user_composer_step4_implementation_summary.md Plans Plans and history
-
Private Message Conversations: Step 1 Solution Assessment
Great job!
docs/plans/private_message_conversations/private_message_conversations_step1_solution_assessment.md Plans Plans and history