Ed-Ready
Architecture and implementation contributions to an educational lab platform, including organization-scoped access, lab versioning, and course-first UX.
Scope of the work
Contributions to cloud lifecycle hardening, organization-scoped lab ownership, Save Version registration, documentation, and course-first UX.
Where it stands
The ownership and version-registration foundation is documented. Course-first UX validation and runtime revision integration are ongoing.
Recorded work
in progressExpanded the course-first UX architecture
Designed and implemented a clearer Ed-Ready flow across lab creation, course building, private and public publishing, organization adoption, assignment, and learner access. Local validation and interface refinement are still in progress.
completed foundation passCompleted PR 53 org-scoped lab ownership and Save Version foundation
Completed a major implementation and validation pass for PR 53, expanding Save Version from a narrow version-registration feature into the wider org-scoped authorization boundary needed for org-owned lab definitions, instruction and deliverable management, learner-safe launch flows, LTI course/context binding, public-lab adoption compatibility, legacy lab backfill safety, and managed immutable ECR image-version registration.
completedCompleted Ed-Ready documentation cleanup and audit
Finalized project-level docs, refreshed app-specific docs under lab_platform/docs, dated the documentation inventory, removed temporary audit files, and squash-merged the documentation cleanup PR into main.
in progressStarted container-backed Save Version ownership foundation
Started the backend foundation for container-backed lab versioning by adding managed image-registry support, version registration modeling, organization lab installation, ownership fields, creator-oriented access rules, and organization-scoped lab creation/read paths. The remaining authorization work is to finish sealing legacy edit and launch/session paths against the same org-scoped model.
completedMerged cloud lab lifecycle hardening work
Completed local and live cloud smoke testing for a hardened lab lifecycle flow, including protected lifecycle API behavior, approved image controls, browser-driven lab launch, managed instance metadata, scheduled cleanup behavior, and cloud stack teardown. Follow-up developer-experience gaps were tracked separately rather than treated as blockers.
design direction selectedMapped creator-mode lab versioning across virtual-machine and container-backed labs
Reviewed a proposed creator-mode lab versioning model against cloud container and virtual-machine behavior. The current working abstraction is to open an editable lab environment, modify it, save a draft version, test it, and publish after validation. For the next implementation pass, the practical MVP direction is local Docker editing and reproducible container-image artifacts.
completedMerged 10-day onboarding architecture package
Added a structured onboarding package that maps the platform across routing, stack responsibilities, frontend-to-backend flow, authentication, lab listing, launch flow, lab execution, backend session lifecycle, remote machine architecture, integrations, cloud infrastructure, infrastructure as code, and production architecture.
Open questions
- Divorced public-lab cloning and remix behavior remains a future architecture decision rather than part of the current foundation
- The final LTI learner/course membership model still needs separation from regular organization membership
- Frontend Save Version publishing workflow and runtime revision registration still need implementation validation before being documented as final product behavior
Next steps
- Complete local validation of the course-first UI/UX work
- Refine the interface from testing feedback
- Move LTI public lab adoption from the current compatibility path into the backend launch flow
- Continue from backend Save Version registration toward runtime revision integration