Skip to main content

Self-Subs — Status 2026-06-30

Delivery / Program Management — periodic status report.

Summary​

Execution has not started (RFC kickoff still pending), but the initiative is recorded at-risk this period: a hard end-of-August commitment (commitment_date: 2026-08-31, commitment_type: revenue) was set, and the Phase-2 ship that satisfies it is gated by three external contracts Bifrost does not own — plus the initiative's FE sits on an already-over-committed engineer. The deadline cannot yet be confirmed deliverable.

Lowlights & blockers​

  • 🔴 Mekari Billing — self-subscription API + Invoicable list API contracts. Request/ response schema and qualifying SO statuses are unspecified; the hub-service resource (Phase-2 Task 2.3) is scaffolded with the live Pigeon call commented out, and the pending-SO modal shape is unconfirmed. Owner: Mekari Billing. Ask: confirm both contracts.
  • 🔴 Mekari Pay — redirect-param convention. FE post-payment state detection (Phase-2 Task 2.5) can't be wired until the success/failure query-param convention is confirmed. Owner: Mekari Pay.
  • 🟡 moderator-be — CID Billing Settings page path. Exact ERB view path for the Disable-Self-Renewal toggle is open (RFC Open Q6); blocks FE Task 1.3 end-to-end.
  • 🟡 FE capacity — Syafrizal M. over-committed. Self-Subs FE (7.5 d) sits on Syafrizal M., who is already ≥1.17 load on known FE work alone (see roadmap Capacity summary / Program-level risks). A hard August date on an over-committed FE is the headline schedule risk.

Risk & dependency changes​

  • NEW — deadline-vs-contract conflict. The 2026-08-31 revenue commitment was added this period (replacing a soft target_quarter-only window). It collides with unresolved external contracts (Mekari Billing/Pay) and FE over-commitment. Recorded here per the delivery doctrine's "persist a notable priority/timeline clash into the dated status report." A deliberate slip or de-scope, if taken, should be captured as a delivery/decisions/ ADR.
  • Phase-1 UI (Tasks 1.1/1.2/1.3) is not contract-blocked — it runs on mocks and can proceed in parallel, partially de-risking the calendar.

Metrics​

  • Progress: 0 / 17.5 man-days (0%)
  • Throughput this period: 0 (pre-execution)
  • Forecast: p50 TBD · p85 TBD — pending available-days/capacity and the external contracts above; cannot be asserted against 2026-08-31 yet.

Next period​

  • Chase Mekari Billing/Pay contract confirmations (the gating items) and the moderator-be path.
  • Resolve the FE assignment so the August date has a viable owner.
  • Once contracts land, derive p50/p85 and confirm whether 2026-08-31 is achievable; if not, open a reprioritization ADR.