zenmemes

New post

zenmemes Platform Docs

Docs home

Documents

2,569 documents

Filters
  1. Railspike Workflow Visibility — Debug Log

    No supported findings.

    docs/plans/railspike_workflow_visibility/railspike_workflow_visibility_debug_log.md Plans Plans and history

  2. railspike_workflow_visibility_step1_solution_assessment.md

    Effort study: railspike-effort / v3/railspikeworkflowvisibility, standing enrollment under P2.

    docs/plans/railspike_workflow_visibility/railspike_workflow_visibility_step1_solution_assessment.md Plans Plans and history

  3. railspike_workflow_visibility_step2_feature_description.md

    Effort study: railspike-effort / v3/railspikeworkflowvisibility, scope v2, standing P2 enrollment.

    docs/plans/railspike_workflow_visibility/railspike_workflow_visibility_step2_feature_description.md Plans Plans and history

  4. railspike_workflow_visibility_step3_development_plan.md

    Effort study: railspike-effort / v3/railspikeworkflowvisibility, scope v2, P2 ledger.

    docs/plans/railspike_workflow_visibility/railspike_workflow_visibility_step3_development_plan.md Plans Plans and history

  5. railspike_workflow_visibility_step4_implementation_summary.md

    Effort study: railspike-effort / v3/railspikeworkflowvisibility, scope v2, P2 ledger.

    docs/plans/railspike_workflow_visibility/railspike_workflow_visibility_step4_implementation_summary.md Plans Plans and history

  6. readable_page_urls debug log

    No supported findings.

    docs/plans/readable_page_urls/readable_page_urls_debug_log.md Plans Plans and history

  7. readable_page_urls_step1_solution_assessment.md

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

    docs/plans/readable_page_urls/readable_page_urls_step1_solution_assessment.md Plans Plans and history

  8. readable_page_urls_step2_feature_description.md

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

    docs/plans/readable_page_urls/readable_page_urls_step2_feature_description.md Plans Plans and history

  9. readable_page_urls_step3_development_plan.md

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

    docs/plans/readable_page_urls/readable_page_urls_step3_development_plan.md Plans Plans and history

  10. readable_page_urls_step4_implementation_summary.md

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

    docs/plans/readable_page_urls/readable_page_urls_step4_implementation_summary.md Plans Plans and history

  11. Feature Plans

    This directory holds planning artifacts for current and recently completed work.

    docs/plans/README.md Plans Plans and history

  12. Step 1: Read-Model Failure Experience — Solution Assessment

    When an outdated read-model SQLite cache lacks threads.votecount, the site labels the failure as PHP host misconfiguration and exposes its raw SQL exception in…

    docs/plans/read_model_failure_experience/read_model_failure_experience_step1_solution_assessment.md Plans Plans and history

  13. Step 2: Read-Model Failure Experience — Feature Description

    An obsolete read-model cache can expose raw SQL as a PHP configuration error.

    docs/plans/read_model_failure_experience/read_model_failure_experience_step2_feature_description.md Plans Plans and history

  14. Step 3: Read-Model Failure Experience — Development Plan

    docs/plans/read_model_failure_experience/read_model_failure_experience_step3_development_plan.md Plans Plans and history

  15. Step 4: Read-Model Failure Experience — Implementation Summary

    docs/plans/read_model_failure_experience/read_model_failure_experience_step4_implementation_summary.md Plans Plans and history

  16. read_model_hot_indexes — Railspike debug log

    Revision of the 2026-10-24 Step 3 entry above (does not supersede its findings; adds the extended-mode observation).

    docs/plans/read_model_hot_indexes/read_model_hot_indexes_debug_log.md Plans Plans and history

  17. read_model_hot_indexes_step1_solution_assessment.md

    Effort study: railspike-effort / v3/readmodelhotindexes; ledger, standing enrollment P2.

    docs/plans/read_model_hot_indexes/read_model_hot_indexes_step1_solution_assessment.md Plans Plans and history

  18. read_model_hot_indexes_step2_feature_description.md

    Effort study: railspike-effort / v3/readmodelhotindexes; ledger, standing enrollment P2.

    docs/plans/read_model_hot_indexes/read_model_hot_indexes_step2_feature_description.md Plans Plans and history

  19. read_model_hot_indexes_step3_development_plan.md

    Effort study: railspike-effort / v3/readmodelhotindexes; ledger, standing enrollment P2.

    docs/plans/read_model_hot_indexes/read_model_hot_indexes_step3_development_plan.md Plans Plans and history

  20. Step 4 — Implementation Summary

    Effort study: railspike-effort / v3/readmodelhotindexes; ledger, standing enrollment P2.

    docs/plans/read_model_hot_indexes/read_model_hot_indexes_step4_implementation_summary.md Plans Plans and history

  21. read_model_schema_version_integrity_step1_solution_assessment.md

    This has not been the case in the past.

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

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

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

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

  25. rebuild_memory_bound_debug_log.md

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

    docs/plans/rebuild_memory_bound_debug_log.md Plans Plans and history

  26. rebuild_memory_bound_step1_solution_assessment.md

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

    docs/plans/rebuild_memory_bound_step1_solution_assessment.md Plans Plans and history

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

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

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

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

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

  32. Recent activity — Railspike debug log

    Mode: enabled by the host-root .railspikedebugon file; extended estimates enabled under standing P2 enrollment.

    docs/plans/recent_activity/recent_activity_debug_log.md Plans Plans and history

  33. recent_activity_step1_solution_assessment.md

    Effort study: railspike-effort / v3/recentactivity; ledger, standing P2 enrollment

    docs/plans/recent_activity/recent_activity_step1_solution_assessment.md Plans Plans and history

  34. recent_activity_step2_feature_description.md

    Effort study: railspike-effort / v3/recentactivity; ledger, standing P2 enrollment

    docs/plans/recent_activity/recent_activity_step2_feature_description.md Plans Plans and history

  35. recent_activity_step3_development_plan.md

    Effort study: railspike-effort / v3/recentactivity; ledger, P2

    docs/plans/recent_activity/recent_activity_step3_development_plan.md Plans Plans and history

  36. recent_activity_step4_implementation_summary.md

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

    docs/plans/recent_activity/recent_activity_step4_implementation_summary.md Plans Plans and history

  37. Related Content Relevance Gate Plan v1

    Suggested relatedcontentassessment shape:

    docs/plans/related_content_relevance_gate_plan_v1.md Plans Plans and history

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

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

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