Feature Plans

This directory holds planning artifacts for current and recently completed work. New work follows Railspike: after Step 3 approval and branching, organize that feature in its own folder before the planning commit. Existing FDP cycles keep their approved process. Numbered plans are grouped by feature even when only some steps were recorded; step numbers retain their original workflow meaning. Missing steps are not reconstructed. Standalone assessments, checklists, and proposals remain at the top level or in the collections below.

Markdown work checklist — relevance-sorted completed work, acceptance, follow-ups and optional compatibility decisions.

Human-readable format audit — JSON conversion checklist and boundaries; retraction text assessment.

Production feedback

Retraction simplification handoff — current user direction, canceled sweep diagnostics plan, and coordination with registration and high-traffic work.

Profile registration cost and remediation — QDB incident evidence, global work hidden inside incremental registration, and proposed performance and recovery fixes.

Profile registration fix checklist — implementation and verification tasks, excluding incident containment.

Retraction sweep evidence diagnostics — historical production findings and failure-path inventory; the proposed diagnostics project is canceled (see the simplification handoff).

Request register — current tracking for migrated requests; intake and update guide. Older inventories are linked from the register and await reconciliation.

Feature folders

Other collections

When organizing a feature, use docs/plans/{feature_name}/, add it to this index, and repair its navigation and affected references. See the transition guide for existing FDP cycles.