Skip to main content

Bifrost Sprint 1 (2026-Q3) — Jira reconciliation, pass 5 (2026-07-15)

Jira reconciliation — recheck (2026-07-15)​

Re-pulled sprint 21367 via sprint-jira-digest.mjs and ran the deterministic sprint:reconcile engine (qontak-docs @ f41ad1a, past the 30d8080 roster-first fix). Issue count rose 122 → 130 (+8) since 2026-07-13. WIP 36; done-since-2026-07-13 throughput 12; oldest in-progress is BIF-8570 (Syafrizal M., 28d, still climbing — was 26d at pass 4).

Prior findings are numbered 1–12 as in the 2026-07-13 pass (stable ids); new findings start at 13.

Status of prior findings:

  1. One CID (BIF-6428, P11) — STILL OPEN, 5th pass. ⛔ ESCALATED, no response. Direct query confirms unchanged: status: Done, resolution: Done, zero children in sprint 21367. Grehasta #3 / Syafrizal M. #6 / Izzul #2 still read it as open work. Owner: Addo Hernando (DRI) — same decision as pass 1: confirm genuinely finished (→ mark those rows stale) or reopen + re-pull. Five consecutive passes with no action is itself notable — recommend a decisions/ ADR if this is still unresolved at sprint close (2026-07-17, 2 days out) so the PM/TPM decision gets a durable, un-droppable home instead of a sixth recheck.
  2. Board coverage — SUPERSEDED, carried into findings 10 below (P13/P14/P16 residue).
  3. Self Top-up retest bugs — RESOLVED (unchanged).
  4. Syafrizal M. over-capacity / off-plan — STILL OPEN, 5th pass. ⛔ ESCALATED. BIF-8570 now 28d (was 26d at pass 4), still climbing. New this pass: roadmap.md itself carries two contradictory figures for the same load — the Capacity summary table (line 239) says 1.21, 11 days over, matching canonical capacity.md; the Program-level-risks prose (line 240) still says 1.13, 7 days over (a stale citation from an earlier reconciliation). Owner: Bifrost EM/TPM — same decision (2nd FE engineer or offload); additionally, whoever maintains roadmap.md prose should reconcile line 240 to the canonical 1.21 figure — flagged here, not auto-fixed (prose reconciliation is outside this skill's propagation table).
  5. Adhoc bucket not in-sprint — SUPERSEDED, folded into finding 9.
  6. Satya roster-mismatch — RESOLVED (unchanged).
  7. A2 (BIF-8751) forecast — STILL OPEN, 5th pass. ⛔ ESCALATED. Still not in sprint 21367, still To Do. New this pass: assignee changed from unassigned to Addo Hernando (PM) — plausibly PM triage, but not an engineering pull and not a fix to the forecast. Owner: Satya (Vinsensius) + TPM — same decision: assign + pull, or formally downgrade the "A2 closes firmly" Deviations forecast before sprint close.
  8. Off-plan load — STILL PRESENT, grown further. BIF-8757 Launchpad-SSO cluster now 17 children (was 11 at pass 4; +6: BIF-8785, 8859, 8863, 8870-8874 range), BIF-7795 cluster now 4 (was 3; Grehasta). Addo's PM-side load holds at 28 (unchanged, expected per roster.json). Owner: TPM read — given this cluster keeps growing rather than resolving, consider whether it warrants its own tracked bucket container (mirroring adhoc-q3-2026's model) rather than staying untracked off-plan load.
  9. Adhoc bucket Jira ⇄ tracker drift — STILL OPEN, 4th pass. ⛔ ESCALATED, unchanged. In-sprint BIF-8695 children {7775, 8236, 8467, 8585, 8593, 8682, 8717, 8784} are identical to pass 4 — no narrowing. Three new Task-level children this pass (BIF-8830/8831/8833) ARE correctly split from A9 (BIF-8682) per their FE-Settings-menu summaries matching A9's PRD ACs — not new drift. Owner: Addo (bucket DRI) — same decision, now aging without action across 4 passes.
  10. P13/P14/P16 zero board presence — STILL OPEN, 2nd recheck of this residue → ESCALATING per doctrine. Direct query confirms BIF-8658 (P13), BIF-8640 (P14), BIF-8641 (P16) are all bare Epics, zero children, unassigned. Read against the queues: these sit at #4 (Grehasta, P13), #3/#4 (Hafriz, P14/P16) — behind higher-ranked Ready items (Grehasta: Qontak One → Self-Subs → One CID; Hafriz: Deduction V2 → Sales Invoice) that are still consuming their time. Owner: TPM — decision needed: confirm this reads as accepted queue-order sequencing (priority-ordered, not capacity-boxed, so reaching #4 by close was never guaranteed) rather than an accidental descope. If accepted, downgrade this from "gap to file" to a documented note in the sprint's Deviations section; if not, route through jira-alignment-check → sprint-jira-sync.
  11. Addo assignment-drift — unchanged, still benign. Same pattern as pass 4 (PM story ownership, not engineering staffing); lint:delivery still clean on BUCKET_IMPLEMENTORS_DRIFT.
  12. Qontak One Team Migration progress (68%) — unchanged, no new evidence this pass.

