Skip to content

Plan: GH-0023 Backend Release Blueprint

Context

This plan is the backend-only blueprint for the scrape -> ingest -> retrieve -> answer release path. It acts as the parent planning document for issues #24 through #32.

Problem

The repo has implementation docs and release notes, but it does not yet have a single issue-bound plan stub under docs/plans/ that can anchor the full backend release sequence.

Current state in repo

  • docs/90_ops/backend_release_todo.md defines the release issue set and order.
  • docs/90_ops/backend_blueprint_v1.md describes the end-to-end backend flow.
  • The codebase already contains implemented pieces for scraping, ingestion, retrieval, multilingual handling, and observability.

Target state

  • One canonical plan doc for issue #23 exists under docs/plans/.
  • The plan links the release scope, sequencing, and downstream issue docs.
  • The plan is explicitly scoped to the backend branch only.

Constraints

  • Scope is limited to app/, db/, tests/, and docs/.
  • admin/ and frontend work are out of scope.
  • The plan must remain useful to both human developers and AI coding assistants.
  • The plan should point to implementation work without duplicating implementation logs.

Proposed approach

  1. Capture the release objective, scope boundaries, and delivery order in one place.
  2. Link downstream issue plans for scraping, ingestion, retrieval, language handling, and verification.
  3. Use this plan as the top-level planning reference for PRs and later implementation docs.

Risks

  • The blueprint can drift if issue-specific docs evolve independently.
  • A broad parent plan can become vague if acceptance criteria stay too high level.

Open questions

  • Should this plan remain a living release doc or be frozen once all child issues are implemented?
  • Should MkDocs nav surface this plan directly or only through workflow pages?

Acceptance criteria

  • A plan doc exists for #23 under docs/plans/.
  • The doc states backend-only scope.
  • The doc names downstream issue groups and delivery order.
  • The doc can be referenced from future issue and implementation docs.

Files likely to change

  • docs/plans/gh-0023-backend-release-blueprint.md
  • docs/90_ops/backend_release_todo.md
  • docs/index.md
  • #23 - [Backend][Plan] Release blueprint for robust scrape->ingest->chat pipeline

Status

Backfilled planning stub