zenmemes

New post

zenmemes Platform Docs

Docs home

Documents

1,741 documents

Filters
  1. image_upload_enhancements_step1_solution_assessment.md

    We want to make many enhancements to the image upload feature.

    docs/plans/image_upload_enhancements/image_upload_enhancements_step1_solution_assessment.md Plans Plans and history

  2. image_upload_enhancements_step2_feature_description.md

    Image posting requires users to resize or convert files themselves and exposes controls to people who cannot upload.

    docs/plans/image_upload_enhancements/image_upload_enhancements_step2_feature_description.md Plans Plans and history

  3. image_upload_enhancements_step3_development_plan.md

    Approved members use every existing thread/reply composer to select/drop/paste, preview, describe, publish, and view a prepared image.

    docs/plans/image_upload_enhancements/image_upload_enhancements_step3_development_plan.md Plans Plans and history

  4. image_upload_enhancements_step4_implementation_summary.md

    docs/plans/image_upload_enhancements/image_upload_enhancements_step4_implementation_summary.md Plans Plans and history

  5. Imported Feature Requests Summary V1

    Reviewed source set from backlog/plans-2026-08-26:

    docs/plans/imported_feature_requests_summary_v1.md Plans Plans and history

  6. import_archive_adversarial_review.txt

    docs/plans/import_archive_adversarial_review.txt Plans Plans and history

  7. Import archive hardening — Railspike debug log

    No supported findings.

    docs/plans/import_archive_hardening/import_archive_hardening_debug_log.md Plans Plans and history

  8. import_archive_hardening_step1_solution_assessment.md

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

    docs/plans/import_archive_hardening/import_archive_hardening_step1_solution_assessment.md Plans Plans and history

  9. import_archive_hardening_step2_feature_description.md

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

    docs/plans/import_archive_hardening/import_archive_hardening_step2_feature_description.md Plans Plans and history

  10. import_archive_hardening_step3_development_plan.md

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

    docs/plans/import_archive_hardening/import_archive_hardening_step3_development_plan.md Plans Plans and history

  11. import_archive_hardening_step4_implementation_summary.md

    Effort study: railspike-effort / v3/importarchivehardening; ledger.

    docs/plans/import_archive_hardening/import_archive_hardening_step4_implementation_summary.md Plans Plans and history

  12. Import record failure isolation — Railspike debug log

    No supported findings.

    docs/plans/import_record_failure_isolation_debug_log.md Plans Plans and history

  13. import_record_failure_isolation_review.txt

    docs/plans/import_record_failure_isolation_review.txt Plans Plans and history

  14. import_record_failure_isolation_step1_solution_assessment.md

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

    docs/plans/import_record_failure_isolation_step1_solution_assessment.md Plans Plans and history

  15. Import without static rendering — Railspike diagnostics

    No supported findings.

    docs/plans/import_without_static_rendering_debug_log.md Plans Plans and history

  16. Import without static rendering — one-shot outcome

    User opted out of staged Railspike after the initial assessment.

    docs/plans/import_without_static_rendering_one_shot_summary.md Plans Plans and history

  17. import_without_static_rendering_step1_solution_assessment.md

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

    docs/plans/import_without_static_rendering_step1_solution_assessment.md Plans Plans and history

  18. Instance content import fixes

    The zenmemes.com preview exposed closed-pipe notices and cascading legacy

    docs/plans/instance_content_sync/instance_content_sync_fix_checklist.md Plans Plans and history

  19. instance_content_sync_step1_solution_assessment.md

    From the TODO file:

    docs/plans/instance_content_sync/instance_content_sync_step1_solution_assessment.md Plans Plans and history

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

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

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

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

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

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

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

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

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

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

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

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

  32. invite_signing_readiness_reproduction.txt

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

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

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

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

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

  37. Invite zero-click workflow debug log

    No supported findings.

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

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

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

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