Skip to main content

Chatbot 26Q3 Engineering Initiatives — Status 2026-07-16

Delivery / Program Management — periodic status report. First dated status entry for this bucket initiative — its progress is the README ## Stories story-count rollup (done ÷ total), never man-days (buckets are goal-led-Kanban pull-in fill, deliberately unsized).

Summary​

Sprint-resync pass 6 (2026-07-16) escalates one code-evidence gap and flags a process-sequencing gap on Story A3, both first surfaced across earlier passes. Story-count rollup stays 0 of 3 Stories done (0%) — neither issue changes that math.

Risk & dependency changes​

  • Escalating (sprint-resync pass 6, F-15, code-evidence-gap). BOT-4653 ("[BE] reduce payload to Ably in bot-preview") is marked Done on the board with no merged-code trace in chatbot/chatbot-fe across 5 consecutive resync passes since 2026-07-15 (partial search — notification-service/qontak-designer not checked in any pass so far). This does not change the story-count rollup (BOT-4653 isn't itself a tracked Story), but it is a stale/incorrect-status risk needing a board fix. Decision needed from the assignee/DRI: confirm code-free or correct the board status.
  • Process-sequencing gap, Story A3 (not a docs-mirror drift — flagging for the DRI). A3's Jira Task (BOT-4661, "[FE] Upgrade pdfjs-dist...") reached in-review on the board before either (a) its own ## Expedite log authorization existed (added retroactively this pass, Authorized by still TBD) or (b) its RFC (sca-pdfjs-dist-upgrade.md) left draft status — DRI, reviewers, and approvers on that RFC are all still TBD despite the build being nearly complete. Recording this so the pattern doesn't repeat on A4+: Expedite authorization and RFC approval should land before build starts, not be backfilled after.
  • Staffing was corrected this same pass (see README.md implementors: + this initiative's roadmap/capacity mirrors): Baghiz Firdausa is now recorded as A3's FE/DRI, matching the board.

Metrics​

  • Progress: 0 of 3 Stories done (0%) — A1 backlog, A2 backlog, A3 in-review (none done yet).

Next period​

  • Resolve the BOT-4653 code-evidence dispute (F-15) before the next resync pass.
  • Get retroactive Expedite authorization + RFC approval recorded for A3; apply the lesson to any future Expedite story.
  • Continue tracking A1 (Ruby 3.4/Rails 7.2, still backlog) and A2 (Rails 8.1, still backlog) — no material movement this period.