zenmemes

New post

zenmemes Platform Docs

Docs home

Documents

2,188 documents

Filters
  1. Markdown renderer: pre-Step 3 evaluation

    Planning evidence, 2026-10-19.

    docs/plans/markdown_renderer_parser_evaluation.md Plans

  2. dynamic_browser_evidence.json

    docs/plans/markdown_task_lists/dynamic_browser_evidence.json Plans

  3. Markdown task lists — Railspike diagnostics

    Debug mode: enabled by the host root .railspikedebugon file presence; contents not read.

    docs/plans/markdown_task_lists/markdown_task_lists_debug_log.md Plans

  4. markdown_task_lists_metrics.json

    docs/plans/markdown_task_lists/markdown_task_lists_metrics.json Plans

  5. markdown_task_lists_step1_solution_assessment.md

    Please proceed.

    docs/plans/markdown_task_lists/markdown_task_lists_step1_solution_assessment.md Plans

  6. markdown_task_lists_step2_feature_description.md

    Literal task markers obscure checklist completion state.

    docs/plans/markdown_task_lists/markdown_task_lists_step2_feature_description.md Plans

  7. markdown_task_lists_step3_development_plan.md

    Ordinary Docs discovery/direct checklist URLs show named, immutable checked/unchecked state in PHP and copied full/shared releases.

    docs/plans/markdown_task_lists/markdown_task_lists_step3_development_plan.md Plans

  8. markdown_task_lists_step4_implementation_summary.md

    Debug mode: enabled, inherited from approved Step 3.

    docs/plans/markdown_task_lists/markdown_task_lists_step4_implementation_summary.md Plans

  9. release_recovery_evidence.json

    docs/plans/markdown_task_lists/release_recovery_evidence.json Plans

  10. render_current_summary.json

    docs/plans/markdown_task_lists/render_current_summary.json Plans

  11. render_frozen_summary.json

    docs/plans/markdown_task_lists/render_frozen_summary.json Plans

  12. static_browser_evidence.json

    docs/plans/markdown_task_lists/static_browser_evidence.json Plans

  13. static_discovery_evidence.json

    docs/plans/markdown_task_lists/static_discovery_evidence.json Plans

  14. static_verification_evidence.json

    docs/plans/markdown_task_lists/static_verification_evidence.json Plans

  15. task_contrast_verification.json

    docs/plans/markdown_task_lists/task_contrast_verification.json Plans

  16. task_corpus_classification.json

    docs/plans/markdown_task_lists/task_corpus_classification.json Plans

  17. Read-only task rendering acceptance

    This slice is verified locally on feature/markdown-task-lists.

    docs/plans/markdown_task_lists/task_render_acceptance.md Plans

  18. Markdown work checklist

    Updated 2026-10-23.

    docs/plans/markdown_work_checklist.md Plans

  19. Media embed support checklist

    Use this checklist to verify existing embeds, close URL coverage gaps, and add

    docs/plans/media_embed_support_checklist.md Plans

  20. Member directory / access split — Railspike debug log

    No supported findings.

    docs/plans/member_directory_access_split/member_directory_access_split_debug_log.md Plans

  21. member_directory_access_split_step1_solution_assessment.md

    The users page/subpages currently do two separate things: member directory and user/access management.

    docs/plans/member_directory_access_split/member_directory_access_split_step1_solution_assessment.md Plans

  22. member_directory_access_split_step2_feature_description.md

    Users mixes finding members and their contributions with reviewing account access.

    docs/plans/member_directory_access_split/member_directory_access_split_step2_feature_description.md Plans

  23. member_directory_access_split_step3_development_plan.md

    docs/plans/member_directory_access_split/member_directory_access_split_step3_development_plan.md Plans

  24. member_directory_access_split_step4_implementation_summary.md

    Standard member directory and Tools access management.

    docs/plans/member_directory_access_split/member_directory_access_split_step4_implementation_summary.md Plans

  25. Member-side mirroring: what it means and why it matters

    Written 2026-10-30.

    docs/plans/member_side_mirroring_proposal.md Plans

  26. merge_consecutive.txt

    docs/plans/merge_consecutive.txt Plans

  27. acceptance.txt

    docs/plans/message_sync_activity/acceptance.txt Plans

  28. message_sync_activity_compatibility_revision.md

    Status: Earlier proposal superseded; legacy upgrade-required restriction withdrawn from current recommendation, never approved

    docs/plans/message_sync_activity/message_sync_activity_compatibility_revision.md Plans

  29. message_sync_activity — debug log

    Verification: Restored repository principles, contribution/workflow and relevant concept guidance; verified frozen R1 hashes, checked local links and whitespac…

    docs/plans/message_sync_activity/message_sync_activity_debug_log.md Plans

  30. message_sync_activity_step1_solution_assessment.md

    Effort study: railspike-effort / v3/messagesyncactivity — ledger, standing P2 enrollment

    docs/plans/message_sync_activity/message_sync_activity_step1_solution_assessment.md Plans

  31. message_sync_activity_step2_feature_description.md

    Effort study: railspike-effort / v3/messagesyncactivity — ledger, standing P2 enrollment

    docs/plans/message_sync_activity/message_sync_activity_step2_feature_description.md Plans

  32. message_sync_activity_step3_development_plan.md

    Effort study: railspike-effort / v3/messagesyncactivity — ledger, standing P2 enrollment

    docs/plans/message_sync_activity/message_sync_activity_step3_development_plan.md Plans

  33. message_sync_activity_step4_implementation_summary.md

    Effort study: railspike-effort / v3/messagesyncactivity — ledger

    docs/plans/message_sync_activity/message_sync_activity_step4_implementation_summary.md Plans

  34. missing_php_startup_guidance_step1_solution_assessment.md

    I just tried to start v3 on a system without PHP installed, and it was not friendly:

    docs/plans/missing_php_startup_guidance/missing_php_startup_guidance_step1_solution_assessment.md Plans

  35. missing_php_startup_guidance_step2_feature_description.md

    Starting v3 without PHP currently produces a shell error with no recovery guidance.

    docs/plans/missing_php_startup_guidance/missing_php_startup_guidance_step2_feature_description.md Plans

  36. missing_php_startup_guidance_step3_development_plan.md

    docs/plans/missing_php_startup_guidance/missing_php_startup_guidance_step3_development_plan.md Plans

  37. missing_php_startup_guidance_step4_implementation_summary.md

    docs/plans/missing_php_startup_guidance/missing_php_startup_guidance_step4_implementation_summary.md Plans

  38. mitrapclub_about_copy_step1_solution_assessment.md

    Please write Step 1 of @docs/fdp/FEATUREDEVELOPMENTPROCESS.md for the next piece, which we'll move to a new chat.

    docs/plans/mitrapclub_about_copy/mitrapclub_about_copy_step1_solution_assessment.md Plans

  39. mitrapclub_about_copy_step2_feature_description.md

    The mitrapclub about page's intro sentence and three sections explaining identity/approval ("A continuous social graph," "How participation works") and backup/…

    docs/plans/mitrapclub_about_copy/mitrapclub_about_copy_step2_feature_description.md Plans

  40. mitrapclub_about_copy_step3_development_plan.md

    Waiting for "Approved Step 3" before branching and starting Step 4.

    docs/plans/mitrapclub_about_copy/mitrapclub_about_copy_step3_development_plan.md Plans