zenmemes Platform Docs

Documents

• Category: Plans ×
• Clear all

2,243 documents

Search unavailable. Retry or refresh the library.

1. reply_composer_focus_layout_step4_implementation_summary.md

   Effort study: railspike-effort / v3/replycomposerfocuslayout · Host ledger

   docs/plans/reply_composer_focus_layout/reply_composer_focus_layout_step4_implementation_summary.md Plans Plans and history

2. Reply continuation — Railspike diagnostics

   No supported findings.

   docs/plans/reply_continuation/reply_continuation_debug_log.md Plans Plans and history

3. reply_continuation_step1_solution_assessment.md

   Effort study: railspike-effort / v3/replycontinuation · P2 ledger.

   docs/plans/reply_continuation/reply_continuation_step1_solution_assessment.md Plans Plans and history

4. reply_continuation_step2_feature_description.md

   Effort study: railspike-effort / v3/replycontinuation · P2 ledger.

   docs/plans/reply_continuation/reply_continuation_step2_feature_description.md Plans Plans and history

5. reply_continuation_step3_development_plan.md

   Effort study: railspike-effort / v3/replycontinuation · P2 ledger.

   docs/plans/reply_continuation/reply_continuation_step3_development_plan.md Plans Plans and history

6. reply_continuation_step4_implementation_summary.md

   Effort study: railspike-effort / v3/replycontinuation · Ledger.

   docs/plans/reply_continuation/reply_continuation_step4_implementation_summary.md Plans Plans and history

7. Reply title directive — Railspike debug log

   Debug mode: enabled (project marker .railspikedebugon).

   docs/plans/reply_title_directive/reply_title_directive_debug_log.md Plans Plans and history

8. Reply title directive — Step 1: Solution Assessment

   Debug mode: enabled (project marker .railspikedebugon present at workflow start; snapshot 2026-11-03T05:19:48Z)

   docs/plans/reply_title_directive/reply_title_directive_step1_solution_assessment.md Plans Plans and history

9. Reply title directive — Step 2: Feature Description

   Effort study: railspike-effort / v3/replytitledirective — host ledger; standing enrollment under protocol P2

   docs/plans/reply_title_directive/reply_title_directive_step2_feature_description.md Plans Plans and history

10. Reply title directive — Step 3: Development Plan

    Effort study: railspike-effort / v3/replytitledirective — host ledger; standing enrollment under protocol P2

    docs/plans/reply_title_directive/reply_title_directive_step3_development_plan.md Plans Plans and history

11. Reply title directive — Step 4: Implementation Summary

    Effort study: railspike-effort / v3/replytitledirective — host ledger; standing enrollment under protocol P2

    docs/plans/reply_title_directive/reply_title_directive_step4_implementation_summary.md Plans Plans and history

12. Reply title live update — Railspike debug log

    Debug mode: enabled (project marker .railspikedebugon).

    docs/plans/reply_title_live_update/reply_title_live_update_debug_log.md Plans Plans and history

13. reply_title_live_update_one_shot.md

    Cycle: v3/replytitleliveupdate; Mode: one-shot; Record: this file; Index: plans index; Predecessor: v3/replytitledirective

    docs/plans/reply_title_live_update/reply_title_live_update_one_shot.md Plans Plans and history

14. repository_archive_readme_step1_solution_assessment.md

    Effort study: railspike-effort / v3/repositoryarchivereadme; host ledger.

    docs/plans/repository_archive_readme/repository_archive_readme_step1_solution_assessment.md Plans Plans and history

15. repository_archive_readme_step2_feature_description.md

    Effort study: railspike-effort / v3/repositoryarchivereadme; host ledger.

    docs/plans/repository_archive_readme/repository_archive_readme_step2_feature_description.md Plans Plans and history

16. repository_archive_readme_step3_development_plan.md

    Effort study: railspike-effort / v3/repositoryarchivereadme; ledger.

    docs/plans/repository_archive_readme/repository_archive_readme_step3_development_plan.md Plans Plans and history

17. repository_archive_readme_step4_implementation_summary.md

    Effort study: railspike-effort / v3/repositoryarchivereadme; ledger.

    docs/plans/repository_archive_readme/repository_archive_readme_step4_implementation_summary.md Plans Plans and history

18. History-free repository exports — one-shot implementation

    2026-10-24.

    docs/plans/repository_content_export_one_shot_summary.md Plans Plans and history

19. Repository Directory Cleanup — Railspike Debug Log

    Debug mode: enabled, inherited from Step 1 and the explicit user request.

    docs/plans/repository_directory_cleanup/repository_directory_cleanup_debug_log.md Plans Plans and history

20. repository_directory_cleanup_step1_solution_assessment.md

    I want to clean up the top-level directory for this project and possibly other second-level directories, so that the project looks neater on GitHub.

    docs/plans/repository_directory_cleanup/repository_directory_cleanup_step1_solution_assessment.md Plans Plans and history

