qdb

qdb Platform Docs

Docs home

Documents

1,727 documents

Filters
  1. agent_api_docs Railspike debug log

    docs/plans/agent_api_docs/agent_api_docs_debug_log.md Plans Plans and history

  2. agent_api_docs_step1_solution_assessment.md

    Let's start with Cycle D, even though we may need to make some updates later.

    docs/plans/agent_api_docs/agent_api_docs_step1_solution_assessment.md Plans Plans and history

  3. agent_api_docs_step2_feature_description.md

    An agent arriving at an instance finds a stale /llms.txt ("Local test slice") and an /api/ index that does not say which routes are signed or how to sign.

    docs/plans/agent_api_docs/agent_api_docs_step2_feature_description.md Plans Plans and history

  4. agent_api_docs_step3_development_plan.md

    None recorded.

    docs/plans/agent_api_docs/agent_api_docs_step3_development_plan.md Plans Plans and history

  5. agent_api_docs_step4_implementation_summary.md

    Branch: feat/agent-api-docs, from origin/main at c6fe21b4 (which adds the onboarding checklist, pushed at the user's request).

    docs/plans/agent_api_docs/agent_api_docs_step4_implementation_summary.md Plans Plans and history

  6. Agent API Onboarding Checklist

    Source: an agent's review of zenmemes.com (12 documentation suggestions plus one

    docs/plans/agent_api_onboarding_checklist.md Plans Plans and history

  7. Agent personality and multiple agents — Railspike debug log

    No supported findings.

    docs/plans/agent_personality_and_multiple_agents/agent_personality_and_multiple_agents_debug_log.md Plans Plans and history

  8. agent_personality_and_multiple_agents_step1_solution_assessment.md

    From docs/plans/zenmemesmetafeedback2026-10-18summary.md:

    docs/plans/agent_personality_and_multiple_agents/agent_personality_and_multiple_agents_step1_solution_assessment.md Plans Plans and history

  9. agent_personality_and_multiple_agents_step2_feature_description.md

    The existing reply-agent has little personality guidance and lacks approval/admin context.

    docs/plans/agent_personality_and_multiple_agents/agent_personality_and_multiple_agents_step2_feature_description.md Plans Plans and history

  10. agent_personality_and_multiple_agents_step3_development_plan.md

    Step 2 approved; implement Option A only.

    docs/plans/agent_personality_and_multiple_agents/agent_personality_and_multiple_agents_step3_development_plan.md Plans Plans and history

  11. agent_personality_and_multiple_agents_step4_implementation_summary.md

    Step 3 approved.

    docs/plans/agent_personality_and_multiple_agents/agent_personality_and_multiple_agents_step4_implementation_summary.md Plans Plans and history

  12. Agent personality acceptance review

    Evaluated with the configured gpt-5-mini writer using synthetic posts in fresh

    docs/plans/agent_personality_and_multiple_agents/evaluation/report.md Plans Plans and history

  13. results.json

    docs/plans/agent_personality_and_multiple_agents/evaluation/results.json Plans Plans and history

  14. Agent posting — Railspike debug log

    Source: RAILSPIKE.md, instruction summaries and approval gates.

    docs/plans/agent_posting/agent_posting_debug_log.md Plans Plans and history

  15. agent_posting_step1_solution_assessment.md

    Effort study: railspike-effort / v3/agentposting; ledger, standing P2 enrollment

    docs/plans/agent_posting/agent_posting_step1_solution_assessment.md Plans Plans and history

  16. agent_posting_step2_feature_description.md

    Effort study: railspike-effort / v3/agentposting; ledger, standing P2 enrollment

    docs/plans/agent_posting/agent_posting_step2_feature_description.md Plans Plans and history

  17. agent_posting_step3_development_plan.md

    Effort study: railspike-effort / v3/agentposting; ledger, standing P2 enrollment

    docs/plans/agent_posting/agent_posting_step3_development_plan.md Plans Plans and history

  18. agent_posting_step4_implementation_summary.md

    Effort study: railspike-effort / v3/agentposting; ledger

    docs/plans/agent_posting/agent_posting_step4_implementation_summary.md Plans Plans and history

  19. Agent Reply Length Step 1 Solution Assessment

    This reply was kind of long for this forum, although maybe that's what a user could have been looking for.

    docs/plans/agent_reply_length/agent_reply_length_step1_solution_assessment.md Plans Plans and history

  20. Scripture Response Guidance and Expansion Step 2 Feature Description

    Readers need complete scripture responses shaped by the question, with optional expansion for further depth.

    docs/plans/agent_reply_length/agent_reply_length_step2_feature_description.md Plans Plans and history

  21. Scripture Response Guidance and Expansion Step 3 Development Plan

    docs/plans/agent_reply_length/agent_reply_length_step3_development_plan.md Plans Plans and history

  22. Scripture Response Guidance and Expansion Implementation Summary

    docs/plans/agent_reply_length/agent_reply_length_step4_implementation_summary.md Plans Plans and history

  23. Agent Reply Manual Trigger and Cron Plan

    Let operators intentionally trigger a reply-agent response for a specific post,

    docs/plans/agent_reply_manual_trigger_and_cron_plan_v1.md Plans Plans and history

  24. Agent Reply One-Step Analyze/Publish Plan

    Make automatic agent reply publishing happen inside POST /api/analyzepost, while keeping POST /api/generateagentreply as an idempotent compatibility and manual…

    docs/plans/agent_reply_one_step_analyze_publish_plan_v1.md Plans Plans and history

  25. Agent Reply Task Queue Merge Step 1 Solution Assessment

    As an operator, I want the agent reply queue and general purpose queue to be merged into the general purpose queue.

    docs/plans/agent_reply_task_queue_merge/agent_reply_task_queue_merge_step1_solution_assessment.md Plans Plans and history

  26. Agent Reply Task Queue Merge Step 2 Feature Description

    Agent replies and maintenance work currently use separate queues, workers, locks, cron entries, and operational status paths.

    docs/plans/agent_reply_task_queue_merge/agent_reply_task_queue_merge_step2_feature_description.md Plans Plans and history

  27. Agent Reply Task Queue Merge Step 3 Development Plan

    docs/plans/agent_reply_task_queue_merge/agent_reply_task_queue_merge_step3_development_plan.md Plans Plans and history

  28. Agent Reply Task Queue Merge Step 4 Implementation Summary

    docs/plans/agent_reply_task_queue_merge/agent_reply_task_queue_merge_step4_implementation_summary.md Plans Plans and history

  29. Agent Response Direct Preflight Step 1 Solution Assessment

    I agree with this, can it be a one-shot, or should we do docs/fdp/FEATUREDEVELOPMENTPROCESS.md again?

    docs/plans/agent_response_direct_preflight/agent_response_direct_preflight_step1_solution_assessment.md Plans Plans and history

  30. Agent Response Direct Preflight Step 2 Feature Description

    Requested response modes currently wait for full model-backed post analysis even though the resulting legacy suggested reply is not used.

    docs/plans/agent_response_direct_preflight/agent_response_direct_preflight_step2_feature_description.md Plans Plans and history

  31. Agent Response Direct Preflight Step 3 Development Plan

    docs/plans/agent_response_direct_preflight/agent_response_direct_preflight_step3_development_plan.md Plans Plans and history

  32. Agent Response Direct Preflight Step 4 Implementation Summary

    docs/plans/agent_response_direct_preflight/agent_response_direct_preflight_step4_implementation_summary.md Plans Plans and history

  33. Agent Response Dropdown Viewport Fit – Solution Assessment

    The request agent response dropdown does not always fully display in-page.

    docs/plans/agent_response_dropdown_viewport_fit/agent_response_dropdown_viewport_fit_step1_solution_assessment.md Plans Plans and history

  34. Agent Response Dropdown Viewport Fit – Feature Description

    The mode menu opened from the "request agent reply" button is placed once on open, so it can be clipped by the viewport and does not stay attached to its butto…

    docs/plans/agent_response_dropdown_viewport_fit/agent_response_dropdown_viewport_fit_step2_feature_description.md Plans Plans and history

  35. Agent Response Dropdown Viewport Fit – Development Plan

    docs/plans/agent_response_dropdown_viewport_fit/agent_response_dropdown_viewport_fit_step3_development_plan.md Plans Plans and history

  36. Agent Response Dropdown Viewport Fit – Implementation Summary

    docs/plans/agent_response_dropdown_viewport_fit/agent_response_dropdown_viewport_fit_step4_implementation_summary.md Plans Plans and history

  37. Agent Response Harness Simplification Step 1 Solution Assessment

    Please write Step 1 of docs/fdp/FEATUREDEVELOPMENTPROCESS.md for simplifying the agent response harness in preparation for the response type selector.

    docs/plans/agent_response_harness_simplification/agent_response_harness_simplification_step1_solution_assessment.md Plans Plans and history

  38. Agent Response Harness Simplification Step 2 Feature Description

    Requested agent replies are currently extracted from a broad structured analysis, rather than generated as focused response tasks.

    docs/plans/agent_response_harness_simplification/agent_response_harness_simplification_step2_feature_description.md Plans Plans and history

  39. Agent Response Harness Simplification Step 3 Development Plan

    docs/plans/agent_response_harness_simplification/agent_response_harness_simplification_step3_development_plan.md Plans Plans and history

  40. Agent Response Harness Simplification Step 4 Implementation Summary

    docs/plans/agent_response_harness_simplification/agent_response_harness_simplification_step4_implementation_summary.md Plans Plans and history