0002 — WABA-S0x Story clones under BIF-8910, with per-story done/not-done reconciliation

Delivery / Program Management — decision record (ADR-style).

Context

Decision record 0001-jira-done-plan-open-conflict.md established that Epic BIF-6428 (closed, 26Q1 phase) holds the 7 original Stories (BIF-6919–BIF-6925, one per WABA-S01–WABA-S07), all still Waiting Confirmation, and that the live 26Q3 Epic BIF-8910 is where the remaining work belongs. A jira-alignment-check pass (2026-07-22) found only 1 of the 7 WABA-Sxx Stories (WABA-S04 → BIF-8963) existed under BIF-8910 — the other 6 were flagged as a per-user-story alignment gap (D4) and deliberately held pending a DRI/human call on how to resolve it, since simply creating 6 fresh, empty Stories would have discarded the real (and uneven) completion evidence already recorded against the legacy Stories' child Tasks.

A direct read of BIF-6428's Task tree (grouped by Work item split links to each of the 7 legacy Stories) shows the actual per-story state is not uniform:

Story	Legacy ref	Dev evidence
WABA-S01 — WABI Monthly Reset & Priority	BIF-6919	All 3 child tasks Won't Fix — no shared-pool WABI reset work tracked as Done
WABA-S02 — WAB-Additional Purchase & Carry-Over	BIF-6920	BE carry-over Done (BIF-7200); 3 QA tasks Won't Fix
WABA-S03 — Postpaid Limit Configuration & Blocking	BIF-6921	BE reset/aggregation Done (BIF-7204); 2 QA tasks Won't Fix
WABA-S04 — Multi-Bucket Balance Deduction Hierarchy	BIF-6922	Column/lookup/package-logic Done; backfill + FE aggregated display Won't Fix; blocking unique-index gap still open — already re-tracked as fresh BIF-8963/BIF-8971
WABA-S05 — WABA ID Column in Usage Reports	BIF-6923	7 tasks + 2 bugfixes Done, code-corroborated; only broad API/E2E QA tasks Won't Fix; MCC filter dropdown (AC-3/4) untracked
WABA-S06 — Company-Level Low Balance Notifications	BIF-6924	BE threshold logic Done (BIF-7221); QA Won't Fix; balance_below_zero event + LowBalanceBanner not built
WABA-S07 — Shared Balance Tooltip	BIF-6925	BIF-7223 marked Done but falsely — no SharedBalanceTooltip component exists in hub-chat (per 0001)

Decision

We will create one new Jira Story per missing WABA-Sxx under BIF-8910 (WABA-S01, S02, S03, S05, S06, S07 — S04 already exists as BIF-8963), each carrying:

1. The PRD user-story statement and a pointer to its full ACs in bifrost/one-cid-multiple-waba/prds/prd-one-cid-multiple-waba-phase-1.md §8.
2. An explicit Status reconciliation section stating what is done, partially done, or not done, with the specific Jira task keys and code evidence backing that call (from the table above).
3. A Cloners link (clones / is cloned by) to the corresponding legacy Story under BIF-6428, so the new Story is not a blank restart — it carries a real, navigable reference to the original work and its task-level history.

Created:

WABA-Sxx	New Story (BIF-8910)	Clones (legacy, BIF-6428)	Reconciled state
S01	BIF-9051	BIF-6919	Not done
S02	BIF-9052	BIF-6920	Partially done — dev done, untested
S03	BIF-9053	BIF-6921	Partially done — dev done, untested
S04	BIF-8963 (pre-existing)	BIF-6922	Not done — core mechanism gap, tracked via BIF-8971
S05	BIF-9054	BIF-6923	Done, with one open gap (filter dropdown)
S06	BIF-9055	BIF-6924	Partially done — below-zero event + banner not built
S07	BIF-9056	BIF-6925	Not done — Jira/code mismatch on BIF-7223

Rejected alternative: re-parenting/renaming the legacy Stories directly onto BIF-8910 and retiring BIF-6428 (option (b) considered during the original jira-alignment-check remediation). This was not chosen because it would rewrite history on issues that already carry real, dated task completions from the 26Q1 phase — cloning preserves that trail on BIF-6428 while giving BIF-8910 its own clean, individually-tracked Stories for the 26Q3 remainder.

Consequences

• BIF-8910 now has all 7 WABA-Sxx Stories as direct children, closing the D4 alignment gap found by the 2026-07-22 jira-alignment-check pass.
• Each new Story's description is the authoritative "what's left" statement for 26Q3 planning; the legacy Stories under BIF-6428 remain as-is (Waiting Confirmation) and are not edited — they stay the historical record, reachable from the new Stories via the clones link.
• Sprint planning for this initiative should size and pull from the BIF-8910 Stories (BIF-9051–9056, BIF-8963), not the BIF-6428 legacy Stories.
• This does not close any sprint-drift-audit or jira-alignment-check finding by itself — per sprint doctrine, only a fresh reconciliation pass closes a ledger entry; this record gives that pass the resolved context to do so.