23 — Release Plan & Milestones (Blueprint §9)

23 — Release Plan & Milestones (Blueprint §9)

Source: 02-Implementation-Blueprint.md — §9) Release Plan (Milestones).

Product alignment: 01-Post-Purchase-Video-Testimonial-Collector-Plan.md — phased MVP delivery from automation foundation to storefront impact.

This document is a build spec only. No code changes are implied until a task references this file.

Related: all implementation plans 05 through 22.

---

0) Goal (one sentence)

Turn the blueprint’s 3 milestone bullets into a practical execution plan with clear dependencies, acceptance gates, QA, and production rollout controls.

---

1) Milestone definitions from blueprint

Milestone 1 (2 weeks)

• DB schema + migrations
• Campaign CRUD
• Request creation from order webhook

Milestone 2 (2 weeks)

• Public token page
• Media upload + storage
• Moderation inbox and detail page

Milestone 3 (2 weeks)

• Theme widget rendering (home + PDP)
• Widget storefront API
• Analytics + billing limits
• App Store readiness and QA

This plan preserves those milestones and adds delivery rigor.

---

2) Dependency graph (must be respected)

Capability	Depends on
Campaign CRUD	DB schema for campaign models
Request creation	Campaign CRUD + webhook auth/idempotency
Public submission page	Request rows + token generation
Media upload/storage	Submission APIs + storage adapter
Moderation inbox/detail	Submission + media metadata + moderation logs
Published content controls	Moderation + publish fields
Widget API + theme blocks	Published rules + placement flags
Analytics	Requests/submissions/events data
Billing limits	Usage meters + plan config

Do not begin Milestone 3 storefront exposure before moderation/publication rules are stable.

---

3) Milestone 1 detailed execution

3.1 Scope

1. Implement testimonial schema foundations (20).
2. Implement campaigns list/create-edit (17, 18).
3. Implement webhook intake + request row creation (07, partial).

3.2 Exit criteria

• Prisma migrations apply cleanly on dev + staging.
• Merchant can create active campaign with valid targeting.
• Order webhook creates correct per-product request rows idempotently.
• TestimonialRequest rows contain token + submission URL + scheduled time.

3.3 QA checklist

• replay webhook does not duplicate requests
• inactive campaign produces zero rows
• one order with 3 eligible line items yields 3 request rows

3.4 Rollback strategy

• If webhook processing causes bad rows, disable webhook route via feature flag and keep campaign UI active.

---

4) Milestone 2 detailed execution

4.1 Scope

1. Public token page + submit APIs (06).
2. Signed upload path + media persistence.
3. Moderation screens (09, 10) and moderation settings baseline (12).

4.2 Exit criteria

• Customer can submit via /t/:token with consent required.
• Media upload succeeds and links to submission.
• Submission appears in pending inbox immediately.
• Merchant can approve/reject from detail with moderation log entry.

4.3 QA checklist

• expired/invalid token handling
• duplicate submit prevented
• media processing status visible
• cross-shop access blocked for admin routes

4.4 Rollback strategy

• If upload provider fails, keep submission form available with graceful “try again” and disable final submit until upload complete.

---

5) Milestone 3 detailed execution

5.1 Scope

1. Published content manager + placement controls (11).
2. Widget settings + public read API + theme blocks (05).
3. Requests log, analytics, billing (13, 14, 15, and dashboard 19).
4. Security/compliance hardening (08).

5.2 Exit criteria

• Home widget shows top configured published items.
• PDP widget shows product-scoped testimonials with fallback behavior.
• Analytics and billing screens show non-empty, validated metrics.
• GDPR handlers cover testimonial tables.
• App passes internal launch QA checklist.

5.3 QA checklist

• storefront widget performance and mobile behavior
• placement toggles reflected in API results
• unpublish removes content from storefront immediately
• billing usage counters reconcile with source data

5.4 Rollback strategy

• Feature-flag public widget API and theme block rendering separately from admin.
• If storefront issue found, disable widget API while preserving moderation/admin.

---

6) Cross-milestone quality gates

Before promoting each milestone to production:

1. Schema gate: migrations tested on production-like snapshot.
2. Security gate: token, rate limit, and auth checks verified (08).
3. Data gate: sample datasets validate KPI/billing math.
4. Support gate: runbook updated for common failures.

---

7) Environment and deployment strategy

7.1 Environments

• Local dev
• Staging with real Shopify test store
• Production

7.2 Release mechanism

• Merge by milestone branch or by vertical slices behind feature flags.
• Suggested flags:
  • TESTIMONIAL_PIPELINE_ENABLED
  • TESTIMONIAL_PUBLIC_SUBMIT_ENABLED
  • TESTIMONIAL_WIDGET_ENABLED

7.3 Migration timing

• Apply DB migrations before enabling dependent flags.
• Never enable webhook creation logic before schema is live.

---

8) Risk register (top items)

1. Webhook duplicates -> over-requesting customers.
   • Mitigation: idempotency keys + unique constraints.
2. Media processing failures -> empty moderation previews.
   • Mitigation: asset status + retry/backoff + clear UI states.
3. Incorrect publication filters -> private/unapproved content leaks.
   • Mitigation: strict API predicates (approved && published && ready).
4. Billing counter drift -> merchant trust loss.
   • Mitigation: reconciliation job + transparent logs.
5. GDPR gaps -> compliance risk.
   • Mitigation: explicit redact tests before milestone 3 release.

---

9) Team execution checklist by role

Backend

• schema + webhook + workers + APIs + reconciliation

Frontend/admin

• campaigns/templates/moderation/published/analytics/billing UIs

Theme extension

• home/pdp blocks + storefront JS

QA

• end-to-end flows per milestone + regression matrix

Ops

• cron schedules, provider credentials, alerting

---

10) Definition of done (program-level)

All of the following must be true:

• Milestone 1/2/3 exit criteria complete.
• Security/compliance tests pass.
• Support and troubleshooting docs updated.
• Feature flags can disable public surfaces safely.
• Merchant-facing flows validated on at least 2 test stores.

---

11) Suggested implementation order (from existing plans)

1. 04 cleanup baseline
2. 20 schema
3. 17 + 18 campaigns
4. 16 templates
5. 07 request pipeline
6. 06 public submission
7. 12 moderation settings + 09 + 10
8. 11 published manager
9. 05 widgets/read API
10. 13 + 14 + 15 + 19
11. 08 compliance hardening
12. 22 final integration verification

---

12) References

• 02-Implementation-Blueprint.md — Section 9
• 01-Post-Purchase-Video-Testimonial-Collector-Plan.md — MVP feature scope
• 05–22 docs in this folder

---

13) Note on numbering

This folder already includes 05 through 22 plans. This file is 23-....