Skip to main content

Self-Subs — Status 2026-07-14

Delivery / Program Management — periodic status report.

Summary​

No change to the initiative's own risk picture (still at-risk — see the 2026-06-30 report for the standing external-contract + FE-overcommitment risks). This entry exists solely to record a priority conflict on the delivery-layer's own required paper trail: the 26Q3 Adhoc bucket's story A9 (Custom Solution Insights UI polish, BIF-8682) was reclassified ⚪ Intangible → 🔴 Expedite on 2026-07-14 (PM/DRI call: it needs to ship now) and pulled in-progress the same day.

Per the adhoc-interrupt doctrine, an Expedite story preempts its own owner's ranked queue — the executing engineer's highest Ready item. On Syafrizal M.'s FE queue, Self-Subs (P6) is that item (the first entry not already In Deployment/In Progress per the 2026-07-13 Jira reconciliation in bifrost/delivery/sprints/2026-07-06-sprint-01.md), so Self-Subs' FE work yields to A9 until it closes.

Lowlights & blockers​

  • 🟠 NEW — briefly preempted by adhoc A9 (Expedite), 2026-07-14. A9 is FE-only and trivial (3 ACs — a Settings-menu entry, a sidebar-label rename, and removing a page title; no BE half, no new capability), so the delay to Self-Subs' FE start is small (~0.5 md) and not durable — Self- Subs resumes immediately once A9 closes. No delivery/decisions/ ADR: this is a same-day reordering, not a slip or de-scope of Self-Subs itself.
  • Standing risks unchanged from 2026-06-30: Mekari Billing / Mekari Pay / moderator-be external contracts still open, and Syafrizal M. (FE) remains over capacity (1.21) independent of this interrupt.

Risk & dependency changes​

  • Adhoc Expedite preemption recorded per doctrine — the required companion entries are the bucket README's ## Expedite log (row: A9, 2026-07-14, authorized by addo.hernando@mekari.com) and the roadmap ## Adhoc / Interrupt lane + ## Priority (P6 note). This status entry is the third leg — "persist the preemption up the chain" into the displaced initiative.
  • No change to the 2026-08-31 commitment_date risk recorded 2026-06-30 — that clash is unaffected by a same-day, sub-day FE reordering.

Metrics​

  • Progress: 0 / 17.5 man-days (0%) — unchanged.
  • Throughput this period: 0 (pre-execution; the FE queue detour is ~0.5 md, immaterial to the 17.5 md total).
  • Forecast: p50 TBD · p85 TBD — unchanged; see 2026-06-30 for the standing external-contract caveats.