Skip to main content

Delivery Timeline

MilestoneEffort (BE/FE/QA…)ConfidenceProgressTarget DateStatus
PRD v1.1 finalized0/02026-06-09Done
OQ-1: notification contract verified0/02026-06-22Done
OQ-7: editor path decided for build0/02026-06-22Done (fallback pre-committed; spike may optimize)
RFC R3 review: Agentic-Ready / PROCEEDHigh0/02026-06-22Done
OQ-14: Figma for typeahead picker + chip0/0TBDPending (blocks web composer/chip visual)
OQ-17: web deep-link to Notes tabFE 1 / QA 0.5Medium0/1.52026-Q3Planned
REV-14: lock-screen PII infosec ack0/0TBDPending before GA
Development startBE 10 / FE 9.5 / Mobile 10 / QA 4.5Medium0/342026-Q3Planned (9/10 chunks unblocked)
QA E2E gate (Lane B — no automation substitute)QA 4.5Medium0/4.5dev-complete ~2026-08-08 → GA 08-14 [derived]At risk — dev p50 08-10 already trails the finish-by; p85 08-19 → GA ~08-25 (misses 08-14 by ~11d)
Release34 totalMedium0/342026-Q3Planned (gated on OQ-14 + infosec ack)

RFC Readiness Notes

  • rfc-reviewer R3 on 2026-06-22 scored the RFC 8.5/10, Agentic-Ready, verdict PROCEED; 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:

DisciplineImplementor
BackendBerlianto
FrontendJovi
MobileAlfi
QAHendry (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 confirmed by Jovi at 9.5 days (was 6); the +3.5-day forecast slip to p85 2026-08-19 is narrated in status/2026-07-01. Lane-B QA-driven finish-by (derived): the 4.5d final E2E has no automation substitute and trails dev, so for GA by the 08-14 commitment dev must complete by ~08-08; dev p50 08-10 already trails that, so 08-14 is at risk on the QA gate (not only on dev). Mobile 10 days (Alfi); the +2 SP bugfix placeholder likely slipping to next quarter is the one mobile-effort uncertainty — see capacity.md.

ImplementorDisciplineCommitted days (this initiative)Window
BerliantoBackend102026-Q3
JoviFrontend9.52026-Q3
AlfiMobile102026-Q3
HendryQA4.52026-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 /crm endpoint, 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.