Skip to main content

One CID Multiple WABA — Status 2026-07-19

Delivery / Program Management — periodic status report. Resolves sprint-resync F-1 (blocked-done-conflict, escalated across 7 passes) via decision 0001 and records the underlying code-evidence audit that decision is based on.

Summary​

F-1 resolved, not by either of its original two options. BIF-6428 is genuinely this initiative's epic (its 7 child Stories map 1:1 onto the RFC's WABA-S01..S07) and most of its child Tasks are legitimately Done and code-corroborated — but the epic-level status: Done concealed that all 7 parent Stories still sit at Waiting Confirmation, one Task (BIF-7223, Shared Balance Tooltip) is marked Done with no corresponding code, and the initiative's core mechanism (letting 2+ WABAs share one balance pool) is still structurally blocked. A new Epic, BIF-8910 ("26Q3 BIF – One CID Multiple WABA Rollout"), now owns the 26Q3 remainder.

progress_pct stays 0 here because it mirrors the RFC Phase-1 task-breakdown's own tracked scope (25.5 md — rfc-one-cid-multiple-waba-phase-1.task-breakdown.md), which is genuinely 0% code-corroborated. That figure understates overall initiative maturity — substantial adjacent work already shipped under BIF-6428 outside the RFC's tracked breakdown (see below) — but overstates it to round it up without a re-scoped, re-estimated breakdown against BIF-8910's actual remaining scope, which is TPM/DRI's next step, not this report's.

Code-evidence audit (2026-07-19)​

Audited against the RFC's 11-task breakdown and BIF-6428's child Stories/Tasks across qontak-billing, hub-core, hub-service, hub-chat:

  • Done + code-corroborated: organization_package_id FK column (BIF-7169/7170 — migration 20260113000000_add_organization_package_id_to_whatsapp_packages in qontak-billing), WABA-ID lookup + feature-flagged package lookup (BIF-7172/7173), contract renewal carry-over (BIF-7200), Postpaid Limit reset/aggregation (BIF-7204), waba_id in Broadcast/Conversation reports + CSV export incl. FE columns and QA execution (BIF-7210–7216 — hub-service PR #2811, hub-chat PR #1773), low-balance threshold update for the shared pool (BIF-7221).
  • Falsely marked Done: BIF-7223 "View Shared Balance Tooltip" — the only commit referencing it (hub-chat 16343de66) only adds waba_id report columns; no SharedBalanceTooltip component exists in hub-chat.
  • Explicitly descoped (Won't Fix): aggregated balance display component, balance transaction history page, several QA test-plan tasks.
  • 🔴 Critical, unstarted: the 20260113000000 migration created idx_whatsapp_packages_organization_package_id as UNIQUE — 2+ WABAs still cannot share one pool, the initiative's core value proposition (RFC Phase-1 Tasks 3/4, 5.0 md). Also unstarted: net-new balance_below_zero alert (qontak-billing), billing_version/show_waba_id store gating and the MCC filter/tooltip/banner FE components (hub-chat, blocked on RFC Detail 2.F).

Next steps​

  • DRI/TPM to size BIF-8910's actual remaining scope (the critical index/sharing gap first) and re-baseline effort/forecast on the initiative README once sized.
  • FE owner + Design to close RFC Detail 2.F (component contracts/frames) — still the sole blocker for the FE polish items and 6.5 of the RFC's original 7 FE days.
  • Next sprint-resync pass: close F-1 against this record; re-derive Grehasta/Syafrizal M./Izzul's queue rows against BIF-8910 instead of the stale BIF-6428 Done-conflict framing.