Lane 1 · CI v1 context graph (the moat) + explainability rebuild
Lane 2 · SOC 2 (Sep 25)
P1 build
Customer-dated
Process
Stretch / shelved — first to cut
Holiday
How to read: tasks per person; TWO capacity lines (planning week vs execution, after FD buffers: Arbind 40%, Jatin 30%, Aditya 30%, Anmol 20%, Vaibhav 15%, Aditya Saini 10%, Pooran 50/50, Chirag full FD; Scott is off this board, his GTM work is tracked outside). Estimates are proposals — you correct them at sizing. Stretch items are excluded from the load math. P# is your personal drop-everything order: when two tasks collide, the lower number wins. No item outranks your P1. Personal leave days are subtracted from execution capacity.
Timeline by person. Spikes and decision docs close in planning week; consumers start after. Hover a bar for the full label. Red ▼ marks hard dates (Sep 4 stats · Sep 8 evals verdict · Sep 25 demo + SOC 2 internal · Sep 30 DB/MCP). Hatched bands = holidays. Buffer week = regression QA only; the shelved replay harness is the stated buffer-week dev option.
Timeline by workstream. Bars labeled by person. Convergence to watch: SWS-01 stats (Sep 4) feeding SWS-02/03 · the Sep 8 architecture dive feeding SWS-17 · the SWS-15 deep-dive gate feeding Surjoy + Akshit · Sep 25 demo and SOC 2 internal deadline landing the same day.