Delivery Timeline
| Milestone | Effort (BE/FE/QA…) | Confidence | Progress | Target Date | Status |
|---|---|---|---|---|---|
| PRD v2.2 finalized | — | — | 0/0 | 2026-06-09 | Done |
| RFC review R2: Agentic-Ready / PROCEED | — | High | 0/0 | 2026-06-18 | Done |
| Engineering spec ready for in-repo chunks | — | High | 0/0 | 2026-06-18 | Done (GA waits on Launchpad dependency) |
| Development start | BE 10 / FE 10 / Mobile 10 / QA 7.5 | Medium | 0/37.5 (+ Design TBD) | 2026-Q3 | Planned (BE 1-7, FE 8-9, Mobile 10 executable) |
| Launchpad dependency delivered | — | — | 0/0 | TBD | Pending before GA — no committed date from Launchpad |
| QA E2E gate (Lane B — no automation substitute) | QA 7.5 | Medium | 0/7.5 | dev-complete ~2026-08-20 → GA 08-31 [derived] | Blocked-until Launchpad; for the 7.5d E2E to fit 08-31, dev must finish ~08-20 |
| Release | — | — | 0/0 | 2026-Q3 | Planned (gated on Launchpad delivery + effort forecast) |
RFC Readiness Notes
rfc-reviewerR2 on 2026-06-18 scored the RFC 8.5/10,Agentic-Ready, verdictPROCEED.- The prior blocker around the teams-for-user(+descendants) contract is closed in the RFC: the dependency contract is pinned in §2.4 and all in-repo chunks are executable.
- GA still waits on Launchpad shipping the teams-for-user endpoint and Team Only radio; that is a delivery dependency, not an RFC/spec gap.
- Backend effort is confirmed by Ghozi: 10 man-days (2 man-weeks, incl. 1 man-week buffer).
Frontend (Azani, 10 man-days = 2 man-weeks), Mobile (Alfi, 10 man-days = 2 man-weeks / 10 SP), and
QA (Hendry, 7.5 man-days) are now confirmed. Design man-days and the overall forecast remain
TBDuntil Design confirms, soeffort_total_daysstaysTBD(BE 10 + FE 10 + Mobile 10 + QA 7.5 = 37.5 so far).
Staffing
Implementors for RFC: Enable Team Owner Field & Team Permission in CDP:
| Discipline | Implementor |
|---|---|
| Backend | Ghozi |
| Frontend | Azani |
| Mobile | Alfi |
| QA | Hendry (primary), Izzul (backup) |
Capacity & Allocation
Per-discipline committed days for this initiative, mirrored from the initiative README. BE confirmed
by Ghozi; FE (Azani) and Mobile (Alfi) confirmed at 2 man-weeks each; QA (Hendry) confirmed at 7.5;
Design still TBD. Sequencing follows the 2026-Q3 policy in
cdp/delivery/roadmap.md. QA defaults to Hendry, Izzul backup.
Forecast remains TBD until Design man-days and the Launchpad dependency are confirmed. Lane-B
QA-driven finish-by (derived): for the 7.5d final E2E (no automation substitute) to fit the 08-31
commitment, dev must complete by ~08-20 — currently blocked-until Launchpad, which has no
committed date, so 08-31 is at risk on both the Launchpad gate and this QA gate. Hendry's 7.5d here
also collides with the two migrations' E2E in the same 08-20→09-07 window — see
capacity.md.
| Implementor | Discipline | Committed days (this initiative) | Window |
|---|---|---|---|
| Ghozi | Backend | 10 | 2026-Q3 |
| Azani | Frontend | 10 | 2026-Q3 |
| Alfi | Mobile | 10 | 2026-Q3 |
| Hendry | QA | 7.5 | 2026-Q3 |
Dependencies & gates
- 🔴 Launchpad — teams-for-user(+descendants) API to the §2.4 contract; must land before flag-ON GA.
- 🔴 Launchpad (⚠️ or Admin Portal — confirm owner) —
teamradio in permission settings UI (CHG-001); prerequisite for an admin to enable TEAM ONLY. - 🔴 Launchpad + CDP — legacy→Launchpad team-name crosswalk (migration); needs building.
- 🔴 Mobile Squad — CDP module renders the Team Owner field + per-note permission flags.
- ✅ Launchpad — level-update endpoint, team-hierarchy traversal, and
crs_permissionsper-action level all verified to exist.
Internal critical path: in-repo BE chunks 1–7 → FE chunks 8–9 → Mobile chunk 10 (all buildable now against the pinned §2.4 contract) → CDP backfill job (CHG-004) + feature-flag wiring (CHG-005); deploy BE → FE → flag-ON, but flag-ON GA waits on the Launchpad deliverables above.