Fortnightly Schedule Validation
Live output of sessionGrid + templateResolver against the real template data. Not a static snapshot: this recomputes on every change, so it cannot drift from what a student would actually be scheduled.
Move First session and watch the amber deadline-anchored rows: they do not move. Everything before them shifts. That is why a schedule cannot be captured in one static file per month count.
Timeline — the shape, rather than the numbers
Solid dots are sessions with an agenda, small grey dots are check-ins, squares are deadline-anchored, and the hollow dashed circle on the top row is the kickoff — booked by hand, off the fortnightly grid, drawn at a modelled date so the opening of the program is visible. Hover any of them for the detail. Runs of grey with a gap beside them are the clustering the tables can only report as a statistic. Bars come from the production generator, not from this page: Zone A ships none in its templates, and the Academic Focus track Zone B and C do ship is discarded and rebuilt from the student's own school calendar. Change School year starts to watch that happen.
Every session — Q17: is this density right?
Grey rows are check-ins: sessions no template meeting claimed. Under the old monthly model these existed to pad each month out to 60 minutes of mentor time. On a fixed fortnightly grid they are about 0% of the student's mentor contact.
| # | Date | Kind | Row | Meeting | Min |
|---|