zenmemes

New post

zenmemes Platform Docs

Docs home

Documents

2,188 documents

Filters
  1. instance_content_sync_step1_solution_assessment.md

    From the TODO file:

    docs/plans/instance_content_sync/instance_content_sync_step1_solution_assessment.md Plans

  2. instance_content_sync_step2_feature_description.md

    Operators currently download a repository archive separately before importing it, and existing import coverage is incomplete.

    docs/plans/instance_content_sync/instance_content_sync_step2_feature_description.md Plans

  3. instance_content_sync_step3_development_plan.md

    Verify and commit each stage with its summary before continuing.

    docs/plans/instance_content_sync/instance_content_sync_step3_development_plan.md Plans

  4. instance_content_sync_step4_implementation_summary.md

    The original explicit-timestamp restriction is superseded by isolated history

    docs/plans/instance_content_sync/instance_content_sync_step4_implementation_summary.md Plans

  5. instance_image_import debug log

    No supported findings.

    docs/plans/instance_image_import/instance_image_import_debug_log.md Plans

  6. instance_image_import_step1_solution_assessment.md

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

    docs/plans/instance_image_import/instance_image_import_step1_solution_assessment.md Plans

  7. instance_image_import_step2_feature_description.md

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

    docs/plans/instance_image_import/instance_image_import_step2_feature_description.md Plans

  8. instance_image_import_step3_development_plan.md

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

    docs/plans/instance_image_import/instance_image_import_step3_development_plan.md Plans

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

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

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

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

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

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

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

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

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

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

  19. invite_signing_readiness_reproduction.txt

    docs/plans/invite_signing_readiness/invite_signing_readiness_reproduction.txt Plans

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

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

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

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

  24. Invite zero-click workflow debug log

    No supported findings.

    docs/plans/invite_zero_click/invite_zero_click_debug_log.md Plans

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

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

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

  28. Implementation summary

    docs/plans/invite_zero_click/invite_zero_click_step4_implementation_summary.md Plans

  29. iPhone reply submit — Railspike debug log

    No supported findings.

    docs/plans/iphone_reply_submit/iphone_reply_submit_debug_log.md Plans

  30. index.html

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

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

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

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

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

  35. acceptance.txt

    docs/plans/key_retirement/acceptance.txt Plans

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

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

  38. key_retirement_step2_feature_description.md

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

    docs/plans/key_retirement/key_retirement_step2_feature_description.md Plans

  39. key_retirement_step3_development_plan.md

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

    docs/plans/key_retirement/key_retirement_step3_development_plan.md Plans

  40. key_retirement_step4_implementation_summary.md

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

    docs/plans/key_retirement/key_retirement_step4_implementation_summary.md Plans