LiLo System · Delivery Planning

Delivery Schedule · Jul 6 → Aug 1 2026

Two engineers. Monday clears the decks (every remaining in-progress slice closed, plus one new WU each), then new WUs run at 3/day per engineer (6/day) open-to-goal. Ownership: Ryan → INST + PROP, Yash → DERIV + UA + NOTIF; Yash is barred from INST-PIPE-WU≥07 / INST-WU≥06. Live tracker, CTO re-plan Sun Jul 12: 37 done, 3 in progress, the rest to do. Week 1 is reconciled to shipped reality (the Sat Jul 11 catch-up column holds six Done WUs). Week 2 is the build run D6 → D10 plus a Ryan build-Saturday (Jul 18) that absorbs the on-hold and placeholder UA tail, so nothing spills into week 3 and the Stabilize → Ship window stays clear.

Family

INST

PROP

DERIV

OPR

NOTIF

HUB

INFRA

Done

In progress

To do

★ Monday closure slice

Model. 1 WU = 1 day, 3/day per engineer (6/day). Monday (D1) cleared the decks: all 11 remaining slices of the 6 In-Progress WUs closed (★), and each engineer opened one new WU; the 3/day cap is lifted only for that Monday wrap-up. Ownership: Ryan → INST + PROP, Yash → DERIV + UA + NOTIF. Week 3 (Mon Jul 20 → Aug 1) is reserved for Stabilize → Ship and holds no build WUs: the two placeholder blocks (End-to-End Testing, Enhancements across all 4 apps) are still to be decomposed. Everything build-side lands by Sat Jul 18. Week 1 is reconciled to shipped reality. The Sat Jul 11 column is a done-work catch-up, not new planning: it holds six shipped WUs (INST-WU-09 Location Capture, PROP-PIPE-WU-04a Check-Out Backend, INST-PIPE-WU-08 Hub Setup Widen, UA-PIPE-WU-02c Resident Terms, HUB-LAN-TLS-WU-01 LAN HTTPS Transport, HUB-WU-17 Third Reality Motion + H&T). That is a one-time exception to the 3/day cap, since these are a record of completed work rather than forward capacity. PROP-PIPE-WU-03a (Consent + Check-In) and DERIV-PIPE-WU-07 (Night Machine) also close in place on Fri D5. UA app-surface consolidation (the big structural change). Per the CTO-locked decomposition register (UA-DEC-5, 2026-07-06), Home is one WU built in three slices, not three WUs. The former board nodes UA-WU-09 (Reassurance Banner), UA-WU-10 (Recent Activity), and UA-WU-11 (Sleep Summary) all fold into UA-WU-03 (Home Screen, LIL-632), which mounts a StatusBanner mood, the metric grid, and recent activity. The grid is fed by three new read pipes: UA-PIPE-WU-06 (Home Metric Cards, LIL-979, D6), which gates UA-PIPE-WU-07 (Read-Model Cards, LIL-986) and UA-PIPE-WU-08 (Bathroom, LIL-987) on D7. The old Devices node (UA-WU-08 / LIL-641) is superseded by the real UA-WU-09 (System Health Surface, LIL-932), which is now on the board (Yash, D8) reading UA-PIPE-WU-05. UA-WU-05 (board "Notification Prefs") splits into UA-WU-10 (Notification Settings); the Alerts inbox becomes UA-WU-11 (Alerts Tab / Page). INST-PIPE-WU-05 (Resident Consent BE) is removed from the diagram. Week 2 build run. Ryan runs the INST/PROP spine D6 → D10 (INST-WU-07 Hub Commissioning pulled in from week 1 on D6; his Fri D10 slot takes the on-hold UA-WU-07 More hub so he reviews it that day). Yash runs the UA metric-cards cluster in dependency order (UA-PIPE-WU-06 → 07/08 → UA-WU-03 / UA-WU-04 / UA-WU-09) alongside his NOTIF and DERIV machines, at 3/day, no weekend. The placeholder UA tail (UA-WU-10 Notification Settings, UA-WU-11 Alerts) lands on a Ryan build-Saturday (Sat Jul 18) rather than spilling into week 3; Yash's weekend stays clear. INST-WU-02 (Auth & Job Scope) is excluded because its blocking substance is already shipped in main (INST-PIPE-WU-02 Done + auth-BFF + installerJobs resolver); see schedule.md §4. Estimates: per-WU story points shown where a Linear estimate exists; closures, ↳-finish carries, and unestimated placeholders render "—" rather than a fabricated number.