0002 — QA reassignments to Izzul (One CID 6.0 md, Downgrade User 5.0 md)

Delivery / Program Management — decision record (ADR-style). Filed at the team level because it moves load between the two shared QA resources; capacity.md and roadmap.md mirror it. Recorded retroactively 2026-07-20 (the two EM/TPM decisions were taken 2026-07-01 and 2026-07-02); this ADR is now their canonical narrative home.

Context

Yoddi is Bifrost's primary QA (65 available eng-days, focus 0.8 → 52 effective); Izzul is a cross-team backup capped at 15 available (12 effective). As task-breakdowns were sized:

• 2026-07-01: one-cid-multiple-waba's QA was sized at 6.0 md. Landing it on Yoddi would have pushed him over capacity.
• 2026-07-02: downgrade-user's QA was sized at 5.0 md. It briefly landed on Yoddi's already-tight queue (51/52 = 0.98), pushing him to 56 ÷ 52 = 1.08 (over) for part of the day.

Decision

EM/TPM decisions on the respective days: Izzul takes One CID's 6.0 md QA (2026-07-01) and Downgrade User's 5.0 md QA (2026-07-02) instead of Yoddi, keeping Yoddi at 51/52 = 0.98 (under).

Consequences

• Izzul carries 11 md against 12 effective days — load 0.92, with ~1 effective day of headroom left. No further sized QA can move onto him without going over.
• This reassignment pattern is exhausted: the next QA overcommit (on either Yoddi or Izzul) needs a real timeline gap or a third QA resource, not another same-pattern reassignment.
• Mirrors: capacity.md Izzul/Yoddi rows and Over/under-commitment section; roadmap Capacity summary and P10 Priority note.