-
account_retraction_attribution_step1_solution_assessment.md
Please write Step 1 for this modification.
docs/plans/account_retraction_attribution/account_retraction_attribution_step1_solution_assessment.md Plans Plans and history
-
account_retraction_attribution_step2_feature_description.md
Retraction notices equate authorship with an exact signing key, so an operator using another approved key for the same account is described as an outside opera…
docs/plans/account_retraction_attribution/account_retraction_attribution_step2_feature_description.md Plans Plans and history
-
account_retraction_attribution_step3_development_plan.md
docs/plans/account_retraction_attribution/account_retraction_attribution_step3_development_plan.md Plans Plans and history
-
account_retraction_attribution_step4_implementation_summary.md
Implementation complete on feature/account-retraction-attribution.
docs/plans/account_retraction_attribution/account_retraction_attribution_step4_implementation_summary.md Plans Plans and history
-
Account Setup Auto-Publish Public Key Plan V1
When a user clicks Set up this browser or Re-setup / change name on /account/key/, a successful setup should publish the generated public key to the server bef…
docs/plans/account_setup_auto_publish_public_key_plan_v1.md Plans Plans and history
-
Activity feed pagination — Railspike debug log
No supported findings.
docs/plans/activity_feed_pagination/activity_feed_pagination_debug_log.md Plans Plans and history
-
activity_feed_pagination_step1_solution_assessment.md
Effort study: railspike-effort / v3/activityfeedpagination; ledger, standing enrollment P2.
docs/plans/activity_feed_pagination/activity_feed_pagination_step1_solution_assessment.md Plans Plans and history
-
activity_feed_pagination_step2_feature_description.md
Effort study: railspike-effort / v3/activityfeedpagination; ledger, standing enrollment P2; scope v3.
docs/plans/activity_feed_pagination/activity_feed_pagination_step2_feature_description.md Plans Plans and history
-
activity_feed_pagination_step3_development_plan.md
Effort study: railspike-effort / v3/activityfeedpagination; ledger, scope v3, R1/P2.
docs/plans/activity_feed_pagination/activity_feed_pagination_step3_development_plan.md Plans Plans and history
-
activity_feed_pagination_step4_implementation_summary.md
Effort study: railspike-effort / v3/activityfeedpagination; ledger, scope v3, R1/P2.
docs/plans/activity_feed_pagination/activity_feed_pagination_step4_implementation_summary.md Plans Plans and history
-
Activity load performance — Railspike debug log
Mode: Enabled by host-root marker; recorded in Step 1.
docs/plans/activity_load_performance/activity_load_performance_debug_log.md Plans Plans and history
-
Activity load performance investigation
Scope: Read-only production HTTP samples and local source inspection for Step 1.
docs/plans/activity_load_performance/activity_load_performance_investigation.md Plans Plans and history
-
activity_load_performance_step1_solution_assessment.md
Effort study: railspike-effort / v3/activityloadperformance; ledger
docs/plans/activity_load_performance/activity_load_performance_step1_solution_assessment.md Plans Plans and history
-
activity_load_performance_step2_feature_description.md
Effort study: railspike-effort / v3/activityloadperformance; ledger
docs/plans/activity_load_performance/activity_load_performance_step2_feature_description.md Plans Plans and history
-
activity_load_performance_step3_development_plan.md
Effort study: railspike-effort / v3/activityloadperformance; ledger
docs/plans/activity_load_performance/activity_load_performance_step3_development_plan.md Plans Plans and history
-
activity_load_performance_step4_implementation_summary.md
Effort study: railspike-effort / v3/activityloadperformance; ledger
docs/plans/activity_load_performance/activity_load_performance_step4_implementation_summary.md Plans Plans and history
-
Activity Source Filename And Commit Plan
Yes.
docs/plans/activity_source_filename_commit_plan_v1.md Plans Plans and history
-
Activity/Commit-Manifest Subsystem Extraction — Plan v1
Sub-plan for the last hard piece of docs/plans/codebasecleanupauditplanv1.md
docs/plans/activity_subsystem_extraction_plan_v1.md Plans Plans and history
-
agent_api_docs Railspike debug log
docs/plans/agent_api_docs/agent_api_docs_debug_log.md Plans Plans and history
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
results.json
docs/plans/agent_personality_and_multiple_agents/evaluation/results.json Plans Plans and history
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
Scripture Response Guidance and Expansion Implementation Summary
docs/plans/agent_reply_length/agent_reply_length_step4_implementation_summary.md Plans Plans and history