Skip to main content

Centralized SSO Token — Status 2026-06-30

Delivery / Program Management — periodic status report.

Summary​

Execution has not started (no RFC is execution-ready; all four repo RFCs sit behind the [critical] upstream SDK/Session-Manager contracts). Recorded at-risk this period for a newly-surfaced timeline clash: the initiative's Lane B QA E2E gate (13.5 md) overflows Q3 under the current FE plan. The target_quarter: 2026-Q3 window is soft (no commitment_date), but on today's sequencing the initiative does not finish in Q3.

Lowlights & blockers​

  • 🔴 QA E2E gate overflows Q3 (NEW). This is Lane B (qa_lane: B — manual QA gate, no automation substitute). The 13.5-day E2E execution is a mandatory, full-duration serial pass that can only run after the integrated FE lands. With FE 37 sitting serial-last on Syafrizal M., the integrated build completes ~W12.2, so E2E runs ~W12.2 → ~W15 — roughly two weeks into Q4. Shift-left design/automation against the RFC contracts can be authored during the build, but it does not shorten or discharge the manual E2E gate.
  • 🔴 FE over-commit drives the date. Syafrizal M.'s 37 FE days are the largest single driver of his ≥1.17 quarter load (roadmap Capacity summary / Program-level risks). The E2E overflow is a consequence of the FE landing late, not a QA-capacity problem (Yoddi is ≥0.67, Izzul untouched).
  • 🔴 Upstream SDK / Session Manager contracts (unchanged). @mekari/sdk package + CDN (SB-1), Session Manager + Kong /sm/* routing (SB-2), current_company sync endpoint — all owned by SSO/Account (BE); no Bifrost task builds them and they gate every repo's pilot.

Risk & dependency changes​

  • NEW — QA-E2E-vs-window clash. Derived constraint: for the 13.5-day Lane B E2E to fit inside Q3 (finish by ~W13), the integrated FE must complete by ~W10.3 — ~2 weeks earlier than today's ~W12.2. So the open "add a 2nd FE / move SSO FE off Syafrizal M." decision now carries a QA-driven finish-by date, not just an FE-hours argument. Recorded here per the delivery doctrine's "persist a notable timeline clash into the dated status report"; the matching gate is mirrored into timeline.md ## Dependencies & gates.
  • A deliberate slip (accept Q4 landing) or a re-staffing of the FE, if taken, should be captured as a delivery/decisions/ ADR.

Metrics​

  • Progress: 0 / 58.5 man-days (0%)
  • Throughput this period: 0 (pre-execution)
  • Forecast: p50 TBD · p85 TBD — pending the upstream SDK/Session-Manager contracts and the FE-staffing decision. Current sequencing puts QA-complete ~W15 (Q4); not Q3-deliverable as staffed.

Next period​

  • Resolve the FE assignment (2nd FE or move SSO FE off Syafrizal M.) against the ~W10.3 FE-finish-by date so the Lane B E2E can fit Q3.
  • Chase SSO/Account on the SDK package + Session Manager staging endpoint (the build can't start integration-testing without them).
  • Once FE staffing + upstream contracts are settled, derive p50/p85 and confirm whether a Q3 landing is recoverable; if not, open a reprioritization ADR accepting the Q4 finish.