21. repository_directory_cleanup_step2_feature_description.md

    Loose notes and reference documents obscure the project's structure on GitHub.

    docs/plans/repository_directory_cleanup/repository_directory_cleanup_step2_feature_description.md Plans Plans and history

22. repository_directory_cleanup_step3_development_plan.md

    docs/plans/repository_directory_cleanup/repository_directory_cleanup_step3_development_plan.md Plans Plans and history

23. repository_directory_cleanup_step4_implementation_summary.md

    docs/plans/repository_directory_cleanup/repository_directory_cleanup_step4_implementation_summary.md Plans Plans and history

24. repository_import_compatibility_debug_log.md

    Source: Step 1 option comparison, shared-contract reuse and normal-entry recovery.

    docs/plans/repository_import_compatibility_debug_log.md Plans Plans and history

25. repository_import_compatibility_step1_solution_assessment.md

    Effort study: railspike-effort / v3/repositoryimportcompatibility; P2 ledger

    docs/plans/repository_import_compatibility_step1_solution_assessment.md Plans Plans and history

26. request_path_cheap_wins — Railspike debug log

    Drafted Step 2 grounded in the three target files (FastmodMetaRead, FrontController/RouteServices, AssetFingerprint).

    docs/plans/request_path_cheap_wins/request_path_cheap_wins_debug_log.md Plans Plans and history

27. request_path_cheap_wins_step1_solution_assessment.md

    Approval: APPROVED — user — 2026-10-25T16:41:40-04:00 — scope v1 (explicit "Approved Step 1" in session)

    docs/plans/request_path_cheap_wins/request_path_cheap_wins_step1_solution_assessment.md Plans Plans and history

28. request_path_cheap_wins_step2_feature_description.md

    Approval: APPROVED — user — 2026-10-25T17:16:00-04:00 — scope v1 (explicit "Approved Step 2" in session)

    docs/plans/request_path_cheap_wins/request_path_cheap_wins_step2_feature_description.md Plans Plans and history

29. request_path_cheap_wins_step3_development_plan.md

    Approval: APPROVED — user — 2026-10-25T17:17:37-04:00 — scope v1 (explicit "Approved Step 3" in session)

    docs/plans/request_path_cheap_wins/request_path_cheap_wins_step3_development_plan.md Plans Plans and history

30. Step 4 — Implementation Summary

    Approval: N/A — Step 4 is the implementation record; Steps 1–3 are APPROVED for scope v1 (recorded in their documents).

    docs/plans/request_path_cheap_wins/request_path_cheap_wins_step4_implementation_summary.md Plans Plans and history

31. Restore invitation prompt diagnostics

    Necessary/useful instructions:

    docs/plans/restore_invitation_prompt/restore_invitation_prompt_debug_log.md Plans Plans and history

32. restore_invitation_prompt_step1_solution_assessment.md

    Effort study: railspike-effort / v3/restoreinvitationprompt; ledger

    docs/plans/restore_invitation_prompt/restore_invitation_prompt_step1_solution_assessment.md Plans Plans and history

33. restore_invitation_prompt_step2_feature_description.md

    Effort study: railspike-effort / v3/restoreinvitationprompt; ledger

    docs/plans/restore_invitation_prompt/restore_invitation_prompt_step2_feature_description.md Plans Plans and history

34. restore_invitation_prompt_step3_development_plan.md

    Effort study: railspike-effort / v3/restoreinvitationprompt; ledger

    docs/plans/restore_invitation_prompt/restore_invitation_prompt_step3_development_plan.md Plans Plans and history

35. restore_invitation_prompt_step4_implementation_summary.md

    Effort study: railspike-effort / v3/restoreinvitationprompt; ledger

    docs/plans/restore_invitation_prompt/restore_invitation_prompt_step4_implementation_summary.md Plans Plans and history

36. Railspike debug log: retracted_posts_hidden_from_listings

    Mode source: .railspikedebugon project marker (new workflow, no explicit request).

    docs/plans/retracted_posts_hidden_from_listings/retracted_posts_hidden_from_listings_debug_log.md Plans Plans and history

37. retracted_posts_hidden_from_listings_step1_solution_assessment.md

    When a post is deleted/retracted, it should no longer show up in listing pages.

    docs/plans/retracted_posts_hidden_from_listings/retracted_posts_hidden_from_listings_step1_solution_assessment.md Plans Plans and history

38. retracted_posts_hidden_from_listings_step2_feature_description.md

    Retracted threads and posts still appear in listing pages as placeholder rows.

    docs/plans/retracted_posts_hidden_from_listings/retracted_posts_hidden_from_listings_step2_feature_description.md Plans Plans and history

39. retracted_posts_hidden_from_listings_step3_development_plan.md

    docs/plans/retracted_posts_hidden_from_listings/retracted_posts_hidden_from_listings_step3_development_plan.md Plans Plans and history

40. retracted_posts_hidden_from_listings_step4_implementation_summary.md

    Branch: feat/retracted-posts-hidden-from-listings.

    docs/plans/retracted_posts_hidden_from_listings/retracted_posts_hidden_from_listings_step4_implementation_summary.md Plans Plans and history