zenmemes Platform Docs

Docs home

Documents

1,737 documents

Filters
  1. docs_discovery_step2_feature_description.md

    Platform Docs exposes only a small curated list, leaving most repository documentation difficult to find.

    docs/plans/docs_discovery/docs_discovery_step2_feature_description.md Plans Plans and history

  2. docs_discovery_step3_development_plan.md

    Tools → Platform Docs must support finding all eligible docs, opening documents/assets and related links, and returning to preserved results on dynamic and sta…

    docs/plans/docs_discovery/docs_discovery_step3_development_plan.md Plans Plans and history

  3. docs_discovery_step4_implementation_summary.md

    All five stages completed on feature/docs-discovery; planning commit 00a1511a.

    docs/plans/docs_discovery/docs_discovery_step4_implementation_summary.md Plans Plans and history

  4. Independent documentation publication — Railspike debug log

    Verification: read current import/full/shared publication, static docs/search/download/asset selection, version checker/layout and deployment guidance.

    docs/plans/docs_independent_publication/docs_independent_publication_debug_log.md Plans Plans and history

  5. docs_independent_publication_step1_solution_assessment.md

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

    docs/plans/docs_independent_publication/docs_independent_publication_step1_solution_assessment.md Plans Plans and history

  6. docs_independent_publication_step2_feature_description.md

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

    docs/plans/docs_independent_publication/docs_independent_publication_step2_feature_description.md Plans Plans and history

  7. docs_independent_publication_step3_development_plan.md

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

    docs/plans/docs_independent_publication/docs_independent_publication_step3_development_plan.md Plans Plans and history

  8. docs_independent_publication_step4_implementation_summary.md

    Restored inherited state: Step 3 approval, planning and Stages 1–6 commits, enabled debug, R1/P2 study history and pending bookkeeping were reconciled before S…

    docs/plans/docs_independent_publication/docs_independent_publication_step4_implementation_summary.md Plans Plans and history

  9. stage1_boundary_evidence.json

    docs/plans/docs_independent_publication/stage1_boundary_evidence.json Plans Plans and history

  10. stage7_acceptance_evidence.json

    docs/plans/docs_independent_publication/stage7_acceptance_evidence.json Plans Plans and history

  11. docs_landing_contrast_audit.json

    docs/plans/docs_landing/docs_landing_contrast_audit.json Plans Plans and history

  12. docs_landing Railspike debug log

    docs/plans/docs_landing/docs_landing_debug_log.md Plans Plans and history

  13. docs_landing_rendered_contrast.json

    docs/plans/docs_landing/docs_landing_rendered_contrast.json Plans Plans and history

  14. docs_landing_step1_solution_assessment.md

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

    docs/plans/docs_landing/docs_landing_step1_solution_assessment.md Plans Plans and history

  15. 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 Plans and history

  16. 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 Plans and history

  17. 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 Plans and history

  18. 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 Plans and history

  19. 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 Plans and history

  20. 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 Plans and history

  21. 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 Plans and history

  22. 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 Plans and history

  23. docs_publication_policy_verification.json

    docs/plans/docs_publication_policy/docs_publication_policy_verification.json Plans Plans and history

  24. Effort estimation trial ledger

    2026-10-28 Step 4 local closeout: canonical entry/stages/outcome.

    docs/plans/effort_estimation_trial.md Plans Plans and history

  25. Effort estimation trial debug log

    No supported findings.

    docs/plans/effort_estimation_trial/effort_estimation_trial_debug_log.md Plans Plans and history

  26. 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 Plans and history

  27. 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 Plans and history

  28. 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 Plans and history

  29. 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 Plans and history

  30. Effort estimation study — your checklist

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

    docs/plans/effort_estimation_trial_maintainer_checklist.md Plans Plans and history

  31. Ephemeral Testing: Candidate Targets

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

    docs/plans/ephemeral_testing_targets.md Plans Plans and history

  32. Ephemeral Testing: Task Descriptions and Agent Prompts

    Companion to ephemeraltestingtargets.md.

    docs/plans/ephemeral_testing_tasks.md Plans Plans and history

  33. 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 Plans and history

  34. 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 Plans and history

  35. 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 Plans and history

  36. event_feature_gating_step4_implementation_summary.md

    docs/plans/event_feature_gating/event_feature_gating_step4_implementation_summary.md Plans Plans and history

  37. 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 Plans and history

  38. 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 Plans and history

  39. 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 Plans and history

  40. 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 Plans and history