Skip to main content

0001 — Downprioritize Centralized SSO Token to P12

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

Context​

Centralized SSO Token (Epic BIF-7802) sat at P7 in the bifrost roadmap ## Priority table. The initiative is a tech-debt / platform effort — it moves the products onto a centralized web session via the Mekari Session SDK — and delivers no instant, visible value to paying customers. It was already the FE serial-last item on Syafrizal M.'s queue after the 2026-07-01 EM resequencing (Qontak One Team + Sales Invoice/Jurnal slotted ahead), and it remains blocked on an external gate (SB-2, the live Session Manager staging endpoint plus the per-repo current-company contract, owned by SSO/Account), so its Q3 E2E fit was already at risk.

Decision​

We downprioritize Centralized SSO Token from P7 to P12 in the bifrost roadmap ## Priority table, effective 2026-07-08. The stated rationale: it cannot drive instant customer value because it is a tech-debt-focused platform initiative, so it yields to customer-facing work. The five initiatives previously ranked P8–P12 (Lite Seats, Downgrade Webhook, Quota Management, Downgrade User, One CID Multiple WABA) each move up one rank to P7–P11; P13 (26Q3 Adhoc bucket) and P14–P17 are unchanged.

The decision was made in the Bifrost Internal Final Call meeting on 2026-07-02. Recording: https://drive.google.com/file/d/11z0nCLtOQ9pvM9T95fMr9cXuFvx9alBM/view.

Consequences​

  • Roadmap ## Priority table renumbered (P7 → P12 for SSO Token; old P8–P12 shift up to P7–P11); the SSO Token Priority note and the table's trailing changelog comment record the move and point back to this record.
  • Sprint-1 (delivery/sprints/2026-07-06-sprint-01.md) is re-derived from the new ranks: the P-ref labels and the per-engineer queue order are updated, since the queues are a priority-ordered projection of the roadmap ## Priority table. SSO Token moves down each queue to its P12 slot (Satya #1 → #3, Syafrizal M. #4 → #7, Yoddi #6 → #9) — it stays blocked and is skipped, but it now sits at its true rank rather than the top. All #-cross-references in the sprint (agent briefs, adhoc pull notes, blocker "Unblocks" lists, Jira-reconciliation rows) were updated to the new positions.
  • No scope is cut and no committed date slips: SSO Token carries no commitment_date, and the drop only formalizes the position capacity had already forced. target_quarter: 2026-Q3 and the effort_* figures on the README stand unchanged; Q3 E2E fit remains at risk (unchanged).
  • README.md needs no per-initiative edit — priority is portfolio-relative and lives only in the roadmap ## Priority table by doctrine (no execution_rank/priority field on the initiative).
  • The readiness dashboard (delivery/readiness.html) renders its own priority ranks and is refreshed via npm run fix:readiness, not by hand; its ranks were already stale against the roadmap and should be reconciled on the next readiness refresh.