Work-in-progress — design surface migration

Where to find what

This project is in a hybrid state. It started before the workbook convention was introduced (2026-05-16) so the original analysis material lives in this directory. From 2026-05-18 onward, the project follows a new split:

• Project-level material — goal, PDEV-442-scoped analyses, implementation specs — stays here in the documentation site. These remain the source-of-product and will be promoted to roadmap/completed/ when the project closes.
• Per-PDEV design work — design discussions, candidate cards, decisions, changesets, and sequencing — moved into the workbook. The workbook is the source-of-process.

The two are linked: when a per-PDEV design discussion converges to a decision worth publishing alongside the project record, the workbook entry is promoted into this documentation site. The reverse does not happen — the workbook is not a mirror of the documentation site.

Active workbook surface

• Workbook root: workbooks/notebooks/product-slow-responses/
  • index.md — project framing, retrofit notes.
  • work-board.md — open threads and operational items (former CT-NNN entries now T4–T16).
  • threads/ — extracted sub-discussions (T17–T25 currently).
  • decisions/ — formal resolutions (T22-aws-jdbc-wrapper-adoption.md, C8-summary-for-items-supersedes-for-item.md, C23-C24-pdev-509-tests-in-common-module.md).
  • pdev-490/
    • context.md — PDEV-490 May-2026 landscape (superseded analysis/pdev-490/goal.md).
    • candidates/ — K01–K16 candidate cards.
    • changesets/ — functional-group implementation guides:
      • common-module-changes.md — Aurora connectivity via the AWS Advanced JDBC Wrapper.
      • items-module-changes.md — bitemporal indexes + pool tuning on the item DB.
      • kanban-module-changes.md — summary/for-items route, indexes, and the listWithDetails refactor.
      • operations-component-configuration.md — version bump, retry knobs, Flyway audit.
      • change-sequencing.md — unified OP / C / K / T vocabulary + wave plan.

What was retired

The directory analysis/pdev-490/ (this site) contained goal.md and impact-assessment.md. Both were superseded by the workbook on 2026-05-18:

• goal.md content carried into workbooks/notebooks/product-slow-responses/pdev-490/context.md (May-2026 landscape) and into individual candidate cards (K01–K16). The PDEV-509 addendum content moved into workbooks/notebooks/product-slow-responses/pdev-490/changesets/common-module-changes.md.
• impact-assessment.md’s C1–C25 attribution rows are now represented as candidate cards (K-NN, one per row) plus decisions. The C ↔ K mapping table lives in workbooks/notebooks/product-slow-responses/pdev-490/changesets/change-sequencing.md.

The sibling files in this directory’s parent analysis/ directory (be-findings.md, fe-findings.md, operations-bottlenecks.md, code-dig.md, infrastructure-improvements.md, sentry-configuration.md, db-configuration.md, db-init.md, pod_capacity.md) are PDEV-442-scoped, not PDEV-490-scoped, and remain here unchanged.

What this means for new work

• Adding a design discussion → workbook (threads/ or work-board.md).
• Recording a design decision → workbook (decisions/).
• Authoring an implementation guide → workbook (pdev-490/changesets/).
• Adding a candidate change → workbook (pdev-490/candidates/).
• Promoting decided design content for publication → curate and add to the appropriate page under this documentation directory.

This is a meta-process choice for the current phase. The project will continue to evolve the split based on what proves useful at project close.