zenmemes Platform Docs

Documents

• Clear all

2,618 documents

Search unavailable. Retry or refresh the library.

1. invite_qr_code_step4_implementation_summary.md

   Application implementation and automated/browser verification are committed on feature/invite-qr-code.

   docs/plans/invite_qr_code/invite_qr_code_step4_implementation_summary.md Plans Plans and history

2. Invite signing readiness — Railspike debug log

   Mode source: Host-root .railspikedebugon exists; new cycle default inherited.

   docs/plans/invite_signing_readiness/invite_signing_readiness_debug_log.md Plans Plans and history

3. invite_signing_readiness_reproduction.txt

   docs/plans/invite_signing_readiness/invite_signing_readiness_reproduction.txt Plans Plans and history

4. invite_signing_readiness_step1_solution_assessment.md

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

   docs/plans/invite_signing_readiness/invite_signing_readiness_step1_solution_assessment.md Plans Plans and history

5. invite_signing_readiness_step2_feature_description.md

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

   docs/plans/invite_signing_readiness/invite_signing_readiness_step2_feature_description.md Plans Plans and history

6. invite_signing_readiness_step3_development_plan.md

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

   docs/plans/invite_signing_readiness/invite_signing_readiness_step3_development_plan.md Plans Plans and history

7. invite_signing_readiness_step4_implementation_summary.md

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

   docs/plans/invite_signing_readiness/invite_signing_readiness_step4_implementation_summary.md Plans Plans and history

8. Invite zero-click workflow debug log

   No supported findings.

   docs/plans/invite_zero_click/invite_zero_click_debug_log.md Plans Plans and history

9. invite_zero_click_step1_solution_assessment.md

   Let's work on this part of the todo.txt.

   docs/plans/invite_zero_click/invite_zero_click_step1_solution_assessment.md Plans Plans and history

10. invite_zero_click_step2_feature_description.md

    Targeted invitations currently require interaction before entry, and the target is not reliably reached.

    docs/plans/invite_zero_click/invite_zero_click_step2_feature_description.md Plans Plans and history

11. invite_zero_click_step3_development_plan.md

    Application change: normal Invite button → unchecked destination opt-in, source-page prefill → generated link/QR → automatic targeted redemption → authenticate…

    docs/plans/invite_zero_click/invite_zero_click_step3_development_plan.md Plans Plans and history

12. Implementation summary

    docs/plans/invite_zero_click/invite_zero_click_step4_implementation_summary.md Plans Plans and history

13. iPhone reply submit — Railspike debug log

    No supported findings.

    docs/plans/iphone_reply_submit/iphone_reply_submit_debug_log.md Plans Plans and history

14. index.html

    docs/plans/iphone_reply_submit/iphone_reply_submit_mockups/index.html Plans Plans and history

15. iphone_reply_submit_step1_solution_assessment.md

    Interactive review: Compare the three mockups (simulated keyboard; no device-validation claim).

    docs/plans/iphone_reply_submit/iphone_reply_submit_step1_solution_assessment.md Plans Plans and history

16. iphone_reply_submit_step2_feature_description.md

    On iPhone, the keyboard can put the reply submit action out of reach below the editor.

    docs/plans/iphone_reply_submit/iphone_reply_submit_step2_feature_description.md Plans Plans and history

17. iphone_reply_submit_step3_development_plan.md

    From ordinary thread Reply or the dedicated reply page, an iPhone user can write and submit exactly one reply with Post visible above the open keyboard.

    docs/plans/iphone_reply_submit/iphone_reply_submit_step3_development_plan.md Plans Plans and history

18. iphone_reply_submit_step4_implementation_summary.md

    Implementation is ready for user testing on feat/iphone-reply-submit.

    docs/plans/iphone_reply_submit/iphone_reply_submit_step4_implementation_summary.md Plans Plans and history

19. acceptance.txt

    docs/plans/key_retirement/acceptance.txt Plans Plans and history

