Delivery Timeline
| Milestone | Effort (BE/FE/QA…) | Confidence | Progress | Target Date | Status |
|---|---|---|---|---|---|
| PRD v1.1 finalized | — | — | 0/0 | 2026-06-09 | Done |
| OQ-1: notification contract verified | — | — | 0/0 | 2026-06-22 | Done |
| OQ-7: editor path decided for build | — | — | 0/0 | 2026-06-22 | Done (fallback pre-committed; spike may optimize) |
| RFC R3 review: Agentic-Ready / PROCEED | — | High | 0/0 | 2026-06-22 | Done |
| OQ-14: Figma for typeahead picker + chip | — | — | 0/0 | TBD | Pending (blocks web composer/chip visual) |
| OQ-17: web deep-link to Notes tab | FE 1 / QA 0.5 | Medium | 0/1.5 | 2026-Q3 | Planned |
| REV-14: lock-screen PII infosec ack | — | — | 0/0 | TBD | Pending before GA |
| Development start | BE 10 / FE 9.5 / Mobile 10 / QA 4.5 | Medium | 0/34 | 2026-Q3 | Planned (9/10 chunks unblocked) |
| Release | 34 total | Medium | 0/34 | 2026-Q3 | Planned (gated on OQ-14 + infosec ack) |
RFC Readiness Notes
rfc-reviewerR3 on 2026-06-22 scored the RFC 8.5/10,Agentic-Ready, verdictPROCEED; the notification-service contract is verified and prior notification blockers are fixed.- Remaining delivery gates are OQ-14 Figma for the web composer/chip visual, OQ-17 web deep-link wiring, and REV-14 infosec acknowledgement for mobile lock-screen PII.
Staffing
Implementors for RFC: Mention User in CDP Notes:
| Discipline | Implementor |
|---|---|
| Backend | Berlianto |
| Frontend | Jovi |
| Mobile | Alfi |
| QA | Hendry (primary), Izzul (backup) |
Capacity & Allocation
This initiative's effort is sourced from
rfc-notes-mention-user.task-breakdown.md
and mirrored from the initiative README. Sequencing follows the 2026-Q3 policy in
cdp/delivery/roadmap.md. QA is assigned to Hendry by default, with
Izzul used only as backup if timeline clashes. Forecast p85 is 2026-08-19 (p50 2026-08-10),
mirrored from the initiative README; it firms up further as remaining release gates close.
FE effort is now confirmed by Jovi at 9.5 days (was 6, the rfc-task-breakdown estimate) — +3.5 days added to the BE-first critical path, which pushes the forecast out from p50 2026-08-05 / p85 2026-08-14. This widens the already-flagged miss against the 2026-07-14 commitment to ~4 weeks.
Mobile effort is estimated by Alfi at 2 man-weeks (10 days), overriding the earlier
verify-only 0. The mobile ticket is 12 SP including a +2 SP bugfix placeholder carried from
this quarter's note-cdp init; that placeholder is likely not picked up this quarter (its
testing slips to next Q), so it is excluded from the firm 10-day capture and flagged here as the
single source of mobile-effort uncertainty.
| Implementor | Discipline | Committed days (this initiative) | Window |
|---|---|---|---|
| Berlianto | Backend | 10 | 2026-Q3 |
| Jovi | Frontend | 9.5 | 2026-Q3 |
| Alfi | Mobile | 10 | 2026-Q3 |
| Hendry | QA | 4.5 | 2026-Q3 |
Dependencies & gates
- 🔴 Design System — web Figma frames for the mention typeahead picker + chip (OQ-14); gates the web composer/chip visual (§4.D chunk 7). Only build blocker.
- 🟡 Infosec — approval of the bluemonday allow-list + mobile lock-screen PII egress before AGREED/GA (OQ-19, REV-14).
- 🟡 Notification/Platform — category choice: reuse generic
mention(2)vs a CDP-specific category (OQ-1); reuse is sufficient for v1, non-blocking. - ✅ Notification/Platform · Mobile · Launchpad — notification-service
/crmendpoint, Web Notification Center, Mobile One Notification V2 routing, and company-scoped user search all verified 2026-06-22.
Internal critical path: BE dark-deploy (schema → parser → sanitizer → async dispatch, chunks 1–5, flag OFF) → FE composer/renderer (chunk 7, after OQ-14) + mobile anchor mapper (chunk 8) → flag-ON GA.