zenmemes Platform Docs

Docs home

Documents

2,188 documents

Filters
  1. docs_landing_step2_feature_description.md

    Follow-up cycle: predecessor docsdiscovery; intended reused branch feature/docs-discovery (unmerged).

    docs/plans/docs_landing/docs_landing_step2_feature_description.md Plans

  2. docs_landing_step3_development_plan.md

    Follow-up cycle: predecessor docsdiscovery; reused branch feature/docs-discovery (unmerged).

    docs/plans/docs_landing/docs_landing_step3_development_plan.md Plans

  3. docs_landing_step4_implementation_summary.md

    Follow-up cycle: predecessor docsdiscovery; reused branch feature/docs-discovery (unmerged).

    docs/plans/docs_landing/docs_landing_step4_implementation_summary.md Plans

  4. Documentation publication policy — Railspike debug log

    Verification: source and existing requirements reviewed; R1 hashes matched; planning changes only.

    docs/plans/docs_publication_policy/docs_publication_policy_debug_log.md Plans

  5. docs_publication_policy_step1_solution_assessment.md

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

    docs/plans/docs_publication_policy/docs_publication_policy_step1_solution_assessment.md Plans

  6. docs_publication_policy_step2_feature_description.md

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

    docs/plans/docs_publication_policy/docs_publication_policy_step2_feature_description.md Plans

  7. docs_publication_policy_step3_development_plan.md

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

    docs/plans/docs_publication_policy/docs_publication_policy_step3_development_plan.md Plans

  8. docs_publication_policy_step4_implementation_summary.md

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

    docs/plans/docs_publication_policy/docs_publication_policy_step4_implementation_summary.md Plans

  9. docs_publication_policy_verification.json

    docs/plans/docs_publication_policy/docs_publication_policy_verification.json Plans

  10. Effort estimation trial ledger

    2026-11-07T14:32:27Z — v3/glosstheme Step 4 local closeout: branch feat/engagifytheme, planning b1551c6a6 and eight stage commits.

    docs/plans/effort_estimation_trial.md Plans

  11. Effort estimation trial debug log

    No supported findings.

    docs/plans/effort_estimation_trial/effort_estimation_trial_debug_log.md Plans

  12. Prospective effort estimation trial — solution assessment

    Can you please write a Step 1 plan, using the Step 2 plan as point to reverse from

    docs/plans/effort_estimation_trial/effort_estimation_trial_step1_solution_assessment.md Plans

  13. Prospective effort estimation trial

    The calibration study proposes retrospective reference scores, but v3 needs prospective evidence of whether those scores help scope work comfortably into Rails…

    docs/plans/effort_estimation_trial/effort_estimation_trial_step2_feature_description.md Plans

  14. Effort estimation trial — development plan

    Deliver documentation-only setup for the maintainer and future agents: a resumable ledger, six useful proposed scopes with preserved estimates, and vendored Ra…

    docs/plans/effort_estimation_trial/effort_estimation_trial_step3_development_plan.md Plans

  15. Effort estimation trial — implementation summary

    Step 3 explicitly approved by the user.

    docs/plans/effort_estimation_trial/effort_estimation_trial_step4_implementation_summary.md Plans

  16. Effort estimation study — your checklist

    Current position: setup is complete on feat/effort-estimation-trial.

    docs/plans/effort_estimation_trial_maintainer_checklist.md Plans

  17. engagify_theme debug log

    No supported findings.

    docs/plans/engagify_theme/engagify_theme_debug_log.md Plans

  18. engagify_theme_step1_solution_assessment.md

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

    docs/plans/engagify_theme/engagify_theme_step1_solution_assessment.md Plans

  19. engagify_theme_step2_feature_description.md

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

    docs/plans/engagify_theme/engagify_theme_step2_feature_description.md Plans

  20. engagify_theme_step3_development_plan.md

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

    docs/plans/engagify_theme/engagify_theme_step3_development_plan.md Plans

  21. engagify_theme_step4_implementation_summary.md

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

    docs/plans/engagify_theme/engagify_theme_step4_implementation_summary.md Plans

  22. Ephemeral Testing: Candidate Targets

    Source: todo.txt item "identify targets for ephemeral testing", which references

    docs/plans/ephemeral_testing_targets.md Plans

  23. Ephemeral Testing: Task Descriptions and Agent Prompts

    Companion to ephemeraltestingtargets.md.

    docs/plans/ephemeral_testing_tasks.md Plans

  24. event_feature_gating_step1_solution_assessment.md

    We recently added an event feature, and it seems to now be available on all sites, which was not the original intent.

    docs/plans/event_feature_gating/event_feature_gating_step1_solution_assessment.md Plans

  25. event_feature_gating_step2_feature_description.md

    The shared thread composer and shared thread rendering currently expose event support on every site.

    docs/plans/event_feature_gating/event_feature_gating_step2_feature_description.md Plans

  26. event_feature_gating_step3_development_plan.md

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

    docs/plans/event_feature_gating/event_feature_gating_step3_development_plan.md Plans

  27. event_feature_gating_step4_implementation_summary.md

    docs/plans/event_feature_gating/event_feature_gating_step4_implementation_summary.md Plans

  28. event_time_step1_solution_assessment.md

    Please add event time and duration to the event framework.

    docs/plans/event_time/event_time_step1_solution_assessment.md Plans

  29. event_time_step2_feature_description.md

    An event thread can only carry a date, location, and link — never a start time — and the compose form's date field is a plain text box with no native picker, s…

    docs/plans/event_time/event_time_step2_feature_description.md Plans

  30. event_time_step3_development_plan.md

    2026-11-14 at 19:00); renders exactly as today when absent.

    docs/plans/event_time/event_time_step3_development_plan.md Plans

  31. event_time_step4_implementation_summary.md

    2026-11-20 at 19:30 · MIT Media Lab, E14 · https://example.com/cypher-night-2, confirming the time renders correctly on both surfaces (closing the two-surfaces…

    docs/plans/event_time/event_time_step4_implementation_summary.md Plans

  32. Extension/Improvement Cookbook Step 1 Solution Assessment

    Developers cannot readily see how the site’s existing architecture supports safe, practical feature extensions, especially LLM- and agent-assisted workflows.

    docs/plans/extension_improvement_cookbook/extension_improvement_cookbook_step1_solution_assessment.md Plans

  33. Extension/Improvement Cookbook Step 2 Feature Description

    The site’s extension facilities are capable but not discoverable through concrete examples.

    docs/plans/extension_improvement_cookbook/extension_improvement_cookbook_step2_feature_description.md Plans

  34. Extension/Improvement Cookbook Step 3 Development Plan

    docs/plans/extension_improvement_cookbook/extension_improvement_cookbook_step3_development_plan.md Plans

  35. Extension/Improvement Cookbook Step 4 Implementation Summary

    docs/plans/extension_improvement_cookbook/extension_improvement_cookbook_step4_implementation_summary.md Plans

  36. Fastmod Audit and Backfill Step 1 Solution Assessment

    Operators need to measure unscored historical content and its estimated Fastmod

    docs/plans/fastmod_audit_backfill/fastmod_audit_backfill_step1_solution_assessment.md Plans

  37. Fastmod Audit and Backfill Step 2 Feature Description

    Fastmod intentionally rates only newly published content, so operators cannot

    docs/plans/fastmod_audit_backfill/fastmod_audit_backfill_step2_feature_description.md Plans

  38. Fastmod Audit and Backfill Step 3 Development Plan

    If this plan is accepted, reply Approved Step 3.

    docs/plans/fastmod_audit_backfill/fastmod_audit_backfill_step3_development_plan.md Plans

  39. Fastmod Audit and Backfill Step 4 Implementation Summary

    configured model, usage-based estimate, and an explicit no-write result.

    docs/plans/fastmod_audit_backfill/fastmod_audit_backfill_step4_implementation_summary.md Plans

  40. Fastmod meta score — Railspike debug log

    No supported findings.

    docs/plans/fastmod_meta_score/fastmod_meta_score_debug_log.md Plans