-
ZenMemes Rules Pinned Post Implementation Plan
The ZenMemes.com rules are saved in zenmemesrules.txt.
docs/plans/archive/zenmemes_rules_pinned_post_options.md Plans Plans and history
-
archive_export_contention_debug_log.md
Source: docs/railspike/docs/workflow/step1solutionassessment.md — compare alternatives and stop before Step 2.
docs/plans/archive_export_contention/archive_export_contention_debug_log.md Plans Plans and history
-
archive_export_contention_step1_solution_assessment.md
Effort study: railspike-effort / v3/archiveexportcontention; ledger; standing P2 enrollment
docs/plans/archive_export_contention/archive_export_contention_step1_solution_assessment.md Plans Plans and history
-
archive_export_contention_step2_feature_description.md
Effort study: railspike-effort / v3/archiveexportcontention; ledger; standing P2 enrollment
docs/plans/archive_export_contention/archive_export_contention_step2_feature_description.md Plans Plans and history
-
archive_export_contention_step3_development_plan.md
Effort study: railspike-effort / v3/archiveexportcontention; ledger; standing P2 enrollment
docs/plans/archive_export_contention/archive_export_contention_step3_development_plan.md Plans Plans and history
-
archive_export_contention_step4_implementation_summary.md
Effort study: railspike-effort / v3/archiveexportcontention; ledger
docs/plans/archive_export_contention/archive_export_contention_step4_implementation_summary.md Plans Plans and history
-
archive_export_efficiency — Railspike debug log
Created from a production incident on qdb.us: GET /downloads/repository.tar.gz
docs/plans/archive_export_efficiency/archive_export_efficiency_debug_log.md Plans Plans and history
-
archive_export_efficiency_step1_solution_assessment.md
Approval: APPROVED — user — 2026-10-26T01:21:01-04:00 — scope v1, recommended Option C (identity fix A sequenced first, then streaming build B); split to A-onl…
docs/plans/archive_export_efficiency/archive_export_efficiency_step1_solution_assessment.md Plans Plans and history
-
archive_export_efficiency_step2_feature_description.md
Approval: APPROVED — user — 2026-10-26T01:26:19-04:00 — scope v1 (explicit "Approved Step 2" in session)
docs/plans/archive_export_efficiency/archive_export_efficiency_step2_feature_description.md Plans Plans and history
-
archive_export_efficiency_step3_development_plan.md
Approval: APPROVED — user — 2026-10-26T02:29:54-04:00 — scope v1, full Option C (A+B, Stages 1–4) as written.
docs/plans/archive_export_efficiency/archive_export_efficiency_step3_development_plan.md Plans Plans and history
-
Step 4 — Implementation Summary
Approval: N/A — Step 4 is the implementation record; Steps 1–3 are APPROVED for scope v1 (full Option C).
docs/plans/archive_export_efficiency/archive_export_efficiency_step4_implementation_summary.md Plans Plans and history
-
attach_image_in_menu debug log
Debug mode: enabled (project marker .railspikedebugon).
docs/plans/attach_image_in_menu/attach_image_in_menu_debug_log.md Plans Plans and history
-
Attach image in the "…" menu: Step 1 solution assessment
We need to roll "choose an image" into the ...
docs/plans/attach_image_in_menu/attach_image_in_menu_step1_solution_assessment.md Plans Plans and history
-
Attach image in the "…" menu: Step 2 feature description
The image chooser is a standalone "Choose an image" button that adds weight to the compose form.
docs/plans/attach_image_in_menu/attach_image_in_menu_step2_feature_description.md Plans Plans and history
-
Attach image in the "…" menu: Step 3 development plan
docs/plans/attach_image_in_menu/attach_image_in_menu_step3_development_plan.md Plans Plans and history
-
Attach image in the "…" menu: Step 4 implementation summary
Branch: attachimageinmenu.
docs/plans/attach_image_in_menu/attach_image_in_menu_step4_implementation_summary.md Plans Plans and history
-
Authentication Modes Documentation — Railspike Debug Log
Assessment evidence is repository source and existing test inspection, not a runtime authentication audit.
docs/plans/authentication_modes_documentation/authentication_modes_documentation_debug_log.md Plans Plans and history
-
authentication_modes_documentation_step1_solution_assessment.md
Let's review our authentication modes and ensure documentation is up to date, please.
docs/plans/authentication_modes_documentation/authentication_modes_documentation_step1_solution_assessment.md Plans Plans and history
-
authentication_modes_documentation_step2_feature_description.md
Scattered authentication guidance conflates browser identity, session authentication, and membership approval.
docs/plans/authentication_modes_documentation/authentication_modes_documentation_step2_feature_description.md Plans Plans and history
-
authentication_modes_documentation_step3_development_plan.md
docs/plans/authentication_modes_documentation/authentication_modes_documentation_step3_development_plan.md Plans Plans and history
-
authentication_modes_documentation_step4_implementation_summary.md
The 15-method run used php tests/run.php with these Class::method filters:
docs/plans/authentication_modes_documentation/authentication_modes_documentation_step4_implementation_summary.md Plans Plans and history
-
automatic_guest_identity_step1_solution_assessment.md
As an operator, I want to have a feature flag available to me where instead of waiting for the user to begin an action before prompting for a username, the ser…
docs/plans/automatic_guest_identity/automatic_guest_identity_step1_solution_assessment.md Plans Plans and history
-
Automatic Guest Identity — Step 2: Feature Description
First-time visitors must begin a signed action and choose a username before a browser identity exists, delaying the interaction they intended to perform.
docs/plans/automatic_guest_identity/automatic_guest_identity_step2_feature_description.md Plans Plans and history
-
Automatic Guest Identity — Step 3: Development Plan
docs/plans/automatic_guest_identity/automatic_guest_identity_step3_development_plan.md Plans Plans and history
-
Automatic Guest Identity — Step 4: Implementation Summary
docs/plans/automatic_guest_identity/automatic_guest_identity_step4_implementation_summary.md Plans Plans and history
-
Account key approval policy FDP checklist
Status: Stage 1 enforcement implemented in the approved accountkeyapprovalsafety cycle.
docs/plans/backlog/account_key_approval_policy_fdp_checklist.md Plans Plans and history
-
Account key approval policy findings and recommendations
Status: First release narrowed to one feature flag.
docs/plans/backlog/account_key_approval_policy_findings_and_recommendations.md Plans Plans and history
-
Account key approval visibility and safety checklist
Status: Approved priorities 1–3 are implemented and locally release-verified.
docs/plans/backlog/account_key_approval_visibility_and_safety_checklist.md Plans Plans and history
-
Activity repository coverage checklist
Activity should report every change committed to the content repository, including files and record types it does not recognize.
docs/plans/backlog/activity_repository_coverage_checklist.md Plans Plans and history
-
Agent Reply Return Notification Step 1 Solution Assessment
Users need to know when an agent reply has returned without manually refreshing or rechecking the thread.
docs/plans/backlog/agent_reply_return_notification_step1_solution_assessment.md Plans Plans and history
-
Agent Response Pending Notice Visibility Step 1 Solution Assessment
When the agent response feature is activated on a post/comment that has a collapsed footer (consecutive posts by the same author), the notice about the respons…
docs/plans/backlog/agent_response_pending_notice_visibility_step1_solution_assessment.md Plans Plans and history
-
Agent Response Pending Notice Visibility Step 2 Feature Description
Same-author continuation styling collapses a post’s action footer, including the agent-response status.
docs/plans/backlog/agent_response_pending_notice_visibility_step2_feature_description.md Plans Plans and history
-
Agent Response Pending Notice Visibility Step 3 Development Plan
docs/plans/backlog/agent_response_pending_notice_visibility_step3_development_plan.md Plans Plans and history
-
Agent Response Pending Notice Visibility Step 4 Implementation Summary
docs/plans/backlog/agent_response_pending_notice_visibility_step4_implementation_summary.md Plans Plans and history
-
Approved Members Identity Publication: Debug Handoff
This document captures the current state of the approved-members-only feature and the remaining authentication/profile-access problem.
docs/plans/backlog/approved_members_identity_publication_debug_handoff.md Plans Plans and history
-
Approved User Server Pause Step 1 Solution Assessment
Approved users need a safe way to pause the server when something looks wrong, with backup access available during that workflow.
docs/plans/backlog/approved_user_server_pause_step1_solution_assessment.md Plans Plans and history
-
Classifier Optimization Step 1 Solution Assessment
The post classifier should be optimized for reliable, explainable safety and eligibility assessment now that agent task execution is a separate capability.
docs/plans/backlog/classifier_optimization_step1_solution_assessment.md Plans Plans and history
-
Clickable External Links Step 1 Solution Assessment
Users need pasted external links, including YouTube Shorts URLs, to become clickable in rendered posts.
docs/plans/backlog/clickable_external_links_step1_solution_assessment.md Plans Plans and history
-
Codex Handoff Draft Quality Step 1 Solution Assessment
Codex handoff drafts currently feel generic because the system uses a fixed deterministic template instead of adapting the user story, FDP Step 1 assessment, a…
docs/plans/backlog/codex_handoff_draft_quality_step1_solution_assessment.md Plans Plans and history
-
/docs/ Index Rewrite — Project-Verified Implementation Guide
docs/plans/backlog/docs_page_changes_revised.txt Plans Plans and history