20. key_retirement — debug log

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

    docs/plans/key_retirement/key_retirement_debug_log.md Plans Plans and history

21. key_retirement_step1_solution_assessment.md

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

    docs/plans/key_retirement/key_retirement_step1_solution_assessment.md Plans Plans and history

22. key_retirement_step2_feature_description.md

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

    docs/plans/key_retirement/key_retirement_step2_feature_description.md Plans Plans and history

23. key_retirement_step3_development_plan.md

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

    docs/plans/key_retirement/key_retirement_step3_development_plan.md Plans Plans and history

24. key_retirement_step4_implementation_summary.md

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

    docs/plans/key_retirement/key_retirement_step4_implementation_summary.md Plans Plans and history

25. stage1_authority_findings.txt

    docs/plans/key_retirement/stage1_authority_findings.txt Plans Plans and history

26. LCD color choices — Railspike debug log

    Debug mode: enabled by the project-root .railspikedebugon marker.

    docs/plans/lcd_color_choices/lcd_color_choices_debug_log.md Plans Plans and history

27. LCD color choices

    Let's work on Feature 06, but Railspike it.

    docs/plans/lcd_color_choices/lcd_color_choices_step1_solution_assessment.md Plans Plans and history

28. LCD color choices — Feature description

    LCD offers only a green palette.

    docs/plans/lcd_color_choices/lcd_color_choices_step2_feature_description.md Plans Plans and history

29. LCD color choices — Development plan

    Awaiting Approved Step 3; no application edits or commits.

    docs/plans/lcd_color_choices/lcd_color_choices_step3_development_plan.md Plans Plans and history

30. LCD color choices — Implementation summary

    docs/plans/lcd_color_choices/lcd_color_choices_step4_implementation_summary.md Plans Plans and history

31. LCD palette rotation — Railspike debug log

    Debug mode: enabled by the project-root marker for this new follow-up.

    docs/plans/lcd_palette_rotation_debug_log.md Plans Plans and history

32. LCD palette rotation — Feature description

    Follow-up to LCD color choices, for the same intended release.

    docs/plans/lcd_palette_rotation_step2_feature_description.md Plans Plans and history

33. Legacy backup compatibility — Railspike debug log

    UTC date: 2026-10-20.

    docs/plans/legacy_backup_compatibility/legacy_backup_compatibility_debug_log.md Plans Plans and history

34. legacy_backup_compatibility_step1_solution_assessment.md

    Can you please help me figure out how to debug this and make sure it does not happen again?

    docs/plans/legacy_backup_compatibility/legacy_backup_compatibility_step1_solution_assessment.md Plans Plans and history

35. legacy_backup_compatibility_step2_feature_description.md

    Public repository downloads can fail on supported legacy posts missing Created-At when the image-aware exporter is selected.

    docs/plans/legacy_backup_compatibility/legacy_backup_compatibility_step2_feature_description.md Plans Plans and history

36. legacy_backup_compatibility_step3_development_plan.md

    The existing public downloads and ./v3 import-instance must handle committed legacy posts with an image-store directory, preserve bytes and recovered dates, pu…

    docs/plans/legacy_backup_compatibility/legacy_backup_compatibility_step3_development_plan.md Plans Plans and history

37. legacy_backup_compatibility_step4_implementation_summary.md

    docs/plans/legacy_backup_compatibility/legacy_backup_compatibility_step4_implementation_summary.md Plans Plans and history

38. Listing query dialog — Railspike debug log

    No supported findings.

    docs/plans/listing_query_dialog/listing_query_dialog_debug_log.md Plans Plans and history

39. listing_query_dialog_step1_solution_assessment.md

    Let's work on this idea from todo.txt, please:

    docs/plans/listing_query_dialog/listing_query_dialog_step1_solution_assessment.md Plans Plans and history

40. listing_query_dialog_step2_feature_description.md

    The user approved this split with Approved Step 2 after the sizing review.

    docs/plans/listing_query_dialog/listing_query_dialog_step2_feature_description.md Plans Plans and history