Delivery Timeline
| Milestone | Effort (BE/FE/QA…) | Confidence | Progress | Target Date | Status |
|---|---|---|---|---|---|
| PRD finalized | — | — | 0/0 | TBD | Pending |
| RFC + task-breakdown | BE 2.5 · FE 2 · QA 2 | medium | 0/6.5 | 2026-07-01 | Done (BE agent-execution-ready; OQ-2 authorization sign-off pending) |
| Development start | BE 2.5 · FE 2 · QA 2 | medium | 0/6.5 | TBD | FE queue slot resolved (resequenced 2026-07-01 — runs after Qontak One Team, ahead of Centralized SSO Token); still blocked on OQ-2 + QA sequencing |
| Release | 6.5 total | medium | 0/6.5 | TBD | Planned |
Dependencies & gates
- 🟡 OQ-2 (authorization) — infosec sign-off pending.
PUT /billings/extrasis today writable by any orgadmin/owner/supervisor/agent/member, not Ops-only as the PRD intends. Task 3 (BE key allowlist, 1.5 md incl. QA) is gated on this deciding Option B (gate the write); drops entirely if Option C (accept self-enable) is chosen. Owner: bifrost + infosec. - ✅ FE schedule slot — resolved 2026-07-01 (EM decision). Syafrizal M. is staffed and his
queue was resequenced so this initiative's FE runs right after Qontak One Team, ahead of
Centralized SSO Token (
Self-Subs → Lite → Qontak One Team → Sales Invoice + Jurnal → Centralized SSO Token), instead of being stuck behind the 37-day SSO build. He remains at exactly 1.00 capacity — see../../delivery/capacity.md. This pushes Centralized SSO Token's own FE start back ~3.5 md; see itsdelivery/timeline.mdfor that consequence. - 🟡 Frontend design pending — no Figma yet (RFC OQ-1); FE logic is buildable but final styling/placement awaits design, and execution needs a hub-chat consumer RFC.