CEDARLINE 3 windows analyzed: Baseline → Update 1

Reading notes

1. Not plotted above: 21 activities with zero net float movement · 21 held TF ≤ 0 at every observation (17 observed at multiple snapshots, 4 single-observation) · 0 held constant positive float. All 23 appear in the register below.
2. Baseline band counts in the inset carry the register convention: the 4 single-observation entrants are imputed at their only reading. The movement panel plots observed pairs only.
3. The horizontal scale is linear to 5 wd; no section break is needed.
4. Band deltas conserve across the population: 0 + 0 + 0 + 0 = 0 over 23 activities.
5. 4 snapshots are plotted per row: the grey tick is the first observation, the dot the last, and small intermediate ticks mark each observation between them, so the trajectory is retained.
6. Engine-reported recovery events (TF increase between consecutive snapshots): 1.
7. Method caveat (cite in any expert report): Float burndown is post-processing of analyst-supplied CPM snapshots. Accuracy depends on the quality of the underlying schedule updates. Recovery events (TF increase) may reflect legitimate scope removal, schedule optimization, or activity deletion, and the analyst must verify which. Slip velocity is a linear average; actual burndown may be non-linear. CPP first-mover at per-activity float-timeline granularity (2026-05-09); methodology not yet formally published in AACE/SCL literature.