-
s7-replay.txt
docs/plans/application_capacity_study/s7-replay.txt Plans Plans and history
-
s7-samples.txt
docs/plans/application_capacity_study/s7-samples.txt Plans Plans and history
-
s7-signed-port-final.log.txt
docs/plans/application_capacity_study/s7-signed-port-final.log.txt Plans Plans and history
-
s7-signed-port-verification.log.txt
docs/plans/application_capacity_study/s7-signed-port-verification.log.txt Plans Plans and history
-
s7-static-delivery-final.log.txt
docs/plans/application_capacity_study/s7-static-delivery-final.log.txt Plans Plans and history
-
s7-static-delivery.log.txt
docs/plans/application_capacity_study/s7-static-delivery.log.txt Plans Plans and history
-
s7signing.py.txt
docs/plans/application_capacity_study/s7signing.py.txt Plans Plans and history
-
s7static.py.txt
docs/plans/application_capacity_study/s7static.py.txt Plans Plans and history
-
setup.py.txt
docs/plans/application_capacity_study/setup.py.txt Plans Plans and history
-
signed_driver.php.txt
docs/plans/application_capacity_study/signed_driver.php.txt Plans Plans and history
-
static_delivery_driver.py.txt
docs/plans/application_capacity_study/static_delivery_driver.py.txt Plans Plans and history
-
transfer_driver.py.txt
docs/plans/application_capacity_study/transfer_driver.py.txt Plans Plans and history
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
Activity Commit File Manifest — Step 4: Implementation Summary
docs/plans/archive/activity_commit_file_manifest_step4_implementation_summary.md Plans Plans and history
-
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
-
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
-
Activity Manifest Readability — Step 4: Implementation Summary
docs/plans/archive/activity_manifest_readability_step4_implementation_summary.md Plans Plans and history
-
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
-
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
-
Agent Reply Request Button Step 2 Feature Description
Agent replies currently depend on automatic post-load work or direct API calls, so a user cannot intentionally ask for an agent response from the page they are…
docs/plans/archive/agent_reply_request_button_step2_feature_description.md Plans Plans and history
-
Agent Reply Request Button Step 3 Development Plan
docs/plans/archive/agent_reply_request_button_step3_development_plan.md Plans Plans and history
-
Agent Reply Request Button Step 4 Implementation Summary
docs/plans/archive/agent_reply_request_button_step4_implementation_summary.md Plans Plans and history
-
All Activity Feed
Users need immediate confidence that every frontend action they take has been durably represented in the content repository and is visible in All Activity, inc…
docs/plans/archive/all_activity_feed_step1_solution_assessment.md Plans Plans and history
-
All Activity Feed
Users need confidence during demos and daily use that successful frontend actions were durably written to the content repository.
docs/plans/archive/all_activity_feed_step2_feature_description.md Plans Plans and history