Skip to content

ADR 0029: MVP release readiness is a documented evidence matrix

Status

Accepted. Apple application identity remains ADR 0028.

Context

04_MVP §11 defines when Duckbill™ is complete. Kickoff §11–12 says documentation stays requirements truth and Jira stays the work plan. MAIL-49 / MAIL-62 require every §11 criterion to map to evidence (ticket plus live URL or test), and 04_MVP §3 items to stay out of the release.

Sprint 07 runs three concurrent streams. Stream A (MAIL-50 / MAIL-103) owns the live mailbox path. Stream B (MAIL-51 / MAIL-109) owns NFR gates from 03_NFR §16. Stream C owns operator docs and the matrix. Declaring MVP complete from documentation alone would hide missing E2E and NFR evidence. Implementing those suites here would expand scope.

ENABLE_SEND stays off (ADR 0003). No secrets belong in git, docs, or Jira.

Decision

  1. Store the MVP release checklist in docs/operations/mvp-release.md. Jira tracks work; the checklist maps 04_MVP §11 to MAIL keys and URLs.
  2. Every §11 bullet must have at least one MAIL key and a live documentation/product URL or an automated test. Rows that still need Stream A or Stream B results cite MAIL-103 or MAIL-109 and leave TODOs for those evidence pages. A TODO is not a pass.
  3. Record 04_MVP §3 items, plus the operator list (custom mail client, iOS app, calendar product, contact consolidation, full composer/send, autonomous AI send/delete, bulk historical migration execution), as NOT done.
  4. Keep ENABLE_SEND off on preview and production. Do not document secret values.
  5. Do not close epic MAIL-12 from this decision. Close MAIL-62 / MAIL-118 / MAIL-49 together after the checklist is live and reviewed.

Alternatives

Consequences

Operators review MVP release checklist and deploy and operate. Preview URL: https://duckbill-dev.jasonkoch.io/docs/operations/mvp-release. Production URL: https://duckbill.jasonkoch.io/docs/operations/mvp-release. The matrix stays incomplete until MAIL-103 and MAIL-109 publish their evidence.