Skip to content

Plans

This directory holds forward-looking backend design and implementation plans.

Naming convention:

  • Legacy plans may use date-based filenames.
  • Issue-bound plans use gh-####-<slug>.md.
  • The gh-#### prefix should match the GitHub issue number so planning and implementation docs can be linked mechanically.
  • Older issue-<number>-<slug>.md files may still exist in a local working tree, but gh-####-<slug>.md is the preferred convention going forward.

Current plan files include legacy date-based plans and issue-bound plans for backend work.

Use plan documents for:

  • scoped design work
  • implementation sequencing
  • tradeoff analysis before code lands

Do not treat plan files as the current implementation truth after code diverges. When implementation lands, update the active architecture and runbook pages under the main docs tree.