Getting Verivend to a safe "Keep The Lights On" maintenance state so engineering capacity can shift to Delio. Target: ready before the first Delio trainings mid-July 2026.
Ticket data pulled from Jira (project HTP) · 27 May 2026 · Overall % = weighted Vue3 50% · Veriform 25% · Admin 25%
Feature set = the "Vue2→Vue3 Remaining Work" list. Each feature combines its route ticket (technical 1:1 routes) and its Lightning Lane ticket (product feedback) — the dropdown shows the child items of both. Tap a row to expand. route / LL badges mark each child's source.
0%
Feature
Tickets (route + LL)
Progress (Done / in-flight / to-do)
To-do lift
Rough timeline — Verivend KTLO into the Delio ramp
Q2 is the transition window (finish the KTLO tracks); Q3 is when Verivend devs start contributing to Delio code, beginning with knowledge transfer and the first trainings mid/late July. Bars are rough, predictive planning ranges. Blue = Verivend · Orange = Delio.
Q2 · Transition
Q3 · Contribute to Delio code
May
Jun
Jul
Aug
Sep
Oct
▸ Delio training — mid/late July
Veriform stabilization
backend merge → DocuSign → enhancements
Admin tooling
6 [KTLO] items
Vue3 migration
in-flight features → Projects → tail
KTLO hardening & handoff
stabilize
Delio KT & first trainings
knowledge transfer
Delio code contributions
ramp on Delio
Verivend (KTLO)Verivend — contingent / hardeningDelio Delio training kickoff
Done In-flight (In Progress / QA / Code Review) To Do▸ Tap a Vue3 feature to expand its route + Lightning Lane child items