zenmemes

New post

zenmemes Platform Docs

Docs home

Documents

1,645 documents

Filters
  1. read_model_schema_version_integrity_step2_feature_description.md

    Read-model schema freshness relies on a manually incremented version number.

    docs/plans/read_model_schema_version_integrity/read_model_schema_version_integrity_step2_feature_description.md Plans Plans and history

  2. read_model_schema_version_integrity_step3_development_plan.md

    Waiting for "Approved Step 3" before creating the feature branch or beginning implementation.

    docs/plans/read_model_schema_version_integrity/read_model_schema_version_integrity_step3_development_plan.md Plans Plans and history

  3. read_model_schema_version_integrity_step4_implementation_summary.md

    docs/plans/read_model_schema_version_integrity/read_model_schema_version_integrity_step4_implementation_summary.md Plans Plans and history

  4. Rebuild thread-label stall — Railspike debug log

    Debug mode: enabled by the user's explicit request, recorded in the Step 1 artifact.

    docs/plans/rebuild_thread_label_stall/rebuild_thread_label_stall_debug_log.md Plans Plans and history

  5. rebuild_thread_label_stall_step1_solution_assessment.md

    On production, ./v3 rebuild appears to stall after this step:

    docs/plans/rebuild_thread_label_stall/rebuild_thread_label_stall_step1_solution_assessment.md Plans Plans and history

  6. rebuild_thread_label_stall_step2_feature_description.md

    ./v3 rebuild appears stalled when parsing reaches its total but silent indexing continues.

    docs/plans/rebuild_thread_label_stall/rebuild_thread_label_stall_step2_feature_description.md Plans Plans and history

  7. rebuild_thread_label_stall_step3_development_plan.md

    Normal ./v3 rebuild batches all three provenance families and reports work through validated promotion/snapshot readiness.

    docs/plans/rebuild_thread_label_stall/rebuild_thread_label_stall_step3_development_plan.md Plans Plans and history

  8. rebuild_thread_label_stall_step4_implementation_summary.md

    Planning commit: 686d8766.

    docs/plans/rebuild_thread_label_stall/rebuild_thread_label_stall_step4_implementation_summary.md Plans Plans and history

  9. Related Content Relevance Gate Plan v1

    Suggested relatedcontentassessment shape:

    docs/plans/related_content_relevance_gate_plan_v1.md Plans Plans and history

  10. rename_windark_to_midnight debug log

    Debug mode: enabled (project marker .railspikedebugon).

    docs/plans/rename_windark_to_midnight/rename_windark_to_midnight_debug_log.md Plans Plans and history

  11. Rename the windark theme to midnight: Step 1 solution assessment

    Is midnight theme still called windark internally?

    docs/plans/rename_windark_to_midnight/rename_windark_to_midnight_step1_solution_assessment.md Plans Plans and history

  12. Rename the windark theme to midnight: Step 2 feature description

    The theme labelled "Midnight" is still windark in code, files, selectors, tests and AGENTS.md.

    docs/plans/rename_windark_to_midnight/rename_windark_to_midnight_step2_feature_description.md Plans Plans and history

  13. Rename the windark theme to midnight: Step 3 development plan

    docs/plans/rename_windark_to_midnight/rename_windark_to_midnight_step3_development_plan.md Plans Plans and history

  14. Rename the windark theme to midnight: Step 4 implementation summary

    Branch: renamewindarktomidnight (from main).

    docs/plans/rename_windark_to_midnight/rename_windark_to_midnight_step4_implementation_summary.md Plans Plans and history

  15. Reply composer focus/layout — Railspike debug log

    No supported findings.

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

  16. reply_composer_focus_layout_step1_solution_assessment.md

    Can you please check the inline reply form for similar behavior, and it also for some reason features a floating post button that covers up the textarea...

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

  17. reply_composer_focus_layout_step2_feature_description.md

    Inline reply switches focus between two textareas, and the floating Post row can cover the editor.

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

  18. reply_composer_focus_layout_step3_development_plan.md

    From ordinary thread Reply or dedicated reply entry, submit exactly one reply or retain the draft with visible correction/retry.

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

  19. 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

  20. Reply continuation — Railspike diagnostics

    No supported findings.

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

  21. 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

  22. 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

  23. 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

  24. 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

  25. 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

  26. 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

  27. 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

  28. 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

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

    2026-10-24.

    docs/plans/repository_content_export_one_shot_summary.md Plans Plans and history

  30. 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

  31. 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

  32. 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

  33. repository_directory_cleanup_step3_development_plan.md

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

  34. repository_directory_cleanup_step4_implementation_summary.md

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

  35. 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

  36. 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

  37. 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

  38. 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

  39. 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

  40. 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