Skip to main content

0001 — CEBE 26Q3: deprioritize, or commit to filing the RFC

Delivery / Program Management — decision record (ADR-style). State: proposal — this record exists to force a decision that has been deferred by default for eight reconciliation passes. It is not yet accepted; the DRI/PM must choose an option and remap status: to approved (accepted) or deprecated (rejected, keeping the record).

This ADR is the durable home for finding F-4 (coverage-gap, ESCALATED), open across Sprint 1 passes 01–11 and re-tested still-open in Sprint 2 pass-01 (2026-07-23).

Context​

Customer Event-Based Engine (CEBE, Epic TF-3302, roadmap P8) has:

  • No RFC authored — only the anchor + two Phase-1 child PRDs are drafted.
  • No Jira board presence — CEBE has 0 issues in Sprint 2 board 21484 (verified 2026-07-23), and had none across Sprint 1.
  • No named Data/Infra owners — the roadmap still shows TBD (Infra); Data Team allocation is unconfirmed.

The only startable work is the ~5-day RFC-authoring slice Julio Jeffer already sized. That slice has not been filed as a Jira Task, and no explicit not-started declaration has been recorded, for eight consecutive reconciliation passes. Per CDP sprint doctrine, a third sprint passing without the RFC filed is itself the decision to deprioritize CEBE — but by default, not deliberately. This record converts that default into an explicit choice.

Decision​

To be completed by the DRI/PM. Choose one:

  • Option A — Commit. We will file the CEBE RFC-authoring Jira Task under TF-3302 this sprint and staff the ~5-day slice; Data/Infra owners named by sprint close. (Remap status: approved.)
  • Option B — Deprioritize for 26Q3. We will formally drop CEBE from 26Q3 delivery; the PRDs remain drafted, the RFC is deferred to a future quarter, and the roadmap P8 row is annotated deprioritized. (Remap status: approved, and reorder the roadmap ## Priority.)

Deciding not to pick — a ninth pass with zero movement — is Option B by default, and this record should then be accepted as Option B.

Consequences​

  • Option A: CEBE re-enters planning-ready state; costs the 5-day slice plus the unresolved Data/Infra staffing question, which becomes the next blocker.
  • Option B: frees the implied P8 capacity expectation and stops F-4 recurring every pass; the cost is CEBE not shipping in 26Q3 and the PRDs going stale until revived.
  • Either way, F-4 closes on the next sprint-drift-audit pass once this ADR is approved and (for A) the Task key exists, or (for B) the roadmap reflects the deprioritization.