New findings from the 2026-07-15 pull — resolving the "F-12 residue" (7 status-progress initiatives deferred at pass 4 pending code-corroboration, now run):

  • deduction-v2: progress 0% → 38%. T1–T3 (BIF-8740/8741/8742) all Done and corroborated, merged to hub-core (PRs #8049/#8050/#8051). Engine bug found: sprint:reconcile's own per-initiative repo-scoping graded these unchecked because the RFC body says hub_core (underscore) and the registry slug is hub-core (hyphen) — the body-mention fallback never matches, so deduction-v2 gets zero scoped repos. Confirmed by hand via the team's full code_repos list instead. Report upstream to whoever maintains sprint-reconcile.mjs — parallel to the 2026-07-10 discipline-tag bug fixed at 30d8080. Excluded 1.0 QA-day (T2/T3) pending independent QA evidence. Written up: deduction-v2/delivery/status/2026-07-15.md → README cache → roadmap mirror.
  • self-subs: progress 0% → 3%. Task 2.1 (BIF-8790) Done and corroborated, merged to hub-core PR #8007. Written up: self-subs/delivery/status/2026-07-15.md.
  • 13. [code-evidence-gap, board-hygiene] self-subs Tasks 2.3/2.4 (BIF-8803/BIF-8804) resolved Won't Fix but carry real code signal — BIF-8803 has an unmerged branch (hub-core:origin/BIF-8803-be-hub-core-task-2-3-selfsubscriptions-initiate-in), BIF-8804 has no trace at all. Two other issues (BIF-8791, BIF-8802) both claim "Task 2.2" under different repos — possible task-id renumbering/duplication without a breakdown update. Owner: Grehasta/TPM — confirm whether work was redirected, not counted in progress either way.
  • 14. [code-evidence-gap, board-hygiene] self-topup BIF-8708/BIF-8709 Done with no code trace in hub-chat/hub-core (qontak-billing unchecked — no sibling checkout, so this is PARTIAL, not conclusive). These sit outside the 22-md as-built scope (post-reconciliation bugfix addendum), so the existing 90% figure is unaffected. Owner: Madani/TPM — confirm whether these were data/seed-level fixes (no code diff expected, per the sprint doc's own suspicion of "likely option_value seed data") or a stale board status.
  • 15. [scope question] sales-invoice-jurnal's done issue BIF-7825 ("Dynamic Payment Link Expiry for Self Top-Up") doesn't map to this epic's task-breakdown (Tasks 1–4 are about flag round-trip / Jurnal timeout / auth allowlist / Download-SI button — a different feature entirely), is PM-assigned, and predates this RFC (created 2026-03-20). Owner: TPM — confirm whether it's legitimately in scope for BIF-8117 or a stray/mis-parented ticket; not counted in progress either way.
  • downgrade-webhook (BIF-8698) and meta-whatsapp-pricing-oct-2026 (BIF-8762) — both done issues are RFC-authoring/[Documents] tickets by their own summary tags, not coded tasks; no breakdown row to attach effort to. Resolved/explained — 0% stands, not a gap.
  • lite-seats — zero done issues in-sprint; nothing to compute, 0% stands.
  • 16. [bucket-tracker-drift] A9 Status reads in-progress in the tracker but its Jira Story (BIF-8682) is still To Do — the child Tasks (BIF-8830/8831/8833, Need Feedback) show real movement, so the tracker's characterization is arguably more accurate than the stale Story-level Jira status. Recommend the fix land on the Jira side (transition the Story to match), not a README edit — flagging for Satya/PM, not changing the tracker this pass.
  • 17. [bucket-tracker-drift] A11 Status reads in-progress but its Jira Story (BIF-8612) is Waiting Confirmation — same shape as #16 (9 of 13 linked Tasks already Done per the tracker's own note); same recommendation (Jira-side transition, not a README edit).

This pass propagates: deduction-v2 and self-subs progress write-ups (status/ → README → roadmap, all applied this pass), plus dated escalation/read requests for findings 1, 4, 7, 8, 9, 10 (all now have a named owner and an explicit decision). It does not fix findings 1 (PM/TPM confirmation), 4 (EM capacity decision + roadmap prose reconciliation), 7 (Satya assignment), 8 (TPM read), 9 (Addo classification), or 10 (TPM queue-order confirmation) — each is now overdue relative to sprint close (2026-07-17, 2 days out) and should get a decision before then rather than a sixth recheck. New board-hygiene questions (13, 14, 15) and Jira-transition recommendations (16, 17) are routed to their named owners, not auto-applied.