Stages & milestones¶
Supplemental reference · Browse supplements · Current report
Next: scope the ORAI AI-native classroom proposal. The stages below retain the larger two-course illustration, which exceeds Greg’s four-hour weekly capacity and requires rescoping or confirmed distinct support. Dates are relative to an approved future term. Six active preparation weeks do not include unpredictable allocation-review waiting time.
Test components and benchmark GPUs
Measure the DS and MLIS components before sizing the classroom allocation.
Events and gate
- Agree the exact inputs, workload configuration and correctness checks with course leads.
- Run CPU components on already-authorized campus UITS/AWS; record runtime, memory, files and failures.
- Run the GPU notebooks on Kaggle or free Colab; export results and actual device/quota information.
Advance when: Provider measurements are usable and the approved workload envelope is documented. Local CPU controls do not count as AWS or CUDA performance evidence.
Submit a sized ACCESS CPU + GPU request
Request the large CPU and GPU allocation with resource-specific quantities.
Events and gate
- Confirm course/term/cohort scope, designated PI, syllabi and required attachments.
- Submit the measured ACCESS request; record submission and review as distinct events.
- Confirm the award, CPU/GPU exchanges, storage and concurrency limits; CloudBank is conditional if its managed service fits.
Advance when: The provider-approved CPU/GPU configuration and educational project period are known. Review time may extend preparation; an application is not an award.
Run a ten-person component canary
Replay on ACCESS, then test one assignment per course with a small group.
Events and gate
- Replay representative workloads on the awarded CPU/GPU architecture and revise resource estimates.
- Run a ten-volunteer component canary, five per proposed course, with synthetic inputs.
- Confirm saved-file restart, portable exports and support effort; if using Classroom 50, rehearse assignment-to-grade flow and separate Codespaces/Actions limits.
Advance when: Both workflows succeed and unresolved defects are recorded. Narrow or defer if core fit fails.
Rehearse the whole class and recovery
Demonstrate the whole-class workload and independent recovery before required use.
Events and gate
- With provider permission, rehearse the planned class load and account isolation.
- Verify submissions, accessibility, independent restore, outage fallback and staffed support.
- Review all thirteen applicable gates; confirm any necessary grant-funded needs and distinct backup coverage.
Advance when: Readiness has dated evidence and named owners. Greg’s work stays within four hours/week; there is no cash budget or assumed grant award.
Teach the two-course pilot
Run the bounded two-course pilot on ACCESS with regular reviews.
Events and gate
- Orient learners, publish feasible support windows and retain equivalent CPU-assessed activities.
- Review access, resource usage, support and learner evidence at teaching weeks 3, 8 and 12.
- Track allocation expiry alerts at 60, 30, 14 and 7 days; decide the continuation route at least 30 days before expiry.
Advance when: The workload and support remain inside confirmed capacity; pause a failing component and use the rehearsed fallback.
Export, close and decide
Close the teaching cycle with usable exports and a deliberate next-term decision.
Events and gate
- Export learner work and reconcile grade records before access ends.
- Verify approved preservation copies and independent recovery; apply retention, account closure and deletion rules.
- Review actual resource/support demand and educational evidence; confirm a new project or approved continuation process.
Advance when: Exports and closure are verified. Educational allocation extension is not assumed.
All milestones after preparation are proposed. No award, resource reservation, course term or classroom admission is confirmed. Review the 13 checks →