-
docs_independent_publication_step4_implementation_summary.md
Restored inherited state: Step 3 approval, planning and Stages 1–6 commits, enabled debug, R1/P2 study history and pending bookkeeping were reconciled before S…
docs/plans/docs_independent_publication/docs_independent_publication_step4_implementation_summary.md Plans
-
stage1_boundary_evidence.json
docs/plans/docs_independent_publication/stage1_boundary_evidence.json Plans
-
stage7_acceptance_evidence.json
docs/plans/docs_independent_publication/stage7_acceptance_evidence.json Plans
-
docs_landing_contrast_audit.json
docs/plans/docs_landing/docs_landing_contrast_audit.json Plans
-
docs_landing Railspike debug log
docs/plans/docs_landing/docs_landing_debug_log.md Plans
-
docs_landing_rendered_contrast.json
docs/plans/docs_landing/docs_landing_rendered_contrast.json Plans
-
docs_landing_step1_solution_assessment.md
Follow-up cycle: predecessor docsdiscovery; intended reused branch feature/docs-discovery (unmerged).
docs/plans/docs_landing/docs_landing_step1_solution_assessment.md Plans
-
docs_landing_step2_feature_description.md
Follow-up cycle: predecessor docsdiscovery; intended reused branch feature/docs-discovery (unmerged).
docs/plans/docs_landing/docs_landing_step2_feature_description.md Plans
-
docs_landing_step3_development_plan.md
Follow-up cycle: predecessor docsdiscovery; reused branch feature/docs-discovery (unmerged).
docs/plans/docs_landing/docs_landing_step3_development_plan.md Plans
-
docs_landing_step4_implementation_summary.md
Follow-up cycle: predecessor docsdiscovery; reused branch feature/docs-discovery (unmerged).
docs/plans/docs_landing/docs_landing_step4_implementation_summary.md Plans
-
Documentation publication policy — Railspike debug log
Verification: source and existing requirements reviewed; R1 hashes matched; planning changes only.
docs/plans/docs_publication_policy/docs_publication_policy_debug_log.md Plans
-
docs_publication_policy_step1_solution_assessment.md
Effort study: railspike-effort / v3/docspublicationpolicy, standing enrollment P2; host ledger.
docs/plans/docs_publication_policy/docs_publication_policy_step1_solution_assessment.md Plans
-
docs_publication_policy_step2_feature_description.md
Effort study: railspike-effort / v3/docspublicationpolicy, standing enrollment P2; host ledger.
docs/plans/docs_publication_policy/docs_publication_policy_step2_feature_description.md Plans
-
docs_publication_policy_step3_development_plan.md
Effort study: railspike-effort / v3/docspublicationpolicy, standing enrollment P2; host ledger.
docs/plans/docs_publication_policy/docs_publication_policy_step3_development_plan.md Plans
-
docs_publication_policy_step4_implementation_summary.md
Effort study: railspike-effort / v3/docspublicationpolicy, standing enrollment P2; host ledger.
docs/plans/docs_publication_policy/docs_publication_policy_step4_implementation_summary.md Plans
-
docs_publication_policy_verification.json
docs/plans/docs_publication_policy/docs_publication_policy_verification.json Plans
-
Effort estimation trial ledger
2026-10-25 UTC — standing P2 enrollment; canonical intake and Step 1 snapshots.
docs/plans/effort_estimation_trial.md Plans
-
Effort estimation trial debug log
No supported findings.
docs/plans/effort_estimation_trial/effort_estimation_trial_debug_log.md Plans
-
Prospective effort estimation trial — solution assessment
Can you please write a Step 1 plan, using the Step 2 plan as point to reverse from
docs/plans/effort_estimation_trial/effort_estimation_trial_step1_solution_assessment.md Plans
-
Prospective effort estimation trial
The calibration study proposes retrospective reference scores, but v3 needs prospective evidence of whether those scores help scope work comfortably into Rails…
docs/plans/effort_estimation_trial/effort_estimation_trial_step2_feature_description.md Plans
-
Effort estimation trial — development plan
Deliver documentation-only setup for the maintainer and future agents: a resumable ledger, six useful proposed scopes with preserved estimates, and vendored Ra…
docs/plans/effort_estimation_trial/effort_estimation_trial_step3_development_plan.md Plans
-
Effort estimation trial — implementation summary
Step 3 explicitly approved by the user.
docs/plans/effort_estimation_trial/effort_estimation_trial_step4_implementation_summary.md Plans
-
Effort estimation study — your checklist
Current position: setup is complete on feat/effort-estimation-trial.
docs/plans/effort_estimation_trial_maintainer_checklist.md Plans
-
Ephemeral Testing: Candidate Targets
Source: todo.txt item "identify targets for ephemeral testing", which references
docs/plans/ephemeral_testing_targets.md Plans
-
Ephemeral Testing: Task Descriptions and Agent Prompts
Companion to ephemeraltestingtargets.md.
docs/plans/ephemeral_testing_tasks.md Plans
-
event_feature_gating_step1_solution_assessment.md
We recently added an event feature, and it seems to now be available on all sites, which was not the original intent.
docs/plans/event_feature_gating/event_feature_gating_step1_solution_assessment.md Plans
-
event_feature_gating_step2_feature_description.md
The shared thread composer and shared thread rendering currently expose event support on every site.
docs/plans/event_feature_gating/event_feature_gating_step2_feature_description.md Plans
-
event_feature_gating_step3_development_plan.md
Waiting for "Approved Step 3" before branching and starting Step 4.
docs/plans/event_feature_gating/event_feature_gating_step3_development_plan.md Plans
-
event_feature_gating_step4_implementation_summary.md
docs/plans/event_feature_gating/event_feature_gating_step4_implementation_summary.md Plans
-
event_time_step1_solution_assessment.md
Please add event time and duration to the event framework.
docs/plans/event_time/event_time_step1_solution_assessment.md Plans
-
event_time_step2_feature_description.md
An event thread can only carry a date, location, and link — never a start time — and the compose form's date field is a plain text box with no native picker, s…
docs/plans/event_time/event_time_step2_feature_description.md Plans
-
event_time_step3_development_plan.md
2026-11-14 at 19:00); renders exactly as today when absent.
docs/plans/event_time/event_time_step3_development_plan.md Plans
-
event_time_step4_implementation_summary.md
2026-11-20 at 19:30 · MIT Media Lab, E14 · https://example.com/cypher-night-2, confirming the time renders correctly on both surfaces (closing the two-surfaces…
docs/plans/event_time/event_time_step4_implementation_summary.md Plans
-
Extension/Improvement Cookbook Step 1 Solution Assessment
Developers cannot readily see how the site’s existing architecture supports safe, practical feature extensions, especially LLM- and agent-assisted workflows.
docs/plans/extension_improvement_cookbook/extension_improvement_cookbook_step1_solution_assessment.md Plans
-
Extension/Improvement Cookbook Step 2 Feature Description
The site’s extension facilities are capable but not discoverable through concrete examples.
docs/plans/extension_improvement_cookbook/extension_improvement_cookbook_step2_feature_description.md Plans
-
Extension/Improvement Cookbook Step 3 Development Plan
docs/plans/extension_improvement_cookbook/extension_improvement_cookbook_step3_development_plan.md Plans
-
Extension/Improvement Cookbook Step 4 Implementation Summary
docs/plans/extension_improvement_cookbook/extension_improvement_cookbook_step4_implementation_summary.md Plans
-
Fastmod Audit and Backfill Step 1 Solution Assessment
Operators need to measure unscored historical content and its estimated Fastmod
docs/plans/fastmod_audit_backfill/fastmod_audit_backfill_step1_solution_assessment.md Plans
-
Fastmod Audit and Backfill Step 2 Feature Description
Fastmod intentionally rates only newly published content, so operators cannot
docs/plans/fastmod_audit_backfill/fastmod_audit_backfill_step2_feature_description.md Plans
-
Fastmod Audit and Backfill Step 3 Development Plan
If this plan is accepted, reply Approved Step 3.
docs/plans/fastmod_audit_backfill/fastmod_audit_backfill_step3_development_plan.md Plans