zenmemes

New post

zenmemes Platform Docs

Docs home

Documents

2,560 documents

Filters
  1. instance_image_import_step4_implementation_summary.md

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

    docs/plans/instance_image_import/instance_image_import_step4_implementation_summary.md Plans Plans and history

  2. instance_import_approval_review_step1_solution_assessment.md

    When we import another instance, we end up with a lot of unapproved accounts.

    docs/plans/instance_import_approval_review_step1_solution_assessment.md Plans Plans and history

  3. instance_incremental_sync_step1_solution_assessment.md

    Deliver the scheduled archive import feature first, then implement its Option B—an incremental content sync API—as a separate feature.

    docs/plans/instance_incremental_sync/instance_incremental_sync_step1_solution_assessment.md Plans Plans and history

  4. Instance portability gaps and feasibility assessment

    The current downloads preserve the canonical public forum record and the current SQLite index database, not the entire running instance.

    docs/plans/instance_portability_gap_assessment.md Plans Plans and history

  5. Invite QR Code — Railspike Debug Log

    Debug mode: enabled by the user's explicit request.

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

  6. invite_qr_code_step1_solution_assessment.md

    As a user, if I am inviting someone in person, I want to have a QR code for them to scan as soon as I've generated an invite on the invite page.

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

  7. invite_qr_code_step2_feature_description.md

    The invite page provides a copyable link, but inviting someone in person requires an immediately scannable handoff.

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

  8. invite_qr_code_step3_development_plan.md

    Each stage ends with applicable verification, a Step 4 summary update, and its own commit before the next stage.

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

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

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

  11. invite_signing_readiness_reproduction.txt

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

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

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

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

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

  16. Invite zero-click workflow debug log

    No supported findings.

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

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

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

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

  20. Implementation summary

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

  21. iPhone reply submit — Railspike debug log

    No supported findings.

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

  22. index.html

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

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

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

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

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

  27. acceptance.txt

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

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

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

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

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

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

  33. stage1_authority_findings.txt

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

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

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

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

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

  38. LCD color choices — Implementation summary

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

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

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