The Build

Timeline & Roadmap

The committed Phase 1 plan, month by month, from July 2026 to the January 2027 cohort launch — with the two anchor dates, the critical dependencies, and the success criteria. The dev team's workstream is sequenced against the-code's parallel Studio and trust-layer work.

Phase 1, month by month

Month	Dev-team workstream
July 2026 · Discovery & alignment	Study Studio's MVP and its outputs; joint walkthrough of the Published Course Package spec (incl. the five open items); LMS integration scoping against HBMSU's Moodle; confirm trust-layer integration boundaries and the six roles; agree the collaboration model. Deliverable: a joint architecture & integration plan.
August 2026 · Foundation build	Schema & data model to the target shape; the LMS layer as system of record (accounts, roster, gradebook, enrolment lifecycle); LTI 1.3 with Moodle (SSO, Deep Linking, NRPS, AGS two line-items); role & permission architecture (SME dual role separated); trust-layer integration interfaces stood up; audit logging; security baseline.
September 2026 · Adaptive core runtime	Evidence Check runtime; the bounded AI Companion (authored + runtime-dynamic anchors); milestone submission flow; AI-assisted grading interface; behavioural-signal instrumentation; all learning-signal capture at target shape; SME dashboards & review queues; the full learner experience end-to-end.
October 2026 · Integration, assembly & QA	End-to-end integration with real Studio courses (all 14 foundation courses loaded, version-pinned); full journey rehearsal; Companion boundary testing; dashboard validation; performance testing at 200–300 scale; security & privacy review; misconception-blocker enforcement testing; internal QA and bug remediation.
November 2026 · Testable environment anchor date	Stand up the testable environment for HBMSU academic, IT, and accreditation review; structured review sessions; walkthrough of the six roles; learner-experience and integrity-mechanism validation; HBMSU sign-off.
December 2026 · Launch readiness	Remediate the November backlog; SME onboarding for the delivery role; student-onboarding prep (incl. behavioural-signal disclosure); runbook & joint on-call model; a small pilot cohort simulation; final security/privacy sign-off; final HBMSU approvals.
January 2027 · Spring cohort launch anchor date	Launch-day joint on-call; live cohort support through the first weeks; data collection for Phase 2 (misconception-library additions, routing calibration, behavioural-threshold refinement, Companion anchor tuning).

The two committed anchor dates

Critical dependencies

These are named throughout Phase 1 because every other milestone rests on them:

Dependency	By when · owner
Published Course Package spec finalised (five open items closed)	End of July 2026 · the-code
Studio golden-slice complete at real course level	End of August 2026 · the-code
HBMSU inputs — 14 course syllabi, CLOs, assessment materials, SME reviewers assigned	End of July 2026 · HBMSU
Moodle LTI configuration + a real instance for integration testing	By August 2026 · HBMSU
Team harmony — a working collaboration model (architecture reviews, integration checkpoints, joint sessions)	Ongoing · both — load-bearing on every milestone

Phase 1 success criteria

By the end of Phase 1 (January 2027), the following should be true:

• The learner platform is live and operational; the 14 foundation courses are produced in Studio and delivered through the Adaptive Learning System.
• The AI-supported learner journey is functional end-to-end; the AI Companion is present with all structural constraints enforced.
• Structured mastery-node course design runs in the runtime; refined CLOs and aligned assessments are in place.
• Basic course-level recommendation is live; the basic academic dashboard is functional across the six roles.
• The SME review and quality-assurance workflow is operational; up to 200–300 Spring 2027 learners are using the platform.