Delivery Timeline

One milestone per consuming surface (the per-repo RFCs); Launchpad is the cross-repo anchor and the pilot. Effort is from rfcs/cross-repo.task-breakdown.md §1 (re-baseline history: README forecast_basis + git). BE is each repo's current-company sync wiring; it excludes the upstream @mekari/sdk + Session Manager + company-sync work owned by SSO/Account (BE) (shared blockers below).

Phased 2026-07-19 (decision 0002): Phase 1 = Launchpad only (2026-Q3, 9.5 md); Phase 2 = CRM + Hub + Hub Chat v2 (2026-Q4, 28 md). No scope cut — total stays 37.5; only the step-5 consumers' window moves to Q4. Only Phase 1 counts toward the Q3 capacity plan.

Milestone	Phase	Source RFC	Effort (FE/BE/QA)	Confidence	Progress	Target Date	Status
Launchpad FE (pilot — Rollout step 4)	P1 · Q3	launchpad-fe	9.5 (FE 6.5 · BE 0.5 · QA 2.5)	low	0/9.5	Q3 (gated on SB-2)	Blocked (upstream)
CRM FE (step 5)	P2 · Q4	crm-fe	9.5 (FE 5.5 · BE 2.0 · QA 2.0)	low	0/9.5	2026-Q4	Deferred to Q4
Hub FE (step 5)	P2 · Q4	hub-fe	7.0 (FE 5.0 · BE 0 · QA 2.0)	medium	0/7.0	2026-Q4	Deferred to Q4
Hub Chat v2 FE (step 5)	P2 · Q4	hub-chat-v2-fe	11.5 (FE 6.0 · BE 2.0 · QA 3.5)	medium	0/11.5	2026-Q4	Deferred to Q4
Phase 1 (Q3)	—	launchpad-fe	9.5 (FE 6.5 · BE 0.5 · QA 2.5)	low	0/9.5	Q3	—
Phase 2 (Q4)	—	cross-repo	28.0 (FE 16.5 · BE 4.0 · QA 7.5)	low	0/28.0	2026-Q4	—
Total	—	cross-repo	37.5 (FE 23.0 · BE 4.5 · QA 10.0)	low	0/37.5	—	—

Capacity & Allocation

Squad-wide view + the Load signal: bifrost/delivery/capacity.md.

Committed days below are split by phase — only the Phase-1 (Q3) column feeds the Q3 capacity plan; Phase-2 days are Q4-deferred and excluded from Q3 load.

Implementor	Discipline	Phase 1 (Q3)	Phase 2 (Q4)	Total	Window
Syafrizal M.	Frontend	6.5	16.5	23	P1: Q3 (gated on SB-2); P2: Q4
Satya	Backend	0.5	4.0	4.5	P1: Q3; P2: Q4
Yoddi / Izzul	QA	2.5	7.5	10	P1: end of Phase-1 build; P2: Q4

⚠️ Chunked 2026-07-19 (decision 0002): only Phase 1 = Launchpad (FE 6.5 · BE 0.5 · QA 2.5) remains in Q3; Phase 2 (28 md) → Q4 and needs a fresh forecast in Q4 planning. Load effects: capacity.md.

Dependencies & gates

Every repo is gated by upstream deliverables owned outside Bifrost — until they land, each repo can only build its mocked-SDK slice (cross-repo task-breakdown §2 shared blockers):

• ✅ SB-1 resolved: mekari-account-web-sdk v0.3.0 is available as the bundled SDK dependency; there is no CDN gate.
• 🔴 Account & Launchpad / SSO/Account (BE) — SB-2: provide a live Session Manager staging endpoint for integration testing. session.refresh() throttle interval (PRD "TBD").
• 🔴 Infosec + Platform/SSO — whitelist the pilot product domain for the SDK iframe CSP.
• 🟡 Integration checks, not independent hard gates — current-company/Kong routing, canonical iframe path, postMessage origin validation, SDK event-name contract (Hub OQ-4); hub-chat-v2 cross-domain _mekari_account readability (Q1, flagged structurally impossible if hub-chat must read the cookie).

Internal sequencing: Launchpad pilot (step 4) proves the SDK → CRM / Hub / Hub Chat v2 onboard (step 5). Within each repo: feature-flag chunk → SDK-loader chunk → plugin chunks; the live Session Manager (SB-2) + iframe CSP whitelist gate end-to-end pilot validation.

• 🟡 QA E2E gate (Lane B): after the 2026-07-19 chunking only Phase 1's 2.5 md E2E (Launchpad) sits in Q3 — a mandatory manual gate, serial on Yoddi, run after the integrated FE lands (decision 0002); the pre-chunk finish-by analysis is superseded — history in git and status 2026-06-30.

Notes

No hard external commitment date on this initiative (target_quarter: 2026-Q3, soft). The binding constraint is SSO/Account delivering the live Session Manager (SB-2) + the CSP whitelist — they gate the pilot enable; FE capacity is tracked in capacity.md. No RFC is execution-ready today — all four sit behind the [critical] open contracts.