Visible release notes published directly on the public site.
Release notes
Recent releases, current status, and the next visible growth steps.
QC+AI Studio is still a compact studio track, not yet a full fifteen-week academy. This page makes the current release state, the feature-availability boundaries, and the growth plan public.
Public feature states made explicit so visitors know what is live, fallback, or gated.
Curriculum, simulator, credential, and operational growth paths are now visible.
Recent releases
Public-facing changes
These are the most recent public improvements pushed to the live site and GitHub repository.
March 29, 2026
Activated live browser simulations
The simulations page now ships browser-playable labs for all sixteen verified concepts, alongside corrected notes, architecture guidance, and the longer-term rollout plan.
March 28, 2026
Improved public curriculum trust surfaces
Modules, About, Attribution, Account, sitemap, metadata, and lesson navigation were tightened so visitors can evaluate the platform without hidden assumptions.
March 28, 2026
Fixed deployment and syllabus presentation issues
Manifest hygiene, transcript fallback labeling, guest-session documentation, and syllabus citation duplication were corrected and redeployed.
Feature availability
What is fully live, guest-first, or environment-gated
First-time visitors should not have to infer feature maturity from trial and error. The public deployment now describes that state directly.
Status
Curriculum and lesson reading
Modules, lessons, syllabus, About, Attribution, and the new Simulations hub are public and fully reachable without sign-in.
Status
Grounded search and Q&A
Search and Q&A stay source-grounded in production. When OpenAI or Pinecone secrets are absent, the site falls back to grounded lexical retrieval instead of pretending semantic mode is active.
Status
Practice surfaces
Dashboard, projects, builder, and arena are usable in a browser guest session. Cross-device continuity still depends on authenticated identity being configured on the deployment.
Status
Persistent identity
Auth0-backed sign-in is prepared in the codebase, but the public deployment currently prioritizes guest-first evaluation unless client-side Auth0 variables are exposed.
Roadmap
Growth path for curriculum, practice, and credentials
The roadmap now acknowledges both content volume and learner outcomes. Expansion is not hidden behind vague ambition statements.
Expansion roadmap
Visible next steps
- Expand beyond the seven-lesson studio track: The current course remains an intensive starter-to-project path. The next visible step is to grow it into a fuller 12-15 week curriculum with additional lessons and labs per module.
- Persist and instrument the simulation layer: The live browser labs now exist. The next step is to persist simulation sessions, resolve citations per state, and wire analytics into learner dashboards and arena-style challenges.
- Add completion signals learners can carry forward: The product already uses portfolio-style rubrics. The next step is a completion badge and exportable portfolio summary that can travel outside the platform.
- Harden public-experience operations: Mobile-specific UX testing, Lighthouse-based regression monitoring, and broader discoverability work remain active follow-up items rather than hidden backlog.
Completion signals
What the platform recognizes today
- Current completion signal: rubric-backed project submissions and peer reviews tied to the public curriculum.
- Planned upgrade: completion badge and portfolio export so learners can carry evidence of work beyond the platform itself.
Community discussions, the first interactive simulator build, broader mobile testing, and external discoverability work remain active follow-up items rather than hidden promises.
External operations
Tasks that require platform-owner action outside the repo
A few discoverability and brand-protection items are real, but they cannot be completed solely by editing this repository.
- Submit the verified domain to Google Search Console so indexing can be requested directly.
- Register or acquire an exact-match `quantumlearn.academy` redirect if brand alignment and typo protection matter.
- Monitor search indexing, backlink growth, and Lighthouse trends as ongoing operational work rather than one-time code changes.