Learning Studio / reference
Current limits
Understand the boundaries of this authoring build.
Delivery
Section titled “Delivery”Public course publication, SCORM export, public enrollment, and LMS delivery are not provided by this build. The disabled Publish control is intentional. Reviewer sharing is separate from learner delivery.
Structure
Section titled “Structure”Course content is structured JSON. Columns provide block nesting; accordion items can contain a single level of tabs. Phone/tablet layouts are overrides on shared content rather than separate device copies.
AI produces drafts or suggestions, not verified instructional truth. Cancelling protects the editor from late output but does not promise provider cancellation. Blueprint building includes at most one repair round.
Validation and evidence
Section titled “Validation and evidence”Review and Alignment help detect specific issues. Neither proves content accuracy, complete accessibility, or sound learning design. Current feature behavior takes precedence over older acceptance reports.
Access
Section titled “Access”Private resources and uploaded fonts are accessed with signed URLs. Reviewer access does not grant authoring rights. Agent integrations act as their signed-in caller.
File upload limits
Section titled “File upload limits”During beta, a file may be up to 200 MB. ZIP unpacking allows up to 500 files and 1 GB total uncompressed content; each extracted file must also fit the per-file limit. Keep a ZIP as one downloadable archive when appropriate. Replacing or restoring a shared file updates every course using that resource.
Integration retry limits
Section titled “Integration retry limits”Course operations and blank workspace creation support idempotency keys. AI course drafting does not currently provide the same replay guarantee, even when the HTTP create request includes a key. After an interrupted draft request, inspect the course list before retrying. See HTTP integration.
Validation context
Section titled “Validation context”MCP validate_course uses the shared validator but currently does not receive the editor’s complete resource set. Run the editor’s Review panel as well when checking missing private files; do not treat an MCP result as proof of resource availability.