Skip to main content

Deduction V2 — Status 2026-07-01

Delivery / Program Management — periodic status report. health: carries the delivery-health status; the doc-lifecycle status: stays in the linter enum (active).

Summary​

Backlog (sized, not yet in execution). The initiative was reconciled to backend-only after the authorize-at-send redesign: the earlier FE history-UI story (DED-S07, PRD CHG-001) was dropped (RFC §1 Out of Scope #5), so effort_frontend_days = 0 and Syafrizal M. is no longer staffed on it. Effort stands at BE 13 · QA 3 = 16 md (FE 0, medium confidence). All planning gates are present (PRD ✓ RFC ✓ task-breakdown ✓ review ✓); the sole remaining gate is an internal PRD refresh before the RFC can move to approved.

Highlights​

  • Scope/staffing reconciled and mirror-clean. FE = 0 / Syafrizal M. off is now consistent across the three hand-maintained homes — initiative README.md (implementors: Hafriz (Backend), effort_frontend_days: 0), the team roadmap.md Implementors column, and delivery/capacity.md Allocation (deduction-v2 absent from Syafrizal M.'s row; his load reflects no FE here). The delivery drift linter (lint-delivery) reports 0 errors, 0 warnings.
  • Remaining staffing: Hafriz (Backend) + Yoddi / Izzul (QA). Code (T1–T7) is execution-ready per the 2026-06-30 task-breakdown.

Lowlights & blockers​

  • 🔴 PRD refresh blocks RFC approval (internal governance gate). The authorize-at-send design gates message sending on the balance hold, which reverses PRD Non-Goal #4 (currently "the hold mechanism is for balance tracking only, not access control"; RFC review OQ-1). The PRD must be refreshed to mandate send-blocking before the RFC can move draft → approved. Owner: Bifrost PM (internal). This is the only gate; effort and capacity are not blockers.

Risk & dependency changes​

  • De-scope recorded: the DED-S07 daily-aggregate history UI (and the DED-S05/S06 delayed toggle) are intentionally not implemented in this design — see RFC §1 Out of Scope #5 and the PRD→RFC trace table. This removed the only FE surface and is the reason for the staffing reconciliation above.

Next period​

  • Land the PRD refresh (reverse Non-Goal #4 to mandate send-blocking), then transition the RFC to approved and begin BE execution (T1–T7).