Project timeline

17 weeks, three overlapping tracks, handover woven through

Contract: ~17 weeks, 2026-05-15 → ~2026-09-15 Jutland demo: Wed 27 – Fri 29 May — JB + Aswin visit teachers; v0.1 demo URL by then Mid-point review: week 6 (Fri 26 June), before both M and JB go on holiday Holiday window: Week 27 (Mon 29 June – Sun 5 July) — JB on Danish summer break; M at Croatia workshop Teacher pilot starts: week 13 (~2026-08-14), when Danish teachers return from summer

At a glance

gantt
    title 4-month AIPLA timeline
    dateFormat YYYY-MM-DD
    axisFormat %b %d
    todayMarker off

    section Strand A
    Setup & ADRs              :a1, 2026-05-15, 7d
    Jutland demo prep         :a2, 2026-05-22, 5d
    Build core (post-demo)    :a3, 2026-05-27, 30d
    Post-holiday iterate      :a4, 2026-07-06, 39d
    Teacher pilot             :a5, 2026-08-14, 32d

    section Strand B
    Build                     :b1, 2026-07-06, 28d
    Pilot                     :b2, after b1, 14d

    section Strand C
    Scoping kickoff           :c1, 2026-07-06, 21d
    Scoping draft             :c2, after c1, 21d

    section Milestones
    Jutland demo (v0.1)       :milestone, m0, 2026-05-27, 0d
    Mid-point review          :milestone, m1, 2026-06-26, 0d
    M + JB holiday (wk 27)    :crit, 2026-06-29, 7d
    Final handover            :milestone, m2, 2026-09-15, 0d

Phase shape

Phase Weeks Date range Focus
0. Decide & set up 1 May 15 – May 22 ADRs done; GCP projects (aipla-dev/test/prod-2026) live; platform feature work kicked off upstream (group-ID auth, tenant_id span hook, budget enforcement, artefact review pipeline — see notes)
0.5. Jutland demo (v0.1) 1–2 May 19 – May 27 All four upstream platform features landed 2026-05-19 (group-ID auth, tenant-span, artefact-review, budget enforcement). Repo sunholo-data/cphu-aipla-app instantiated 2026-05-19. Sprint M0–M5 completed and v0.1 deployed 2026-05-20 at aipla-v01-frontend-wgwhd7mspa-lz.a.run.app — 6 days ahead of the Wed 27 May Jutland deadline. Includes problem-set-hints Danish physics-tutor skill (projectile motion “Boldkast”), KU coat-of-arms branding, KaTeX, group-ID join. Buffer week 21–26 May for AR-led prompt iteration.
1. Build (Strand A core) 3–6 May 27 – Jun 26 In progress. Teacher UI (5 routes, wired to backend), teacher permission model (Firebase auth + Class entity + tag-based access), lesson picker, LED Planck lab (second physics skill), proactive tutor greet, commit-on-submit workbench state — all shipped by end of week 3. Next: KineBot (third skill), session persistence, teacher UI Phase 3 (Firebase auth swap).
Mid-point review 6 Fri Jun 26 Live demo + scope review before holidays
Both on holiday (M + JB) 7 (wk 27) Jun 29 – Jul 5 Code freeze. JB on Danish summer break; M at Croatia workshop
2. Internal iteration 8–12 Jul 6 – Aug 14 First eval run; iterate Strand A; Strand B build; Strand C scoping kickoff
3. Teacher pilot 13–14 Aug 14 – Aug 28 Real teachers (10 Danish + K) engage; capability-floor eval refresh
4. Strand C scoping draft 14–16 Aug 19 – Sep 9 5–10pp scoping note: beyond-LLMs, beyond-chat, student models
5. Handover-intensive 16–17 Sep 2 – Sep 15 Final docs, deep-dive sessions, sign-offs

Handover fan-out (parallel, not sequential)

Handover starts week 4, not week 13. Each artefact is explicitly co-owned with someone who’ll be around after the contract.

Artefact Primary inheritor Co-owned with First touchpoint
Capability-floor eval (dataset + runner) AR (domain) student helper (operations) Week 3 — co-design task taxonomy
Pedagogical rubrics / LLM-judge prompts AR — Week 4 — first rubric review
Production architecture (Strand A) DS + P2 ZL (day-to-day) Week 4 — ADR walkthrough
Cloud infra / GCP setup P2 (when hired) UCPH IT (for self-host migration) Week 6 — runbook v0
Day-to-day operations Student helpers P2 Week 8 — onboarding session
Strand B (simulation/game) ZL (likely) DS Week 10 — kickoff
Scoping note (Strand C) JB (audience) AR (input) Week 14 — draft review

Recurring handover mechanisms

  • Pair on commits from week 3 onwards — every major component touched by ≥ 2 people before merge
  • ADR sign-offs — every architecture decision needs a second signature, captured in the Sign-off column on the Architecture page
  • Bi-weekly walkthrough sessions — 1hr, rotating audience (AR / DS+ZL / P2 once hired / student helpers)
  • Task-oriented runbooks written for successors, not for posterity:
    • “How to add a new bot configuration”
    • “How to onboard a new teacher / class”
    • “How to run the capability-floor eval and update the report”
    • “How to add a new model to the routing layer”
    • “What to do when X breaks”

Risk markers

  • Teacher feedback window is narrow. Real teachers active only weeks 13–17 (post-summer). Don’t over-engineer pre-summer iteration on internal feedback alone — leave headroom to respond to teacher input.
  • P2 hire timing unknown. If they arrive late, their onboarding compresses. Pre-document everything assuming they may only have 2–3 weeks of overlap.
  • Both M and JB on holiday weeks 7–8 (early-to-mid July). The mid-point review at week 6 needs to leave M with enough scope clarity and enough demo material for JB to take into the break. No major direction-setting during the holiday window.
  • Build phase is 4 weeks pre-holiday, not 6. Strand A core needs the minimum viable vertical slice ready by ~Jun 26 — RAG and multimodal can layer on post-holiday if needed.
  • GDPR / consent forms — JB owns these but they gate any teacher-facing deployment. Confirm by early August at latest.

Definition of “done” at week 17

  • Strand A pilot deployed and used by at least 3 teachers (weeks 13–17)
  • Capability-floor report v1 published
  • Strand B prototype demonstrable
  • Strand C scoping note delivered
  • All artefacts have a named co-owner who has demonstrated they can operate them
  • UCPH self-host migration notes complete enough for IT to estimate effort
  • Final handover session run with P2 + AR + DS + ZL