zenmemes Platform Docs

Documents

• Collection: Plans and history ×
• Clear all

1,645 documents

Search unavailable. Retry or refresh the library.

1. image_content_step4_implementation_summary.md

   docs/plans/image_content/image_content_step4_implementation_summary.md Plans

2. Image upload enhancements — Railspike debug log

   Debug mode enabled at the user's request after the initial Step 1 handoff.

   docs/plans/image_upload_enhancements/image_upload_enhancements_debug_log.md Plans

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

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

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

6. image_upload_enhancements_step4_implementation_summary.md

   docs/plans/image_upload_enhancements/image_upload_enhancements_step4_implementation_summary.md Plans

7. Imported Feature Requests Summary V1

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

   docs/plans/imported_feature_requests_summary_v1.md Plans

8. import_archive_adversarial_review.txt

   docs/plans/import_archive_adversarial_review.txt Plans

9. Import archive hardening — Railspike debug log

   No supported findings.

   docs/plans/import_archive_hardening/import_archive_hardening_debug_log.md Plans

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

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

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

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

14. Import record failure isolation — Railspike debug log

    No supported findings.

    docs/plans/import_record_failure_isolation_debug_log.md Plans

15. import_record_failure_isolation_review.txt

    docs/plans/import_record_failure_isolation_review.txt Plans

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

17. Import without static rendering — Railspike diagnostics

    No supported findings.

    docs/plans/import_without_static_rendering_debug_log.md Plans

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

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

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

21. instance_content_sync_step1_solution_assessment.md

    From the TODO file:

    docs/plans/instance_content_sync/instance_content_sync_step1_solution_assessment.md Plans

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

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

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

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

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

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

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

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

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

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

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

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

34. invite_signing_readiness_reproduction.txt

    docs/plans/invite_signing_readiness/invite_signing_readiness_reproduction.txt Plans

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

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

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

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

39. Invite zero-click workflow debug log

    No supported findings.

    docs/plans/invite_zero_click/invite_zero_click_debug_log.md Plans

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