zenmemes

New post

zenmemes Platform Docs

Docs home

Documents

2,188 documents

Filters
  1. Fast LLM Post Scoring Step 2 Feature Description

    Full post analysis is too broad and expensive when a consumer only needs one focused probability.

    docs/plans/fast_llm_post_scoring/fast_llm_post_scoring_step2_feature_description.md Plans Plans and history

  2. Fast LLM Post Scoring Step 3 Development Plan

    docs/plans/fast_llm_post_scoring/fast_llm_post_scoring_step3_development_plan.md Plans Plans and history

  3. Fast LLM Post Scoring Step 4 Implementation Summary

    docs/plans/fast_llm_post_scoring/fast_llm_post_scoring_step4_implementation_summary.md Plans Plans and history

  4. Fast Post Scoring Batch Runner Step 1 Solution Assessment

    Operators need a safe command or scheduled worker that finds posts lacking a current fast score and rates them without reprocessing already current posts.

    docs/plans/fast_post_scoring_batch_runner/step1_solution_assessment.md Plans Plans and history

  5. Fast Post Scoring Batch Runner Step 2 Feature Description

    Fast scoring currently rates one requested post and forgets the outcome.

    docs/plans/fast_post_scoring_batch_runner/step2_feature_description.md Plans Plans and history

  6. Fast Post Scoring Batch Runner Step 3 Development Plan

    docs/plans/fast_post_scoring_batch_runner/step3_development_plan.md Plans Plans and history

  7. Fast Post Scoring Batch Runner Step 4 Implementation Summary

    docs/plans/fast_post_scoring_batch_runner/step4_implementation_summary.md Plans Plans and history

  8. Fastmod Productization - Remaining Work Plan

    Fastmod is a private moderation-review signal.

    docs/plans/fast_post_scoring_productization_remaining_work_plan.md Plans Plans and history

  9. fdp_to_railspike_debug_log.md

    Sources and evidence: Step 4 Do — Stage Boundary Protocol produced stage commits ba02ff71, 0472be5f, and 8e1d4bba, each with its summary.

    docs/plans/fdp_to_railspike/fdp_to_railspike_debug_log.md Plans Plans and history

  10. fdp_to_railspike_step1_solution_assessment.md

    I want to convert this project from using FDP to using Railspike, from https://github.com/gulkily/railspike.

    docs/plans/fdp_to_railspike/fdp_to_railspike_step1_solution_assessment.md Plans Plans and history

  11. fdp_to_railspike_step2_feature_description.md

    FDP is embedded in contributor guidance, workflow updates, and feature-request handoffs.

    docs/plans/fdp_to_railspike/fdp_to_railspike_step2_feature_description.md Plans Plans and history

  12. fdp_to_railspike_step3_development_plan.md

    docs/plans/fdp_to_railspike/fdp_to_railspike_step3_development_plan.md Plans Plans and history

  13. fdp_to_railspike_step4_implementation_summary.md

    docs/plans/fdp_to_railspike/fdp_to_railspike_step4_implementation_summary.md Plans Plans and history

  14. Step 1: Solution Assessment — Feature Flags Page Organization

    Please review our feature flags page, does it need better organizing?

    docs/plans/feature_flags_organization/feature_flags_organization_step1_solution_assessment.md Plans Plans and history

  15. Step 2: Feature Description — Feature Flags Page Organization

    The feature-flags page groups seven unrelated settings under “Forum” because it follows technical key prefixes.

    docs/plans/feature_flags_organization/feature_flags_organization_step2_feature_description.md Plans Plans and history

  16. Step 3: Development Plan — Feature Flags Page Organization

    docs/plans/feature_flags_organization/feature_flags_organization_step3_development_plan.md Plans Plans and history

  17. Step 4: Implementation Summary — Feature Flags Page Organization

    docs/plans/feature_flags_organization/feature_flags_organization_step4_implementation_summary.md Plans Plans and history

  18. Step 1: Solution Assessment — Feature Flags Page Redesign

    The /tools/feature-flags/ page uses a fixed-width table that wraps flag keys mid-word and doesn't scale past a handful of flags, and the reviewed spec (docs/fe…

    docs/plans/feature_flags_redesign/feature_flags_redesign_step1_solution_assessment.md Plans Plans and history

  19. Step 2: Feature Description — Feature Flags Page Redesign

    The /tools/feature-flags/ page's fixed-width table wraps flag keys mid-word and shows four always-visible columns per flag, which doesn't scale as the flag cou…

    docs/plans/feature_flags_redesign/feature_flags_redesign_step2_feature_description.md Plans Plans and history

  20. Step 3: Development Plan — Feature Flags Page Redesign

    docs/plans/feature_flags_redesign/feature_flags_redesign_step3_development_plan.md Plans Plans and history

  21. Step 4: Implementation Summary — Feature Flags Page Redesign

    docs/plans/feature_flags_redesign/feature_flags_redesign_step4_implementation_summary.md Plans Plans and history

  22. Feature Flags security-review cleanup — Railspike debug log

    No supported findings.

    docs/plans/feature_flags_security_review_cleanup/feature_flags_security_review_cleanup_debug_log.md Plans Plans and history

  23. index.html

    docs/plans/feature_flags_security_review_cleanup/feature_flags_security_review_cleanup_mockups/index.html Plans Plans and history

  24. feature_flags_security_review_cleanup_step1_solution_assessment.md

    Effort study: railspike-effort / v3/featureflagssecurityreviewcleanup · Ledger

    docs/plans/feature_flags_security_review_cleanup/feature_flags_security_review_cleanup_step1_solution_assessment.md Plans Plans and history

  25. Access history in User Access

    Effort study: railspike-effort / v3/featureflagssecurityreviewcleanup · Ledger

    docs/plans/feature_flags_security_review_cleanup/feature_flags_security_review_cleanup_step2_feature_description.md Plans Plans and history

  26. Access history — development plan

    Effort study: railspike-effort / v3/featureflagssecurityreviewcleanup · Ledger

    docs/plans/feature_flags_security_review_cleanup/feature_flags_security_review_cleanup_step3_development_plan.md Plans Plans and history

  27. Access history — implementation

    Effort study: railspike-effort / v3/featureflagssecurityreviewcleanup · Ledger

    docs/plans/feature_flags_security_review_cleanup/feature_flags_security_review_cleanup_step4_implementation_summary.md Plans Plans and history

  28. Feature flags toolbar — Railspike debug log

    docs/plans/feature_flags_toolbar/feature_flags_toolbar_debug_log.md Plans Plans and history

  29. Feature flags search and status toolbar

    The grouped /tools/feature-flags/ page still requires scanning every flag to find a setting or inspect enabled, overridden, or locked flags.

    docs/plans/feature_flags_toolbar/feature_flags_toolbar_step2_feature_description.md Plans Plans and history

  30. feature_flags_toolbar_step3_development_plan.md

    docs/plans/feature_flags_toolbar/feature_flags_toolbar_step3_development_plan.md Plans Plans and history

  31. Implementation summary

    docs/plans/feature_flags_toolbar/feature_flags_toolbar_step4_implementation_summary.md Plans Plans and history

  32. Step 1: Solution Assessment — Signed Feature-Flag Changes

    We need to record who changed a feature flag and sign the request.

    docs/plans/feature_flag_change_attribution/feature_flag_change_attribution_step1_solution_assessment.md Plans Plans and history

  33. Step 2: Feature Description — Signed Feature-Flag Changes

    Feature-flag changes currently prove only that a root-approved session reached the server.

    docs/plans/feature_flag_change_attribution/feature_flag_change_attribution_step2_feature_description.md Plans Plans and history

  34. Step 3: Development Plan — Signed Feature-Flag Changes

    docs/plans/feature_flag_change_attribution/feature_flag_change_attribution_step3_development_plan.md Plans Plans and history

  35. Step 4: Implementation Summary — Signed Feature-Flag Changes

    docs/plans/feature_flag_change_attribution/feature_flag_change_attribution_step4_implementation_summary.md Plans Plans and history

  36. Railspike debug log — feature_flag_change_pages

    Mode source: .railspikedebugon present at project root (new workflow default).

    docs/plans/feature_flag_change_pages/feature_flag_change_pages_debug_log.md Plans Plans and history

  37. Step 1: Solution Assessment — Feature-Flag Change Pages

    OK, there's no pages for feature change items, I guess?

    docs/plans/feature_flag_change_pages/feature_flag_change_pages_step1_solution_assessment.md Plans Plans and history

  38. Step 2: Feature Description — Feature-Flag Change Pages

    Approved direction: Step 1 Option B (dedicated change page; legacy items fall back to their commit page).

    docs/plans/feature_flag_change_pages/feature_flag_change_pages_step2_feature_description.md Plans Plans and history

  39. Step 3: Development Plan — Feature-Flag Change Pages

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

    docs/plans/feature_flag_change_pages/feature_flag_change_pages_step3_development_plan.md Plans Plans and history

  40. feature_flag_change_pages_step4_implementation_summary.md

    Branch: feature/featureflagchangepages, based on fix/backup-page-tools-nav-order (unmerged; carries the Backup layout fix that Stage 5 depends on).

    docs/plans/feature_flag_change_pages/feature_flag_change_pages_step4_implementation_summary.md Plans Plans and history