zenmemes Platform Docs

Documents

• Category: Plans ×
• Clear all

2,186 documents

Search unavailable. Retry or refresh the library.

1. s7-integrity.txt

   docs/plans/application_capacity_study/s7-integrity.txt Plans Plans and history

2. s7-php-metrics.txt

   docs/plans/application_capacity_study/s7-php-metrics.txt Plans Plans and history

3. s7-php-server.log.txt

   docs/plans/application_capacity_study/s7-php-server.log.txt Plans Plans and history

4. s7-publication.log.txt

   docs/plans/application_capacity_study/s7-publication.log.txt Plans Plans and history

5. s7-recovery-rebuild.log.txt

   docs/plans/application_capacity_study/s7-recovery-rebuild.log.txt Plans Plans and history

6. s7-replay.txt

   docs/plans/application_capacity_study/s7-replay.txt Plans Plans and history

7. s7-samples.txt

   docs/plans/application_capacity_study/s7-samples.txt Plans Plans and history

8. s7-signed-port-final.log.txt

   docs/plans/application_capacity_study/s7-signed-port-final.log.txt Plans Plans and history

9. s7-signed-port-verification.log.txt

   docs/plans/application_capacity_study/s7-signed-port-verification.log.txt Plans Plans and history

10. s7-static-delivery-final.log.txt

    docs/plans/application_capacity_study/s7-static-delivery-final.log.txt Plans Plans and history

11. s7-static-delivery.log.txt

    docs/plans/application_capacity_study/s7-static-delivery.log.txt Plans Plans and history

12. s7signing.py.txt

    docs/plans/application_capacity_study/s7signing.py.txt Plans Plans and history

13. s7static.py.txt

    docs/plans/application_capacity_study/s7static.py.txt Plans Plans and history

14. setup.py.txt

    docs/plans/application_capacity_study/setup.py.txt Plans Plans and history

15. signed_driver.php.txt

    docs/plans/application_capacity_study/signed_driver.php.txt Plans Plans and history

16. static_delivery_driver.py.txt

    docs/plans/application_capacity_study/static_delivery_driver.py.txt Plans Plans and history

17. transfer_driver.py.txt

    docs/plans/application_capacity_study/transfer_driver.py.txt Plans Plans and history

18. Approval acceptance text — Railspike debug log

    Debug mode: enabled by confirmed host-root marker file; contents not read.

    docs/plans/approval_acceptance_text/approval_acceptance_text_debug_log.md Plans Plans and history

19. approval_acceptance_text_step1_solution_assessment.md

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

    docs/plans/approval_acceptance_text/approval_acceptance_text_step1_solution_assessment.md Plans Plans and history

20. approval_acceptance_text_step2_feature_description.md

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

    docs/plans/approval_acceptance_text/approval_acceptance_text_step2_feature_description.md Plans Plans and history

21. approval_acceptance_text_step3_development_plan.md

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

    docs/plans/approval_acceptance_text/approval_acceptance_text_step3_development_plan.md Plans Plans and history

22. approval_acceptance_text_step4_implementation_summary.md

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

    docs/plans/approval_acceptance_text/approval_acceptance_text_step4_implementation_summary.md Plans Plans and history

23. approval_seed_immediate_refresh_step1_solution_assessment.md

    I've been told that ./v3 approve or ./v3 approval seed requires a complete rebuild.

    docs/plans/approval_seed_immediate_refresh/approval_seed_immediate_refresh_step1_solution_assessment.md Plans Plans and history

24. approval_seed_immediate_refresh_step2_feature_description.md

    ./v3 approve and ./v3 approval seed currently require a full read-model rebuild before reporting success.

    docs/plans/approval_seed_immediate_refresh/approval_seed_immediate_refresh_step2_feature_description.md Plans Plans and history

25. approval_seed_immediate_refresh_step3_development_plan.md

    Every stage requires verification, summary update, and a commit before its successor.

    docs/plans/approval_seed_immediate_refresh/approval_seed_immediate_refresh_step3_development_plan.md Plans Plans and history

26. approval_seed_immediate_refresh_step4_implementation_summary.md

    docs/plans/approval_seed_immediate_refresh/approval_seed_immediate_refresh_step4_implementation_summary.md Plans Plans and history

27. app_sessions — Railspike debug log

    Mode: enabled from the project marker (new workflow, no explicit request).

    docs/plans/app_sessions/app_sessions_debug_log.md Plans Plans and history

28. app_sessions_step1_solution_assessment.md

    Debug mode: enabled (project marker .railspikedebugon present; debug log)

    docs/plans/app_sessions/app_sessions_step1_solution_assessment.md Plans Plans and history

29. app_sessions_step2_feature_description.md

    Debug mode: enabled (debug log)

    docs/plans/app_sessions/app_sessions_step2_feature_description.md Plans Plans and history

30. app_sessions_step3_development_plan.md

    Debug mode: enabled (debug log)

    docs/plans/app_sessions/app_sessions_step3_development_plan.md Plans Plans and history

31. app_sessions_step4_implementation_summary.md

    Debug mode: enabled (debug log)

    docs/plans/app_sessions/app_sessions_step4_implementation_summary.md Plans Plans and history

32. Activity Commit File Manifest — Step 1: Solution Assessment

    Classic Activity and Forte Activity show only the activity record's source file, even when its commit atomically changes additional canonical files, and do not…

    docs/plans/archive/activity_commit_file_manifest_step1_solution_assessment.md Plans Plans and history

33. Activity Commit File Manifest — Step 2: Feature Description

    An activity event represents one record, but its commit can change several files.

    docs/plans/archive/activity_commit_file_manifest_step2_feature_description.md Plans Plans and history

34. Activity Commit File Manifest — Step 3: Development Plan

    Reply Approved Step 3 to begin implementation on a feature branch.

    docs/plans/archive/activity_commit_file_manifest_step3_development_plan.md Plans Plans and history

35. Activity Commit File Manifest — Step 4: Implementation Summary

    docs/plans/archive/activity_commit_file_manifest_step4_implementation_summary.md Plans Plans and history

36. Activity Manifest Readability — Step 2: Feature Description

    Activity cards repeat source/signature filenames above the commit manifest, and inline manifest paths are hard to scan.

    docs/plans/archive/activity_manifest_readability_step2_feature_description.md Plans Plans and history

37. Activity Manifest Readability — Step 3: Development Plan

    Reply Approved Step 3 to begin implementation on a feature branch.

    docs/plans/archive/activity_manifest_readability_step3_development_plan.md Plans Plans and history

38. Activity Manifest Readability — Step 4: Implementation Summary

    docs/plans/archive/activity_manifest_readability_step4_implementation_summary.md Plans Plans and history

39. Activity Source Links Slices Plan

    Make the activity page source metadata actionable:

    docs/plans/archive/activity_source_links_slices_v1.md Plans Plans and history

40. Agent Reply Request Button Step 1 Solution Assessment

    Users need an intentional in-page control that requests a reply-agent response for a specific post without relying on automatic browser-triggered reply work.

    docs/plans/archive/agent_reply_request_button_step1_solution_assessment.md Plans Plans and history